Dear Meraki Community,
I got 3 different customers using MR33 APs and all of them reporting issues with this product.
Symptoms are as follows, some equipment are able to associate to a SSID on an specific MR33 AP while others fails. But they can connect to another MR33 AP. All equipment are in the same network.
For my 3 customers, I noticed the connected device were only in 802.11b/g channels (2.4GHz) ! Tried reboot, factory reset, nothing.
Is there any bug somewhere ? Firmware version is the latest stable.
Meraki support asked me to deactivate 5GHz band steering and upgrade to the latest beta version.
But my concern is band steering is recommended in best practices and I would like to be sure the beta will also work properly and will not bring other issues.
Hope somebody else experienced the issue with this model to work together.
Solved! Go to Solution.
Band steering requires that the client send an active probe request - and not all clients do. Those that don't wont see the SSID. If the issue you are seeing is that clients can not even see the SSID then disable it - otherwise this is not related to your problem.
Upgrading to the beta firmware is a good idea to try. The beta firmware has lots of issues resolved in it.
I have a client with similar problem, and one alternative solution we did was:
- Configure all MR33 with L3 Roaming in Access Control
- Configure the minimum bitrate to 24Mbps (excluding the 802.11b devices)
- Configure in radio settings the option of: Radio Power to Enable automatic power reduction.
With that we observed better performance over wifi.
I hope this can help you.
Did you find a solution on this problem ?
I experience the same problem, and the problem is about 1,5 week old, the same time you experienced that some clients could not find the ssid and unable to connect to the MR33.
If you got a solution from support or others in the community, please add solution to this problem in this thread so more of us can solve our challenges.
Thanks in advance.
Recently I replaced some access point MR12 to MR33 and some clients reportered issues with connection but only when the connection is throught MR33 with another access point like MR42 doesn't have any issue.
Did you find a solution?
Thank you !
Currently I have the same issue with some clients connect to MR33 but if the user move to another location and connect to MR32 or 42 with the same firmware the user connect without problem.
I have rebooted the AP several times but the issue is the same.
Current version: MR 25.9.