clients experiencing 802.11 association rejected for load balancing become unresponsive

[chiggin1]

clients experiencing 802.11 association rejected for load balancing become unresponsive

we have 70 Firmware MR 25.11 MR 53 waps  Both Windows and Apple clients that experience this event become unusable until they completely power down then restart.  What should we do?  Please help

[PhilipDAth]

This is usually related to client firmware - however you can disable client load balancing on the MR53's.

You need to go into Wireless/Radios Settings and edit the profile to disable "Client Balancing".

Note you can only do this if you are actually using a profile. If you are using the default profiles you'll need to create a new one first.  You can read over this document if you fall into this case:

https://documentation.meraki.com/MR/Radio_Settings/RF_Profiles

[chiggin1]

Thank you.  Have applied this to a couple of AP's.  Note that we have the problem with several different clients at least two of them have the latest version of firmware available

[PhilipDAth]

Also note that 25.12 is the current stable firmware - not 25.11.

[AndersonGarcia]

I had the same issue today. I did what was suggested here and it fixed the issue. I just wanted to point out that I didn't find the user load balancing option on the newer dashboard, I had to use the old version to get it.

Does anyone know where this option is on the newer dashboard?

[NolanHerring]

Assuming you don't have any custom RF profiles.

Then follow the below

[FelixWong]

I'm experiencing this issue currently with my clients.

Their APs are currently running firmware 25.11.

Did anyone get their problem solved after going to 25.12 or do we have to switch off client balancing to see a change?

[vassallon]

@FelixWong We have tried both 25.12 and 25.13 and have had to disable load balancing. Looking at the 26.1 and 26.2 release notes for the 26 beta firmware, it sounds like Meraki is trying to address some of these issues with that release.

[PhilipDAth]

If the client rejects a load balancing disconnect and falls to roam then the client has the issue. 

No Meraki firmware upgrade will fix the client. 

You can try and get fixed client drivers.   Otherwise your only option is to disable client load balancing on the Meraki side.   If the APs are getting overloaded as a result you may need to deploy more APs.