NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Plugging devices to the ethernet ports of RBS53 knocks it off the network
After manually updating the firmware's on my one RBR and 2 RBS's, everything works fine, with good wireless backhaul between the router and the satellites.
When I connect 2 devices (Dish hopper and Chromecast Ultra) to the Ethernet ports at the back of one RBS, that RBS gets disconnected (and displays the solid Magenta LED).
Disconnecting the devices cables from the RBS restores the connection in "Good" backhaul condition.
Any idea why this is happening. It is a recent behavior. I had the 2 devices using the Ethernet ports on teh RBS for many many months until a few days back. Then discovered that they had old firmware, which I updated manually (detailed in a different thread).
6 Replies
I confirmed this with the second satellite.
It drops connection with the RBR sporadically until I disconnected a couple of Ethernet cables from the satellite (and switched those devices to WiFi). After that, the satellite-router connection is rock solid.
Very weird.
Any idea why the satellites don't like the use of its Ethernet ports?
Could they be getting confused by expecting a wired backhaul if I connect a device o the ports? I am spitballing here.
Any settings that I should check to allow the use of the Ethernet ports without disturbing the wireless connection between the RBR and tge RBS's?
Does this happen if only one of the devices is connected to a satellite?
Moving the Dish Hopper is not trivial, but the Chromecast could be connected directly to the router. Does that cause a problem?
When these devices are connected with Ethernet, are they configured to turn off their WiFi connection?
Are they both connected to the same television?
What I suspect is that the Ethernet connection is causing a 'loop' of some sort, which overwhelms the satellite CPU or the actual Ethernet switch that is built into the satellite hardware. Alas, this would not be trivial to validate.
Could you
- connect to a satellite web debug page using the Orbi web administration credentials ("admin" and password)
https://kb.netgear.com/000053867/How-do-I-connect-a-satellite-to-my-Orbi-router - record the satellite CPU utilization. (Refresh the screen several times to get an average reading.)
- connect the device(s) that cause the problem.
- continue to observe and record the satellite CPU utilization.
- connect to a satellite web debug page using the Orbi web administration credentials ("admin" and password)
I keep my DISH hopper ethernet connected to a 2ndary GS series non managed switch behind any RBR I have online. Then any and all RBS and DISH Joeys ethernet connected to this same GS series non managed switch.
ISP modem> RBR<>GS524(Main home network switch)<>Out to other wall jacks, patch panel and ethernet connected devices.
RBR<>GS108(2ndary segment switch)<>DISH Hopper
GS108(2ndary segment switch)<>DISH Joeys x2
GS108(2ndary segment switch)<>RBS in Dinning room
GS108(2ndary segment switch)<>GS108 in living room<>GS108 in basement<>RBS in basement
Thank you all for your suggestions.
I now have a stable setup with 1 RBR, 2 RBS's, both without any Ethernet port connections and with with good wireless backhauls. All devices in the rooms with the RBS's are using WiFi. I will proceed carefully and systematically, recording the CPU usage per CrimpOn's instructions.
I'll connect the cable to RBS#1's post, other end uncononnected.If stable, I'll connect the cable to the Hopper, keeping the Hopper on WiFi.
If stable, I'll switch the Hopper to Ethernet.
I'll report the results of this much troubleshooting here....
This sounds like a plan. I am interested to learn how the Dish Hopper can be connected to an Ethernet network and not automatically select it. My Windows laptops seem to switch by themselves the instant a wired connection becomes available. (Sometimes I wind up with a laptop connected to both a wired network and a WiFi connection.)
I really appreciate the effort it takes to deal with this sort of situation. It is patently obvious that connecting a device with Ethernet cannot possibly cause a network device to fail. It is also pretty clear from forum posts that this does happen. It would be a tremendous relief to have an explanation for what can cause this to happen.
