NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Solution to fix Orbi Satellite flashing white forever/failed upgrade
TL;DR
If your satellite upgrade fails and is stuck with the white pulsing led forever, follow Netgear's instructions for a manual upgrade, but do not download their TFTP2.exe file, use this one on ...
- When the satellite is in Recovery mode, it will not ask for a DHCP address, and instead will only use 192.168.1.1. Also, you'll have to have it connected directly to your computer. If router is set for that subnet, it'll already take 192.168.1.1, so you'll have IP conflicts and likely be unable to see the satellite with an IP scanner. You *might* be able to reassign the router's IP, but then again you could just save a lot of trouble by connecting the satellite directly to computer. Plus a direct connection has the lowest chance for a corrupted upload.
When the satellite is in Recovery mode, it will not ask for a DHCP address, and instead will only use 192.168.1.1. Also, you'll have to have it connected directly to your computer. If router is set for that subnet, it'll already take 192.168.1.1, so you'll have IP conflicts and likely be unable to see the satellite with an IP scanner. You *might* be able to reassign the router's IP, but then again you could just save a lot of trouble by connecting the satellite directly to computer. Plus a direct connection has the lowest chance for a corrupted upload.
SOLVED! Thanks for the hints, everybody... here is what I ended up doing:
You were correct that the satellite IP address was indeed 192.168.1.1 -- but I was not able to either ping that address or see it with the port scanner (since no ports were active, I guess?)
I manually set the PC's lan port to 192.168.1.68, and plugged it directly into the WAN port of the RBS40 (port #1) using a standard ethernet cable. This caused my PC to disable the ethernet port, so I plugged the PC into a mini-hub first. Once the network activity light showed that the PC was active, I plugged the satellite lan port #2 into the hub. While holding the reset button in, I powered up the satellite and continued to hold the reset button until the power led started flashing red (10-15 sec). At that point it was connected to the network using the default id address.
Based on other tips, I activated the TFTP feature on the PC, started a Powershell as Administrator, and successfully pushed the latest firmware image onto the satellite, using:
`tftp -i 192.168.1.1 PUT .\RBS40-V2.1.4.16.img`
I could watch the lights on the hub flashing as the file was transferred, and when they stopped I could see in Powershell that the transfer was successful. After a power cycle, the satellite booted up as expected, and I could sync it with the router. Sweet!
