Windows 8 may encounter a problem when trying to connect to the Cisco Unified Wireless Network. If the client is using WPA or WPA2 key management with AES encryption, then the connection may fail. With "debug client" in effect on the Wireless LAN Controller, a message similar to the following is seen:
*dot1xMsgTask: Jun 12 20:23:37.471: 00:11:22:33:44:55 Retransmit failure for
EAPOL-Key M1 to mobile 00:11:22:33:44:55, retransmit count 5, mscb deauth count 0
Windows 8 supports IEEE 802.11w (2009) natively in the OS. The Client implementation complies with IEEE 802.11w specification. All Windows 8 certified WLAN miniport drivers are required to support IEEE 802.11w through Windows Hardware Certification program. When Windows 8 clients attempt to connect to Cisco’s MFP capable APs, the connection fails. This failure is the result of an interoperability issue between Windows 8 IEEE 802.11w implementation and Cisco’s MFP implementation on their APs. The AP doesn’t report the correct “Key Descriptor version” for M1 in 4 way handshake. The client drops the unexpected M1 and thus the 4 way handshake fails. Legacy clients that don’t support 802.11w do not have this issue.
1. Update the Controller to updated Firmware Image: Cisco has fixed the issue in an update release. You can download the updated software from https://supportforums.cisco.com/docs/DOC-27213. This option is highly recommended. This image has a fix for reporting correct “Key descriptor version” for M1 of 4 way handshake messages. 4 way handshakes complete successfully thus establishing a successful connection. This will resolve the connectivity issue described above and also allow you to use all Windows WLAN 8 features.
2. Roll Back to Pre-Windows 8 Drivers. Another option is to roll back to pre-Windows 8 drivers. These drivers can be obtained from the hardware manufacturer or their website.
Note that this approach will disable all Windows 8 specific WLAN features and user experience will be equivalent to capabilities supported by pre-Windows 8 drivers.
The information and the solution in this document represents the current view of Microsoft Corporation on these issues as of the date of publication. This solution is available through Microsoft or through a third-party provider. Microsoft does not specifically recommend any third-party provider or third-party solution that this article might describe. There might also be other third-party providers or third-party solutions that this article does not describe. Because Microsoft must respond to changing market conditions, this information should not be interpreted to be a commitment by Microsoft. Microsoft cannot guarantee or endorse the accuracy of any information or of any solution that is presented by Microsoft or by any mentioned third-party provider.
Microsoft makes no warranties and excludes all representations, warranties, and conditions whether express, implied, or statutory. These include but are not limited to representations, warranties, or conditions of title, non-infringement, satisfactory condition, merchantability, and fitness for a particular purpose, with regard to any service, solution, product, or any other materials or information. In no event will Microsoft be liable for any third-party solution that this article mentions.
Article ID: 2749073 - Last Review: Nov 22, 2012 - Revision: 1