Client Connecting To Multiple APs And Disconnecting

[AhmedJawad]

I have clients, example below. we have the flowing issues 

- the client is connecting to access points in other floors. this client is in the 6th, and it is connecting to the 7th , 8th, and sometimes even the 9th. 

- I have changed the RF profile per floor to reduce the power transmission and the bitrate. 

- The client is trying to connect, and the aroma between AP6139 and AP6141 is getting disconnected. error in the attached below is EAPoL invalid MIC 

- The only change we had some time ago is we enabled 801.11r for fast roaming because we had issues with phones not connecting in some areas. 

any idea please ? 

[alemabrahao]

While many customers enable 802.11r within their network without issue, some legacy devices may not connect to an 802.11r network. 802.11r is a recommended feature due to its many benefits, however a device audit is encouraged first to ensure that mission critical devices are not affected.

Fast Transition (FT) 802.11r roaming is not supported between Meraki WiFi 6 models and any other MR Access Points (APs) running version 25.x or lower. If you have a mixed deployment with WiFi 6 models and any other model of Meraki APs and 802.11r is either set as enabled or adaptive on any of the SSIDs configuration ensure all your APs are running version 26.4 or higher.

https://documentation.meraki.com/MR/Wi-Fi_Basics_and_Best_Practices/Roaming_Technologies

Try disabling the client load balancing to.

https://documentation.meraki.com/MR/Other_Topics/Client_Balancing

[AhmedJawad]

All of the affected users are Windows 10; there are no legacy devices. 

[alemabrahao]

Is the WiFi network card driver up to date?

[AhmedJawad]

All of the laptops in the company are controlled by SCCM for updates, so they should be all up to date. 

is there any specific bug in any drivers you know of? 

[RaphaelL]

EAPoL Invalid MIC.  Let me guess.. Windows 10 with a Intel wireless NIC and MR running 29.X++ ?

[AhmedJawad]

Yes , Any known bug ? 

[RaphaelL]

Yes. This is an issue with Microsoft. 

https://community.meraki.com/t5/Wireless-LAN/Wireless-Invalid-MIC-EAPoL-4-way-handshake-is-failling/...

https://community.meraki.com/t5/Wireless-LAN/WE-need-your-help-Help-us-fix-a-bug/m-p/211547

The only fix at the moment is to turn off 802.11r until Microsoft deploys the fix later this month / next month. 

[RaphaelL]

I forgot that Microsoft said : This will not be fixed for Win10 releases due to complexity of backport and regression risk.