NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
MeGrimlock
Mar 10, 2020Apprentice
RBR850 Frequent Disconnects Starting March 9th AM EST
Yesterday 3/9, starting at about 6AM EST, my Orbi system is disconnecting my Nest Cameras and Thermostat and my work laptop every 10-20 mins or so. I have about 20 devices connected to my mesh syste...
Chivvalry
Mar 18, 2020Star
Bumping this for folks who may not have seen it... this WORKS. It's only a workaround until they fix that crappy firmware release but it'll get you up and running. Make sure to check the "Always" box as well.
xnolightx wrote:After adding updates1.netgear.com to the blocked sites list my RBR850 was no longer able to reach out for updates last night and is still sitting on 3.1.5.23. The only wacky thing is that the RBS (satellite) did manage to reach out and has upgraded to 3.2.9.2. That doesn't appear to be an issue because I have not experienced dropped connections with the satellite on this version.
For those of you who want to try this and you are using your Orbi in router mode, all you will need to do is:
1) In the Advanced\Security\Block Sites page add a keyword for updates1.netgear.com (make sure to hit the apply button in the upper right after adding the keyword).
2) Revert your RBR850 firmware to 3.1.5.23.
3) Confirm you are still seeing updates1.netgear.com on the Block Sites page.
4) Click on Administration\Firmware Update and wait a few moments. You should see the web GUI say that the service is unreachable under the status column for the RBR850.
If you are using the Orbi in AP mode the same principal applies, but you will need to add updates1.netgear.com to the blocked sites on your upstream router rather than the Orbi.
I hope this helps people get on with their digital lives while netgear figures out what they have broken.
bluegoose987
Mar 18, 2020Star
Confirmed, this isn't limited to .AX units. Latest NG firmware broke .AC units as well
Interesting is the NTP find in this thread. I went and checked, sure enough NTP was out of sync. Corrected and 4 of my IOT cameras were able to connect again. I don't know if it is coincidence or not, really grasping at straws but it's a simple thing for others to check. Also, what DNS settings are ppl seeing on their .AX systems?
- FURRYe38Mar 18, 2020Guru - Experienced User
Did you disable DST and if so, did you see any change?
Funny how this could be a problem since 3/1.
bluegoose987 wrote:Confirmed, this isn't limited to .AX units. Latest NG firmware broke .AC units as well
Interesting is the NTP find in this thread. I went and checked, sure enough NTP was out of sync. Corrected and 4 of my IOT cameras were able to connect again. I don't know if it is coincidence or not, really grasping at straws but it's a simple thing for others to check. Also, what DNS settings are ppl seeing on their .AX systems?
- bluegoose987Mar 18, 2020Star
Yes, disabled DST, manually set my time as it was off by 1 hour and applied. Already saw device count increase by 4 so some devices might not have liked time being out of sync...
Again, I'm grasping at straws here but it was an interesting find especially seeing users on the older .AC systems are having the same issues...- FURRYe38Mar 18, 2020Guru - Experienced User
Ok, I'll forward this to a forum moderator. Something to have NG look into.
Thank you for you the information.
bluegoose987 wrote:Yes, disabled DST, manually set my time as it was off by 1 hour and applied. Already saw device count increase by 4 so some devices might not have liked time being out of sync...
Again, I'm grasping at straws here but it was an interesting find especially seeing users on the older .AC systems are having the same issues...