NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
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...
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.
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.
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?
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?
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...
- Just to clarify… The DHCP server was only part of my solution. There were several things that I did. But the DHCP server was the first thing that I did that really seemed to have an impact on the clients being recognized by the router. Prior to setting the router as the DHCP server, the router was “losing” devices in the attached devices menu. That’s what I meant by it wasn’t playing nicely with my DHCP server. But that’s what at least got my devices to be solidly recognized and not disconnected, especially the satellite.
I think the way that I reset the device as well as the fragment size were much more important. Resetting the device with just one method didn’t really seem to have any impact on performance or reliability. But when I reset it using the interface, then Telenet, and finally the reset button, things got a LOT better. It’s almost as if things were not being cleared out during a single reset.
Considering how much I’ve looked at this over the last 24 hours, I think the fragment size might be the MOST important, especially if you have a lot of devices. It’s almost as if the router is not properly utilizing this setting, especially since I don’t have any discernible packet collisions or fragmented packets from either the router status page or any of my network traces. Setting it to a very low figure does seem to fix the issues. That’s when I noticed that my ping times were leveling out to more of a straight line on the graph as opposed to the worlds tallest roller coaster. That’s also when I noticed zero connection drops and zero lost packets.
Granted there are still some other minor connection issues with certain types of devices, but I have a feeling that’s more of a blocked connection issue. In any case, it’s much better than it was. I’m currently tracking down whether the router is blocking certain port traffic to an iPhone, even though the security page is set to never restrict any ports or devices. For example, a wireless light switch shows connected and is available via a web interface. But it is showing as off-line when using an iPhone and the associated app. Same thing with nest thermostats and ring cameras. Of course, if I come across anything profound I will post it. And I have forwarded my info off to Netgear, but I’m not expecting a response and I’m not even expecting them to read it before Christmas.Just curious if you have tried putting the RBR into AP mode since you have a DHCP server already existing on your network. Does this change any behaviors? Having two DHCP servers on the same network would be problematic I presume.
Wombatmatty wrote:
Just to clarify… The DHCP server was only part of my solution. There were several things that I did. But the DHCP server was the first thing that I did that really seemed to have an impact on the clients being recognized by the router. Prior to setting the router as the DHCP server, the router was “losing” devices in the attached devices menu. That’s what I meant by it wasn’t playing nicely with my DHCP server. But that’s what at least got my devices to be solidly recognized and not disconnected, especially the satellite.
I think the way that I reset the device as well as the fragment size were much more important. Resetting the device with just one method didn’t really seem to have any impact on performance or reliability. But when I reset it using the interface, then Telenet, and finally the reset button, things got a LOT better. It’s almost as if things were not being cleared out during a single reset.
Considering how much I’ve looked at this over the last 24 hours, I think the fragment size might be the MOST important, especially if you have a lot of devices. It’s almost as if the router is not properly utilizing this setting, especially since I don’t have any discernible packet collisions or fragmented packets from either the router status page or any of my network traces. Setting it to a very low figure does seem to fix the issues. That’s when I noticed that my ping times were leveling out to more of a straight line on the graph as opposed to the worlds tallest roller coaster. That’s also when I noticed zero connection drops and zero lost packets.
Granted there are still some other minor connection issues with certain types of devices, but I have a feeling that’s more of a blocked connection issue. In any case, it’s much better than it was. I’m currently tracking down whether the router is blocking certain port traffic to an iPhone, even though the security page is set to never restrict any ports or devices. For example, a wireless light switch shows connected and is available via a web interface. But it is showing as off-line when using an iPhone and the associated app. Same thing with nest thermostats and ring cameras. Of course, if I come across anything profound I will post it. And I have forwarded my info off to Netgear, but I’m not expecting a response and I’m not even expecting them to read it before Christmas.
Wombatmatty wrote:
......... I think the fragment size might be the MOST important, especially if you have a lot of devices. It’s almost as if the router is not properly utilizing this setting, especially since I don’t have any discernible packet collisions or fragmented packets from either the router status page or any of my network traces. Setting it to a very low figure does seem to fix the issues. That’s when I noticed that my ping times were leveling out to more of a straight line on the graph as opposed to the worlds tallest roller coaster. That’s also when I noticed zero connection drops and zero lost packets.
.........Wombatmatty The CTS/RTS settings should affect only wireless devices as I understand it! how are your wired devices behaving now?
I have UPNP turned off by default as I prefer to have control over the port-forwards.
So I had the disconnect issue with the newest firmware despite having UPNP off.
Just got another router though and will install that later tonight as I'm giving up.
Will try to get my money back somehow given this is a $700 router.
