As far as I remember Windows 8 is far more picky with configurations/certificates than the previous versions. It took a while and a couple of tries to get the certificate right. Rui
Message: 1 Date: Thu, 03 Apr 2014 22:11:18 +0200 From: Alain P?an <alain.pean@lpn.cnrs.fr> To: freeradius-users@lists.freeradius.org Subject: Re: AW: freeradius EAP TLS / Windows 8 Client Message-ID: <533DC066.1040706@lpn.cnrs.fr> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Le 03/04/2014 19:39, kai.zemke@hauni.com a ?crit :
While i was investigating i also found this bugs about windows 8 and cisco APs. But they all apply to setups with a centralized access point management. I have only autonomous standalone access points. So from my point of view... this bug does not apply to my setup.
I already read the report of such a behaviour with windows 8 and a Netgear wireless access point (wnap300). If you have another wireless AP available, for example aruba, you should try with it. Another test is to try PKIP instead of WPA2 on your AP ssid.