Problem connecting to a WPA2-Enterprise secured network

Greetings,

we are running here a WPA2-Enterprise secure wireless configuration. The authentication method in use is PEAP. Certificates are disabled. MSCHAPv2 is configured to prompt for a username and password. This configuration works perfectly well for *any* Windows version up to 8.0, Apple OSX clients and Linux boxes.

Windows 8.1 in this configuration does not connect successfully. Looking in the WLAN Autoconfig logs shows, that it succeeds the network association, then starts wireless security, starts 802.1x authentication, restarts 802.1x authentication, succeeds 802.1x authentication and stops wireless secrutiy. This cycle is repeated 8 times and finally results in an error with ID 8002, Failure Reason: The operation was cancelled.

Checking the logs on the radius server (FreeRadius 2.0.4) shows, that there are eight authentication requests coming in, which are authenticated correctly.

The problem is persistent to every 8.1 machine we had so far.  Any hints that point in a solution to this issue is highly welcome.

Helmut

March 6th, 2015 7:06am


Hello Helmut,

As this issue is related to radius server FreeRadius, it is recommended to ask in the related FreeRadius forum.

Please take a look at the following article.
http://freeradius.org/download.html
We strongly recommend that everyone using Version 1.1.8 (or any earlier version) upgrade to the latest 2.2.x or 3.0.xrelease as soon as possible.

Please note: Since the website is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.

Best regards,
Fangzhou CHEN

Free Windows Admin Tool Kit Click here and download it now
March 9th, 2015 4:36am

Hello FangZhou,

actually it turned out, that the problem was not Radius-related at all. Upgrading to the latest Radius version did not solve the issue, so we continued to investigate and figured, that it is related to a bug in our Cisco wireless controller, which is already documented in KB 2749073 . Upgrading the firmware on that device fixed the problem immediately. Thanks for your suggestion of upgrading the Radius, it was anyway a good idea to get this upgraded to the current level.

Best Regards

Helmut

March 16th, 2015 10:08am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics