Cannot connect to Win10 PC with client certificate (no connection possible)
aland at deployingradius.com
Tue Jan 14 14:42:44 CET 2020
On Jan 14, 2020, at 8:32 AM, uj2.hahn at posteo.de wrote:
> I installed CA and client certificates on Win 10 Pro client PC and configured a certificate based WLAN profile via Cisco AP (named ciscosb) to freeradius. (login via certificate, no password).
> But I dont't get it to work. PC says "no connection to this network possible". Windows WLAN report says "Error during authentification of EAP method type 13. Error: 0x54F. And it also says : Disconnect reason: explicit Eap error.
Ask Windows what "Error 0x54F" means.
> I'm still not clear where to find the issue: Client PC or Cisco AP or freeradius configuration.
> Here is the log of one connection attempt. Could you please check if from radius perspective everything looks ok?
> (3) Sent Access-Challenge Id 26 from 192.168.188.50:1812 to 192.168.188.45:41837 length 0
> (3) EAP-Message = 0x010200060d20
> (3) Message-Authenticator = 0x00000000000000000000000000000000
> (3) State = 0xca374eaecb3543720219c4f185b69853
> (3) Finished request
> Waking up in 4.1 seconds.
The Windows system decided that it didn't like the server certificate, and stopped doing EAP.
Where did you get these certs from? Are you using the testing certs from raddb/certs? Those *do* work.
More information about the Freeradius-Users