NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
RBR50 power LED blinking green, now appears hung or dead
So in the middle of my Teams meeting this morning my network just disappeared. I did the normal fault searching, and concluded the fiber-optic connection to my ISP is fine, the issue is with my RBR5...
Mstrbig wrote:If you rebooted the ONT before connecting the Orbi, then connected the Orbi router from a LAN port on the ONT to the WAN port on the Orbi, then turned on the Orbi and ran the Orbi setup, and you have no lights on the ONT LAN, You pretty much proved it is possibly dead.
I tried powering everything off and connecting and turning on components in different orders, no change.
Then I tried this:
https://kb.netgear.com/000059633/How-to-upload-firmware-to-a-NETGEAR-router-using-TFTP-client
During preboot I could actually ping 192.168.1.1, and the tftp upload completed on the first try.
I got my hopes up, but then thought it was still a failure as switching the laptop back to DHCP and waiting for the router reboot to complete I could no longer ping 192.168.1.1 and attempting to access http://192.168.1.1/ with a browser timed out.
I was about to shut it all down again when I noticed one of my wifi camera indicator lights go green. It had connected to a network that should not have been available. I double-checked the Ethernet properties on the laptop in front of me, and it had indeed received a 10.0.1.* address.
Turns out none of the many factory reset attempts had erased my configuration, so when I rebooted with firmware V2.5.1.16 it happily picked up where it left off, with the same wifi SSID and IP range which I had changed from the default to 10.0.*.*.
Only difference is I am now running V2.5.1.16 (which is what I uploaded manually through tftp) instead of V2.3.5.30, which I have avoided upgrading from since it has been so stable for me.
My assumption is that the router decided to force an automatic firmware upgrade on me in the middle of my Teams call, despite my manual cancellation of the upgrade all these months. It botched the upgrade leaving the router bricked.
Thanks! I got my hopes up there for a second, as the power LED did go solid green to solid amber to blinking amber to solid green.
However, there was no SSID broadcast, and connecting an Ethernet cable to a LAN port results in "cable connected but device not responding" and finally a self-assigned IP address.
Additional attempts to factory reset have no visible effect, and subsequent procedures have hade the same result, except now ending in a blinking green power LED instead of solid green.
No other Ethernet cables are connected, and the RBS50 is powered off.
Mstrbig wrote:
I find this sometimes resets stubborn Orbi routers.
Unplug the Orbi router from the wall, leaving the power supply plugged into the orbi for 3 minutes.
Holding the reset button, plug the Orbi in and turn on.
Once the power lights goes through red and back to green, release the reset button.
Hopefully you will have a solid green power light and can reconfigure the Orbi.
Mooose wrote:Thanks! I got my hopes up there for a second, as the power LED did go solid green to solid amber to blinking amber to solid green.
However, there was no SSID broadcast, and connecting an Ethernet cable to a LAN port results in "cable connected but device not responding" and finally a self-assigned IP address.
So the router power light is solid green? What self assigned IP address did you see? When wired to a LAN port, can you http:// to that IP address?
Mstrbig wrote:
Mooose wrote:Thanks! I got my hopes up there for a second, as the power LED did go solid green to solid amber to blinking amber to solid green.
However, there was no SSID broadcast, and connecting an Ethernet cable to a LAN port results in "cable connected but device not responding" and finally a self-assigned IP address.
So the router power light is solid green? What self assigned IP address did you see? When wired to a LAN port, can you http:// to that IP address?
I can get it to solid green by repeating your procedure, but sometimes it goes to blinking green. It is currently solid green and the IP address is 169.254.29.185. I can http to that IP, but only because I have apache running on my local machine, which has the self-assigned IP. There is no router or DNS server supplied by the RBR50, subnet mask is 255.255.0.0.
Mooose wrote:I can get it to solid green by repeating your procedure, but sometimes it goes to blinking green. It is currently solid green and the IP address is 169.254.29.185. I can http to that IP, but only because I have apache running on my local machine, which has the self-assigned IP. There is no router or DNS server supplied by the RBR50, subnet mask is 255.255.0.0.
This is good.
169.254.29.185 is basically an Automatic Private IP address. IP addresses in this range means the computer cannot see a network. A computer or device using DHCP needs to have an external server tell it what IP address to use.
So, did you reboot your ISP modem/router and are you plugged into it via LAN from it to WAN on your Orbi?
Mstrbig wrote:
169.254.29.185 is basically an Automatic Private IP address. IP addresses in this range means the computer cannot see a network. A computer or device using DHCP needs to have an external server tell it what IP address to use.
So, did you reboot your ISP modem/router and are you plugged into it via LAN from it to WAN on your Orbi?
I haven't plugged in my ONT, or anything else, at the moment.
If the RBR50 is working, shouldn't it have an active DHCP server providing IP addresses on the LAN ports regardless if there is an Internet connection or not? Also, shouldn't it broadcast the Orbi02 SSID by default after a factory reset?
I am pretty sure that I have been able to configure the RBR50 after a factory reset without first connecting the WAN before.