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.
Thanks for finding this and letting us know. Hope it helps out.
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.
This works. Make sure you check the "Always" box under keyword blocking. Thank you!
@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.
Glad it worked. Hope NG will get all this fixed so users can move forward.
Thank you for letting us know and being patient.
Chivvalry wrote:This works. Make sure you check the "Always" box under keyword blocking. Thank you!
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.
Hi all,
just want to add my discontent with how Netgear is handling this issue. I too have regular drop-outs of video conferences, calls, VDI sessions since March 9. I spend hours trying to solve it and will later tonight try to downgrade even further. I already downgraded to an earlier firmware but the system updated to V3.2.9.2_1.2.4.
For a $700 router this is unacceptable. Due to the coronavirus situation both my wife and I have to work from home, and both of us can't really work efficiently with constantly being dropped out of calls or VDI sessions. If the workaround mentioned above does not work, I'll have to buy a new router tomorrow morning.
Very unhappy.
I have been having the same issues with quick signal dropout as well with the RBR850. I noticed I was having audio streaming drop outs with Sonos (ethernet to BOOST to speakers via mesh network), Elder Scrolls Online (PC via ethernet), vairious online games (PS4 via ethernet) and YouTube/Netflix restarts and drop outs (Roku and Android devices via ethernet and also wifi).
System is Netgear Orbi RBK852 (RBR850/RBS850) and a Netgear CM1200 Modem (my own) with Spectrum ISP.
Steps I took to no avail:- Rebooted Modem & Orbis (of course)
- Checked stats on modem and Orbi and could not find anything that stood out
- Checked Modem direct and the PC direct worked perfectly with no drop outs
- Checked CTS and RTS values and those were set to 2347 for both as suggested
- Checked Modem in case it was a low signal that for some reason worked direct but didn't work with a router, no issues stood out
- Tried rolling back drivers to 3.9.2 and there was no change in the issue
- Used my protection plan to get a new Orbi System...same issue right out of the box without upgrading firmware. It was 3.9.2 out of the box originally. This means anyone picking up a new Orbi AX6000 will have issues most likely.
- Tried running a ping in CMD (pinged Google for a couple nights in a row) and would get a few drop outs (~10) but less then what I was actually experiencing which was around 4 or 5 an hour
- Tried about a dozen other fixes I have research with none of them working- Found my old router, connected it up and had no issues
The only thing that has worked so far is the fix I found on here where you roll back the firmware to 3.1.5.23 on the Satellite, then the Router, then factory reset both (I did Satellite first then the Router). Then blocked the update site (remember to click always and then aply) and so far it has stuck and has worked. I honestly think someone at Netgear was quitting made this code to spite the company, because when a system right out of the box has issues with your firmware retroactively, it had to be on purpose. Thanks Netgear, probably not recommending this to anyone now. Also a huge thanks to the individual who figured out this fix!- This seems to be a problem with anything long tcp connection based. I do not think udp has the issue. Once a buffer gets full the connection freezes and drops. In video it can fill faster than others.
This is my theory without actually seeing data.I've been getting regular disconnects again on my cell phone that last only as long as it takes to reconnect. to WiFi I've also had the same sorts of issues with Teams meetings over wired connection and WebEx over wireless (two different devices, one on VPN, one not). Thankfully I'm able to connect via phone for audio, so that stays going while my meeting connections are down.
I'm not sure how much of this can be blamed on the Netgear firmware, cloud infrastructure, or something else at this point. My streaming box (2019 nvidia Shield Pro) seems to be dealing with the connection alright at this point, probably because the disconnects aren't lasting long enough to burn through the entire buffer. If I can spare another hour or so, I may re-downgrade my firmware (since I was initally caught in the upgrade loop prior to people here figuring out the way to block DNS and prior to Netgear pulling down the buggy firmware from upgrade servers). I've said it before, but I'll say it again; I expected a LOT better quality from a $700 WiFi system.
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?
- 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.
