NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
**I found a Connection issue Resolution for wired backhaul !! **
Ok so Everytime my power would go out or and update happened/ or any way my orbi system would have to turn off my connection would just die with my rbk53 unit. Mainly because once I had my ethernet wires connected for wired backhaul it would be hours of turning the satalites off / on the router same thing nothing would work till finally hours later or days later it would start working like normal. So I figured out WITHOUT the help of Netgear (they were no help) if you have a wired connection on your orbi unit it will suffer in the begging of booting up. It pretty much doesn’t know if it should go wireless or wired so it would throw off everything on every unit from satalite to router and just become a mess. I have a rbk53 plus a extra rbs50 which is wired backhaul. So the best way to fix this is by RE-STARTING (off/on) THE WIRED SATALITE THEN GO THE ROUTER UNPLUG THE ETHERNET WIRES OUT OF IT (but you can leave the other ends the satalites or devices just remove from router) NOW RE-START THE ROUTER LET IT BOOT UP AND ONCE ITS ALL SET WHICH IS ABOUT 2-3 min HOOK UP THE ETHERNET WIRES BACK IN THE ROUTER AND BOOM! If you try updating like me with all units attached & not doing this process you will be just be stuck turning the unit off / on and it would cripple the system. Its SAD that Netgear has no idea about this. I remember when Ethernet backhaul just started you would hook up the Ethernet cable and everything would stop working. I feel as if theres some bugs they dont know about and people are getting these issues because of the wired Ethernet backhaul. I will contact Netgear support to address them about this and I finally have Internet which is working EXCELLENT!!!!!!! Finally I can say I love my Orbi unit!
Hope this help you guys!
Hope this help you guys!
30 Replies
Replies have been turned off for this discussion
Sevo123,
Thank you so much! Every time my system would restart devices wouldn’t sync I couldn’t access the main Orbi through web interface. I would have factory reset each time.
Today it went into psycho Orbi mode so I unplugged all ethernet plugs going into Main Orbi. Power cycled, waited a few minutes and plugged all ethernet cables back into the main Orbi and BAM! All is good in my Orbihood.
The Orbi system is outstanding when it’s up and running. Thanks again.
- Im So glad I was able to help!
Just curious, any network switches in the mix between the router and satellites?
- Hi, No i dont have any
I had the same issue. Below is what resolved it for me (basically what OP said, but i tried to simplify the instructions a bit). This got me stable after the auto-update recently to the new firmware.
I have an RBK50 (RBR50+RBS50) and an RBS40. My network was basically dead with the orbi after the 2.1.4.10 update. All devices auto-upgraded. A power-cycle as suggested by the known issues did not help. But powering them up in this order seems to have gotten things working great again!
- Power off all orbi gear
- Power on only the RBR50 (Orbi Router). Wait 2-5 minutes.
- Unplug backhaul ethernet cable from RBS40/RBS50 (Orbi Satallite)
- Power on RBS50 or RBS40 (only 1 at a time, just to make sure to be able to keep an eye on each device and make sure network remains stable).
- Login to RBR50, once you see that the RBS40/50 is connected with 5G, wait 2-5 minutes and plug the backhaul cable back in. Wait 2-5 minutes again and you should see the interface switch to wired for the backhaul connection. Monitor network for another 2-5 minutes to ensure things remain working as-expected.
- Repeat steps 4/5 for any additional satellites.
Kewl.
Thanks for posting your process. Hope this helps others. Will keep this in mind.
Another user with a good process:
https://community.netgear.com/t5/Orbi/OrbiOS-2-1-4-availability/m-p/1560759/highlight/true#M29582
I have an RBR50 and two RBS50 units. Tried this with one of the RBS50 units and once I plugged in Ethernet, it basically became unresponsive. Left it for 15 minutes with no change, so I unplugged. Within a minute or two everything came back up just fine.
I test lots of mesh here, most recently the eero and Velop tri-band. Neither of those has any issues using Ethernet backhaul in exactly the same locations/configuration.
I do have several dozen Sonos devices, but that hasn't been an issue with any other mesh.
Any network LAN switches in between the router and satellite? If so, whats the Mfr and model# of these swithces?
DaveHamilton wrote:
I have an RBR50 and two RBS50 units. Tried this with one of the RBS50 units and once I plugged in Ethernet, it basically became unresponsive. Left it for 15 minutes with no change, so I unplugged. Within a minute or two everything came back up just fine.
I test lots of mesh here, most recently the eero and Velop tri-band. Neither of those has any issues using Ethernet backhaul in exactly the same locations/configuration.
I do have several dozen Sonos devices, but that hasn't been an issue with any other mesh.
I have a TrendNet TEG-S16D in between, yes. Straight-ahead, "dumb" Gigabit switch. Passes STP no problem (given that all my Sonos stuff works just fine across it).
FURRYe38 wrote:
Any network LAN switches in between the router and satellite? If so, whats the Mfr and model# of these swithces?
DaveHamilton wrote:
I have an RBR50 and two RBS50 units. Tried this with one of the RBS50 units and once I plugged in Ethernet, it basically became unresponsive. Left it for 15 minutes with no change, so I unplugged. Within a minute or two everything came back up just fine.
I test lots of mesh here, most recently the eero and Velop tri-band. Neither of those has any issues using Ethernet backhaul in exactly the same locations/configuration.
I do have several dozen Sonos devices, but that hasn't been an issue with any other mesh.
