NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Orbi disconnecting continously
I just bought an Orbi Router + satellite, the first 2 weeks where a dream, excelent speed, WiFi everywhere and almost no hickups, but it had been already 2 weeks of nightmare, disconects every 20 minu...
Hello Everyone
We have release firmware version 1.12.0.18 this firmware has fixes for disconnects and many more I posted the release notes below.
https://kb.netgear.com/000044171/RBR50-Firmware-Version-1-12-0-18
If you are still having issues after updating your Orbi unit you may want to factory reset the Orbi and test again. If you are still having disconnect issues or other issues with this firmware please create a new thread or contact our support team.
http://www.netgear.com/support/contact.aspx
Thanks
DarrenM
OP, what firmware version do you use?
I have V1.8.0.6 and I get disconnect on all of my devices (Mac, AppleTV, PS4, Nintendo 3DS, iOS, etc.). Only solution is to turn off/on wifi or in case like AppleTV, I have to reboot the entire device.
Wifi disconnects not fixed here with V1.9.1.12. Running Orbi in AP Mode. Turned down 2.4GHz transmit power to 25%. Implicit beamforming and mu mimo disabled.
Today 3 non-moving iOS devices got disconnected in 10 minutes, each 3 times! The devices were 1-3 meters from satellite away (in visual range). I did some RSSI analysis: Seems that the devices get kicked out from 5GHz band while the signal is strong, but the 2.4GHz signal from identical Orbi is equal or slightly stronger. It seems not to be a steering problem between router and satellite since my signals are well separated (satellite client signals are strong while router client signals are very weak and vice versa).
Turning down the transmit power of the 2.4GHz band to 25% helps for medium/long distance to the router/satellite as workaround, but not for narrow distances. Playing with the 2.4GHz transmit power "controls" at which distance the disconnects are typically happening.
So the root cause is a band steering bug between the 5 and 2.4GHz bands. Which is very disappointing for such expensive hardware, especially if you consider that client side band steering (without expensive hardware) works more reliable and Netgear didn't fix this bug for months (while very aware of the problem).
Slowly but surely I conclude that Netgear can't fix that problem and I should return the defective by design devices...
If all your devices support the 5GHz band I recommend disabling the 2.4GHz completely as a workaround (and if you don't need to cover the very far distance which 5GHz can't reach). I have some legacy devices so I can't turn it off.
(posted in a other discussion, too)