Firmware 2.2.1.210 released as of 10/3/18

YOu might try the manual FW file load and then factory reset and setup from scratch. Others have said this has worked for them and have working systems on v210. 

https://community.netgear.com/t5/Orbi/Firmware-2-2-1-210-released-as-of-10-3-18/m-p/1647303/highlight/true#M42416
https://community.netgear.com/t5/Orbi/RBK40-Download-Speed-Slows-Down-After-5-Days/m-p/1643475/highlight/true#M41776
https://community.netgear.com/t5/Orbi/Orbi-MR-2-1-Update-3-23-18/m-p/1548414/highlight/true#M27868
https://community.netgear.com/t5/Orbi/speed-slows-down-Orbi/m-p/1551822/highlight/true#M28289
https://community.netgear.com/t5/Orbi/Is-2-1-3-4-in-auto-update/m-p/1553979/highlight/true#M28616
https://community.netgear.com/t5/Orbi/Orbi-Satellite-RBS50-Not-Connecting-via-Ethernet/m-p/1556692/highlight/false#M28949
Roomba: https://community.netgear.com/t5/Orbi/Orbi-amp-the-new-Roomba-i7-connectivity/m-p/1655054/highlight/false#M44045

What is the size of your home? Sq Ft?
What is the distance between the router and satellite(s)? 30 feet is recommended in between them to begin with depending upon building materials.

What channels are you using? Auto? Try setting manual channel 1, 6 or 11 on 2.4Ghz and any unused channel on 5Ghz.
Any Wifi Neighbors near by? If so, how many?
What WPA security modes are you using?

Try disabling the following and see:
MIMO, Daisy Chain, Fast Roaming, IPv6 and Set 20/40Mhz Coexistence to 40Mhz only. Save settings and reboot the router and satellite(s).

If you updated to recent FW v.210, try enabling Daisy Chain. Some have mentioned that this seems to be working in reverse order, enabling means disabled actually.

---

Computer_Slave wrote:

Thanks for your clarification.  Airport Extreme does not have Ethernet backhaul but it least several Airport Extreme devices can be linked together either by ethernet cable (apparently no drop in speed through HP 48-port Gb switch) or WiFi (50% drop in speed) to provide a stable yet slower home network. But the latest firmware (2.2.1.210) of RBK53 is so unstable that it is not useable at all.  Firmware 2.1.4.16 is better but there is no option for a user to disable the firmware auto-update.  Now the RBK53 was put aside next to my Airport Extreme devices to wait for bugs fix!

---

It's interesting.  I was thinking about all the problems that people seem to be having with the v210 firmware and then there are the silent group that have no problems whatsoever.  I'm assuming the hardware is the same between users of the same models, provided NetGear didn't actually make physical design changes along the way without telling anyone, which is probably unlikely.  So the differences from user to user would likely be the modem they use, the physical devices they have connected to the ethernet ports, the physical setup of the Orbi system, and then the software configuration setup.  I'm wondering if, when people are doing a hard reset, they're willing to try to take everything they can "back to basics"?  No backhaul, not ethernet cabled devices, no custom software configurations, etc.  That would just leave them with only the modem that could differ from others that don't have problems using the same firmware and the same model of Orbi.

From what i've seen and others haven seen, some of the issues surround the auto update feature. Users have expressed that they systems have been working up to the point where the autoupdate happens, then everything starts failing. Even with prior v.16 FW, users said there systems were working until the autoupdate happens. I've had users do the factory reset and setup from scratch or the FW manual file load and setup from scratch, the ones that are willing, and they have expressed that they were able to get there systems running again. 

There have been other considerations, like modem router combo units, satatelite placement and some feature settings with in the Orbi system that seems to help. Daisy chain seems to be having problems right now on v210. Some have expressed that it's not working write or works in reverse enable disable in the UI. 

Reason why I ask what modem users have. 

Some have said there may have been subtle HW changes however we'll probably not really know. Some say older Orbi seem more problematic than more recent ones bought off the shelf. 

---

BleedingCash wrote:

It's interesting.  I was thinking about all the problems that people seem to be having with the v210 firmware and then there are the silent group that have no problems whatsoever.  I'm assuming the hardware is the same between users of the same models, provided NetGear didn't actually make physical design changes along the way without telling anyone, which is probably unlikely.  So the differences from user to user would likely be the modem they use, the physical devices they have connected to the ethernet ports, the physical setup of the Orbi system, and then the software configuration setup.  I'm wondering if, when people are doing a hard reset, they're willing to try to take everything they can "back to basics"?  No backhaul, not ethernet cabled devices, no custom software configurations, etc.  That would just leave them with only the modem that could differ from others that don't have problems using the same firmware and the same model of Orbi.

---