NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
No ethernet connectivity from RBR50 (backhaul or devices)
I think I may have a similar issue as posted here (https://community.netgear.com/t5/Orbi-Wi-Fi-5-AC-and-Orbi-with/Orbi-RBR50-No-connection-to-ethernet-wired-devices/m-p/2096775#M120756). Everythi...
I've fixed it.
I would never have known this was even a 'thing', but the unmanaged switch in my lounge - between the router and the switch into my dining room - was the culprit.
I narrowed it down to the switch, so I unplugged it and tried it elsewhere in the chain and it worked without issue, which made me doubt whether that was the issue after all. I then positioned back in its original spot, plugged it in and all of a sudden, it's working without issue. I systematically plugged everything back into it, and everything is now purring like a kitten.
I did not realise that simply power cycling a dumb switch could fix the problem (given that there are no 'brains' going on in there) nor would I have thought that that could cause the issue in the first place... how has it managed to cause an issue in the network when all it's doing it providing more ports in the network?
In answer to your latest question though, FURRYe38, so as not to be rude when you've been helping me out...
The switch in question is a Netgear GS316-100UKS 16-port Gigabit unmanaged switch. Cables are mainly Cat.5e given that Cat.6 were too thick to manoeuvre around where required (i.e. when not in a straight run). My broadband is only 45 Mbps so I'm not suffering by using Cat.5e, although ultimately I would like to move to Cat.6 as a minimum, but that's a MAJOR job involving running cables through walls (I live in a brick house) and around bends and doorways.
I've had various different colours throughout this process.
I've had white when it's restarting; blue on the satellites when they're syncing; and pink on the router when it's trying to establish a connection or obtain an IP address.
I've had the pink light a few times in the past - normally after a firmware update or when something somewhere has gone wrong and it's lost connectivity - sometimes get drops in connectivity through the night according to the HomeKit notifications on my phone most mornings ("All home hubs are not responding").
At the moment I don't have any lights on anything - all Wi-Fi devices are working perfectly; all ethernet devices are not.
I've powered off the router and the modem several times for one minute minimum each time, and have performed the sequential reboot of devices several times to no avail.
RBR50 is running firmware v2.7.5.4, RBS50s are running v2.7.4.24 (and continuously tell me there are no further firmware upgrades available).
CAT.6 between the modem and router (right next to each other).
So as painful as it may end up being, I think I may be at the stage of systematically cable testing every cable in my setup and trying to isolate the offending device.
Yes I would check ethernet cabling for all wired devices to see whats going on. Disconnect ALL ethernet cables from the back of the RBR and just connect one wired PC or laptop and test.
You need to update the RBS as well to same version of FW manually using a wired PC and web browser and send the FW file package to the RBS web page:
I tried connecting directly to the RBR50 via ethernet this morning but my Mac was getting a 169.x.x.x address as well, so wasn't able to. So I'll have to try and find the rogue device/cable unfortunately.
FURRYe38 wrote:Yes I would check ethernet cabling for all wired devices to see whats going on. Disconnect ALL ethernet cables from the back of the RBR and just connect one wired PC or laptop and test.
You need to update the RBS as well to same version of FW manually using a wired PC and web browser and send the FW file package to the RBS web page:
Yes I have tried to manually update it (twice) - the first time it went through the process but didn't update the version number; the second time it told me I was trying to update to a version that's already installed (even though the file I have is RBS50-V2.7.5.4.img.
I feel like I'm starting to exhaust my options somewhat.
The devices that were connecting to 16.x.x.x addresses stopped after I turned off the satellites and they reconnected to the router (apart from my Eve Indoor Camera, which for now I've disconnected entirely). I've systematically tested every cable between my router and Satellite 1 and there are zero issues with any cables. Devices, on the other hand, I don't know, there could be issues that I haven't found. But I'm working on the assumption at the moment that a cable is the more likely culprit than a device (most of which are pretty new) just randomly deciding to break for no apparent reason.
I've now managed to upgrade the firmware on the two RBS50s, so all devices are now in sync in terms of firmware.
When I power cycle the router and disconnect both satellites, and then I connect a switch to the back of the router (which has my Philips Hue bridge and IKEA Tradfri gateway connected to it) everything is fine - the lights are controllable via HomeKit, the Hue and IKEA apps work perfectly. As soon as I connect Satellite 1 and the cables in the back of it, I start getting issues - Hue hub external connectivity light goes out, IKEA app won't connect to the gateway. Satellite 1 still only shows connectivity via 5G (even though I've synced the satellite to the router and all cables are plugged in).
I've just turned on satellite 2, and it's currently connecting via 5G (no ethernet connected yet). But I assume the same behaviour will happen after I sync the satellite to the router.
I really don't understand what the problem is all of a sudden - this has been rock solid for a few years now.
My gut at the moment says there's a faulty port somewhere between the router and Satellite 1, but without systematically trying every device (of which there are 12 and I've already ruled out seven) I don't know how to prove it.
I've now had this issue for over 24 hours, and I've spent 17.5 of those trying to fix this with what feels like zero progress.
UPDATE: I've narrowed it down to something connected between the router and Satellite 1. Everything else in the house is now up and running, including Satellite 2 which has re-established connectivity via ethernet backhaul to the router, which means I can at least go to work tomorrow as all my office equipment is back online.
Satellite 1 is connected to the router via a series of switches:
Router -> Lounge switch (unmanaged) -> Dining room switch (unmanaged) -> Satellite 1
- [Lounge] TV
- [Lounge] Apple TV
- [Lounge] PS5
- [Lounge] Xbox
- [Lounge] Sky Q
- [Lounge] Sonos
- [Lounge] ethernet to dining room switch
- [Dining room] TV
- [Dining room] Apple TV
- [Dining room] Sky Q mini
- [Dining room] Sonos
- [Dining room] Satellite 1
I've tested all cables in the lounge, and I've tested the cables from the router to the lounge switch, the lounge switch to the dining room switch, and the cable from the dining room switch to Satellite 1. So I need to test the cables for all devices in the dining room and then, failing that, it's a physical port on one of my devices rather than the cable.
It could also be a config. issue on one of the devices, or an IP address conflict, etc. But I've checked the IP addresses on the router and I can't see any conflicts.