NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Orbi RBR50 No connection to ethernet wired devices
Firmware 2.7.2.104 MacOS computers. 3 or 4 days ago, my orbi lost connection with all of my ethernet hard wire devices. Has there been a recent firmware upgrade? I've noted that any hard wired de...
All,
I have a final update on this issue.
Unfortunately I experienced the same weird IP address issues, even after switching out the RBR50 for the RBK852 router.
Going back to square one, I eventually tracked the issue down to a faulty ethernet connection on an old Blue-ray player in my entertainment system.
Hard to believe that one bad ethernet port could cause such havoc. While it didn't bring down the whole network, it did bring down any ethernet hard wired device on the network. Turns out that neither the Orbi nor an Orbi update was to blame.
So . . . after switching over to the RBK852, as I said, I was still having issues getting any internet connection on any device using ethernet.
The issue was hard to track down.
At first I thought I had lost the entire ethernet switch that was feeding my entertainment system. What I learned from CrimpOn earlier in the thread was that one bad ethernet connection was all it might take the throw things off. So . . . by slowly connecting and disconnecting one device at a time on the switch, I was able to narrow the issue down to the ethernet port on the Blu-ray player being the culprit. Hook the BR player up via ethernet and strange 168.254 IP addresses started appearing. Take the Blu-ray out of the loop and bingo, ethernet was working properly again.
Kudos to CrimpOn. This nugget of information from him also helped solve the problem:
>> 168.254 is a valid IP address, although not one that an Orbi would assign.
169.254 is an IP address that a device self-assigns to itself when it cannot reach a DHCP server.
It did not come from the Orbi. <<
Thanks CrimpOn for sticking with it, offering advice, and continuing to ask the right questions.
Also thanks to Furrye38 for his helpful suggestions and support. We are lucky to have this community of experts that is willing to offer their
time and support and show an interest in helping solve our problems. You have made me feel validated by not treating me like the novice I know I am.
Roborbi
CrimpOn,
Unfortunately the unit is out of warrenty. More than a couple years old.
Thanks for the instructions on how to downgrade the firmware. I will consider.
I'm fairly certain the upgrade to the latest firmware happened 3 months ago however.
And up until 5 days ago all was working well.
My gut tells me it's a hardware failure.
Been looking for an excuse to go Wi-Fi 6.
I guess the orbi gods have answered. : > (
roborbi
Any chance you have a spare router? Something you can swap in to check this with a different router?
Yes. I have a new RBK852 Wi-Fi 6 unit arriving tomorrow. I'll let you know how the switch over goes.
roborbi
All,
I have a final update on this issue.
Unfortunately I experienced the same weird IP address issues, even after switching out the RBR50 for the RBK852 router.
Going back to square one, I eventually tracked the issue down to a faulty ethernet connection on an old Blue-ray player in my entertainment system.
Hard to believe that one bad ethernet port could cause such havoc. While it didn't bring down the whole network, it did bring down any ethernet hard wired device on the network. Turns out that neither the Orbi nor an Orbi update was to blame.
So . . . after switching over to the RBK852, as I said, I was still having issues getting any internet connection on any device using ethernet.
The issue was hard to track down.
At first I thought I had lost the entire ethernet switch that was feeding my entertainment system. What I learned from CrimpOn earlier in the thread was that one bad ethernet connection was all it might take the throw things off. So . . . by slowly connecting and disconnecting one device at a time on the switch, I was able to narrow the issue down to the ethernet port on the Blu-ray player being the culprit. Hook the BR player up via ethernet and strange 168.254 IP addresses started appearing. Take the Blu-ray out of the loop and bingo, ethernet was working properly again.
Kudos to CrimpOn. This nugget of information from him also helped solve the problem:
>> 168.254 is a valid IP address, although not one that an Orbi would assign.
169.254 is an IP address that a device self-assigns to itself when it cannot reach a DHCP server.
It did not come from the Orbi. <<
Thanks CrimpOn for sticking with it, offering advice, and continuing to ask the right questions.
Also thanks to Furrye38 for his helpful suggestions and support. We are lucky to have this community of experts that is willing to offer their
time and support and show an interest in helping solve our problems. You have made me feel validated by not treating me like the novice I know I am.
Roborbi