NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
gobananasnet
Oct 10, 2020Apprentice
RBR50 "Connection Hell" since the new firmware update v2.5.2.4
RBR50 "Connection Hell" since the new firmware update v2.5.2.4. A few days ago everything seemed ok, all 30+ devices were connecting. Now since the firmware updated a few days ago 75% of our 30+ devices have a great deal of trouble staying connect. No change in devices or their locations. HELP!
10 Replies
- gobananasnetApprentice
I just updated the firmware manually to v2.7.0.70, and that only updates the main router and not the satellites. Apparently that manual firmware is only for the router as the satellites rejected this version when attempting to update them manually too, all via the web interface. Also, it has not helped connectivity. Most of our security system is down and many other important devices too. This is crazy making. HELP!
gobananasnet wrote:I just updated the firmware manually to v2.7.0.70, and that only updates the main router and not the satellites. Apparently that manual firmware is only for the router as the satellites rejected this version when attempting to update them manually too, all via the web interface.
There are separate firmware downloads for RBR vs. RBS. If you try to upload the RBR firmware file to an RBS it will fail as incompatible. Make sure you download the RBS50 firmware file from https://www.netgear.com/support/product/rbk50.aspx#download, unzip it, and select that file when manually updating each satellite.
- gobananasnetApprentice
Thanks, yes, I'm well aware of that. It was successful for the main router, but the Satellites it is not yet made for them it seems, only works on the router at this time. Satellites remain v2.5.2.4. Thanks
- FURRYe38Guru - Experienced User
Be sure you power OFF the RBR and RBS for 1 minute then back ON after a FW udpate. IF you still notice odd problems, try a factory reset and setup from scratch and check again.
- gobananasnetApprentice
I had already done all of that. That problem remians unchanged. UGH!
- FURRYe38Guru - Experienced User
Revert back to v16 on the RBS first, then RBR lastly. Reset and setup from scratch.