NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Orbi firmware v2.1.1.16 discussion
do we need to do nvram wipe for this 2.1.1.16 Firmware just released today? noticed it downloaded automatically.
Reporting back about four days after rolling back to v2.0.0.74.
Stability and connectivity remain generally good, and worlds better than 2.1.1.16. Devices are connecting to the nearest router and not disconnecting randomly. It's maybe a little more volatile than before, but that could be my imagination.
I am having two significant new problems:
* I've got a second-generation Nest thermostat that can connect to the network just fine, but cannot retrieve an "entry key" for coupling with a Nest account. While working through the issue with a Nest technician, we discovered some information buried in the Nest network settings: the ping is 11,000 milliseconds. Yeah, as in: 11 seconds. It's literally 20 feet away and within line-of-sight of one Orbi, and maybe 15 feet away from a satellite in the other direction. I tried resetting the thermostat, reconnecting to the network... no dice.
* I've got an older Brother WiFI printer that just cannot connect to the network. I've reset it and reconfigured it repeatedly.
Both devices have been in use for years without issue. They've even outlasted some WiFi equipment (an old Linksys router, then Apple AirPorts, now the Orbi). No idea why they're having such trouble now, or whether it's the fault of the Orbi or the devices.
Still contemplating a network change to Velop or something else, especially as Netgear continues to fail to acknowledge the severity and urgency of this problem.
I am noticing also that my wireless printer now does not stay connected to the network. This printer worked flawlessly before. I do have a special character in my connection password.
Also I appear to have computers dropping from the internet. This could conceivably be dropping from the network, or the whole network disconnecting from cable modem. I will research further. I may try going back to a known stable version of the system for my RKR40 router and both RKS40 satellites.Suggestions appreciated.
I have about 45 devices on my network. Sat/RBS50 isn't showing any connections but I believe thats a known UI issue. I hardwired my backhaul via 1Gbps switch. Also - since I factory reset all settings after installing v2.1.1.16 - I am stable... no reboots in 10 days and counting. Previous to this my RBK50 system was rebooting like nuts.
Follow-up to my message 379. Just after I posted, one of the two satellites lost connection (even though it was part of Ethernet backhaul). I reset the entire system to factory settings (Router and both satellites) and set up (for what seemed like the 50th time - maybe that's why the model number has a "50" in it) as a new system.
GREAT NEWS! Since then, the router and satellites have remained connected, as have the 38 end-device connections.
Look forward to the next firmware update to (hopefully) fix this mess and at least some acknowlegement from Netgear that they have caused great productivity loss (and frankly, pain) to their loyal customers (I have been one for over a decade).
My plan is to switch back to 5 GHz backhaul for location 2, if and when this is fixed. The Velop system will remain in location 1, since it will soon be too late to return it during the weeks it will take Netgear to fix this, and I have no option for a hard-wired solution there.