NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
thebishop
Feb 01, 2017Apprentice
Orbi drops wifi for iPad Pro, iPhone 7 and Macbook Pro intermittently
Running 1.4.0.34 on both main Orbi and sattelite (main and sattelite are on different floors with wall between, perhaps 20-25 feet distance straight line). I generally have "5 bars" of Wifi on al...
- Jul 11, 2017
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
Tingyunliu
Feb 17, 2017Star
Using the same ssid was exactly what I did. So far, this happened to me on my iPad Air and iphone7/6. Just reset the network on These devices. Will see how it goes. Thanks for the tip. Btw, Apple TV seem to be ok. No wifi dropping.
For others:
1. If you have this problem, does this only happen to you iOS devices?
2. If you have this problem, do you use the same ssid for your iPhone/iPad?
For others:
1. If you have this problem, does this only happen to you iOS devices?
2. If you have this problem, do you use the same ssid for your iPhone/iPad?
- thebishopFeb 17, 2017Apprentice
Ok, I tried removing it and readding the SSID and it still drops. I dont think it is the clients really - as someone else had problems with their Note3, so the answer to 1. is "No".
I have seen drops on both new iOS and new macOS devices (we don't have any non-Apple devices to try with).
It really seems to be an Orbi problem and I once again offer to help Netgear engineering with any troublehshooting they might need, I can fully reproduce the problem here and would be happy to run with any additional debug logs required to help pinpoint the reason.