NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.

Forum Discussion

rdnarrs's avatar
rdnarrs
Aspirant
Apr 06, 2022
Solved

ORBI RBS850 update of Firmware from V4.6.3.16_2.0.51 to V4.6.7.13

I received an email from Netgear that there was an important Security Firmware update for my RBR850 system and I should update.  I went to the Advanced / Administration / Firmware update section of t...
  • rdnarrs's avatar
    rdnarrs
    Apr 09, 2022

    I tried a initial install with the same results, router and one satellite OK.  I decided to try to update the firmware on the remaining satellite and the router hoping that it was a firmware incompatibility issue..  The satellite took a longggggg time to go from 99% to up and running (20 minutes.) After the updates and powering all 3 of the units off and on, everything came up roses - so it must have been a firmware incompatibility from

    V4.6.3.16 to V4.6.7.13.   This issue can be closed.

FURRYe38's avatar
FURRYe38
Guru - Experienced User
Apr 07, 2022

What web browser did you use? 

Did you update the RBSs Fw using the RBS web page or thru the RBRs web page? 

 

I recommend using a web browser and PC to setup the RBR first after a factory reset. Walk thru the setup wizard here, skip adding the RBS. Once the RBR is setup, then take one RBS at a time, while near the RBR or in same room and wirelessly sync the RBS to the RBR. Wait for the front LED to turn BLUE then OFF. Once off, so same for 2nd RBS. Once fully synced and checked, power off the RBS and place back in to normal remote locations.

rdnarrs's avatar
rdnarrs
Aspirant
Apr 09, 2022

I tried a initial install with the same results, router and one satellite OK.  I decided to try to update the firmware on the remaining satellite and the router hoping that it was a firmware incompatibility issue..  The satellite took a longggggg time to go from 99% to up and running (20 minutes.) After the updates and powering all 3 of the units off and on, everything came up roses - so it must have been a firmware incompatibility from

V4.6.3.16 to V4.6.7.13.   This issue can be closed.