I have one MR45 with poor WiFi quality.
I opened a case for this problem.
It´s only on our MR45 (not on MR42, MR42E, MR52, MR32 ...)
It´s only on some Dell Notebook models and on Microsoft Tablets (not with Apple Notebooks f.e.)
The problem occures only when the devices are running on battery.
If you plug in the power supply the problem disappears immediately.
If you change the Win10 power-saving for the Wireless adapter from "normal" to "high..." then it works!
Dear Meraki stuff, do a update for this accespoints, and tell the service that this problem exists, they don´t believe me!
Solved! Go to Solution.
I guess @cmr will chime in here too. I'd even say that's a known problem with AX and the Intel chipsets (or better their drivers).
Please keep us updated regarding your TAC case.
@CptnCrnch I replied where @redsector posted in this thread: https://community.meraki.com/t5/Wireless-LAN/Getting-low-connectivity-MR45-Meraki/m-p/99993#M14778 as indeed it has been a known issue to Meraki since June but they need us to do some more diagnostics that I was unable to do in lockdown...
I found out:
All devices running with Win 10 (1909)
Dell Latitude E7400 with Intel Wireless-AC 9560 is working well
Dell Latitude E7450 with Intel Dual Band Wireless-AC 7265 is working well
Dell Latitude E7490 with Intel Dual Band Wireless-AC 8265 is not working well
This information I sent to the Meraki case
News from the Meraki support:
So we are aware of some issues on with the Wireless-AC 8260's you're running the 8265's but I believe these are extremely similar to each other. I believe this issue is related to the beamforming (documented below).
With your permission, I'd like to perform a backend change to disable the beamforming on the MR45 for now. If this works this would atleast get things running for the time being whilst a fix is implemented.
Could I ask which SSID we have been testing on so far? This backend change is made on a per SSID basis so we could test this on 1 SSID for now. This change would only take effect on the MR45.
I do not expect disruption to the clients on the MR45 at this time but its also possible they could experience temporary issues or a disconnection when this backend change is made.
Meraki put an modified firmware on our MR45:
"So, I need to move just this MR45 onto a different firmware for now, this will mean this will allow everything to keep working even if your MR is rebooted. Again this is only temporary whilst the entire issue is looked into on our side.
Please note the firmware change will involve a short amount of downtime as the device reboots 2-3minutes is likely.
If this is also agreeable I will make this change from my end?"
It´s working now.
The issue occures (only?) on Wireless-AC 8260 and 8265 wireless hardware
The issue occures only when the notebook or tablet is running on battery, no issue with an external power supply
The issue occures only when the power saving of the WiFi hardware is set to standard (Win10), not when you change it to high power consumption
In the End: you can´t put blame on Meraki. I think it´s an Intel issue.
Here are the news:
I wrote to Meraki helpdesk after an test-update on one of our MR45:
"Great, it´s working now.
But: you reduced the functionality.
Isn´t it better to complain at Microsoft or Intel to provide a proper driver for the wireless-devices?"
this is the answer:
Thats great news!
You are correct, ideally this would not be required at all.
Please be assured that this issue is on-going, we still have our teams working on this issue, it has not been forgotten about. The fix we have used here is only a temporary work-around. Whilst I do not have an ETA on a true fix, we at Meraki are still looking into this.
This fix was simply aimed to get you up and running whilst we proceed.
We will let you know via this case as soon as a full solution is found.
Kind Regards ..."