Controllerless Networks

Reply
Contributor I

IAP - MIC failed in WPA2 Key Message 2 from Station

Dear community hoping you can help please, I have a dual Instant Access Point 205 setup.

Corporate wireless network is configured, using WPA-2 / WPA and internal authentication server. iphones are fine when users connect but windows 10 clients will not connect. Any ideas please?

Security logs read:

Jun 14 13:53:53  stm[1849]: <132094>  |AP NERA_AP01@10.1.10.11 stm|  MIC failed in WPA2 Key Message 2 from Station …… Have I missed something in the configuration?

Guru Elite

Re: IAP - MIC failed in WPA2 Key Message 2 from Station

Are you using Preshared Key authentication or 802.1x?

That message is fairly generic and we need to narrow down the issue.

 



Colin Joseph
Aruba Customer Engineering

Looking for an Answer? Search the Community Knowledge Base Here: Community Knowledge Base

Contributor I

Re: IAP - MIC failed in WPA2 Key Message 2 from Station

Hi cjoseph, I am using 802.1x using the built in authentication server. Each
user has been set up with an ID and password. I also tried to create a
second similar SSID but experience the same issue. Thanks
Guru Elite

Re: IAP - MIC failed in WPA2 Key Message 2 from Station

Okay.  Windows 10 has some known issues when the internal server is used for authentication (802.1x termination).  Please see the thread here:  http://community.arubanetworks.com/t5/Wireless-Access/Authentication-with-EAP-PEAP-on-Windows-10/td-p/252673  It has to do with EAP-TLS 1.2

 

The long-term solution is to use an external radius server.  The short-term solution is to use the hack here:  https://support.microsoft.com/en-us/kb/3121002



Colin Joseph
Aruba Customer Engineering

Looking for an Answer? Search the Community Knowledge Base Here: Community Knowledge Base

Contributor I

Re: IAP - MIC failed in WPA2 Key Message 2 from Station

Thanks to those of you who commended on this one. You were correct in terms of it being a windows 10 issue. Apparently TLS 1.2 certificates are mandated by Windows 10. This issue was resolved by upgrading the ArubaOS on the IAP. The updated ArubaOS includes a compliant TLS 1.2 certificate and as such this is resolved.

Please note, the IAP software was updated by downloading from the Aruba support site as the opton to "check for updates" via the IAP web interface did not access the recently released version. Thanks again for your help, much appreciated. And my apologies for the delayed feedback.

Search Airheads
cancel
Showing results for 
Search instead for 
Did you mean: