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 wi...
Just curious, any network switches in the mix between the router and satellites?
FURRYe38 wrote:
Just curious, any network switches in the mix between the router and satellites?
Yes I do go through a switch.
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.
wziemer wrote:
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!
Thanks! I had the same problem with my RBK20 using Ethernet backhaul after the automatic update to 2.1.4.10. Following your procedure I finally managed to update to 2.1.4.10 without breaking my whole network. Both Orbis are running fine for 12+ hours.
Whats the Mfr and model# of this swtich? There are some issues with using switches. Managed swtiches seem to cause problems. One user found that if you have a managed switch, you need to disable IGMP protocols. This may help on managed switches. I use two unmanged swithces between my 1 satellite and router. No problems...so far.
Dsdeck wrote:
FURRYe38 wrote:
Just curious, any network switches in the mix between the router and satellites?
Yes I do go through a switch.Thank you very much for your directions.
I just installed brand new RBK53 system with wired backhaul satellite connection. Initially, when I've wired satellite it did not work, but after reading this post and follow instructions it worked.
However, when I disconnected satellite from power (needed to use different outlet) and powered it up again, it stopped working and I needed to perform the same procedure.
So my question is - what will happen after power outage? Do I need to go thru same procedure?
I'm concerned about it, because I have home and media automation systems and if I am not at home it will be stacked. Any ideas?
Regards
I purchased the RBK53 kit from CostCo yesterday. I immediately updated the firmware which proved to be a challenge. One of the satellites refused to report the firmware version back to the router, so it just sat with the "please wait a moment message". At this point, all three units were in the same room about 15ft. apart, and they were still having trouble communicating. After several restarts, I finally managed to get them updated (v2.1.4.10) at which point I started the process of placing them in my home and configuring. Let's just say that it took several hours and starting over multiple times to get to a place where all units are communicating and using wired haulback. I did this by following the steps outlined earlier in the thread, and being very patient.
I wanted to point out a couple of things that I've observed during this setup process and during the post-setup testing to see if anyone has suggestions:
1. The overall coverage area of each unit seems to be very small with little ability to trasmit through walls. I have a Nighthawk R7500 single router that seems to provide better coverage and faster speeds than all three of the Orbi units.
2. Once switched to wired haulback, the satellites do not seem to be able to communicate firmware version back to the router. That screen simply hangs, which implies that firmware updates will require moving all of the satellites closer together and leveraging wireless haulback.
3. When a client is connecting through a satellite the process of joining the wifi network fails with an incorrect password message even when the password is correct. Moving to the room with the router allows the user to join the network with the same password.
4. The Orbi iOS app fails to find the Orbi system when launching through a satellite, but does work when in the room with the router.
Any suggestions? I'm hoping that a firmware update will fix most of this stuff. If not, I will be taking advantage of CostCo's return policy.
- Thanks for letting me know. It's a TP-Link un-managed gigabit switch. Maybe that's the problem?
If it's un-managed it shouldn't be. Be sure to confirm it's unmanaged. Whats the model # of it.
Also could be bad cabling as well.
Could be a bad switch, you would have to try a different switch and test. Could be various things when it comes to switches.
I'm using a older inexpesive NG non managed Gb switch and a mid level non managed HP Gb switch in between mine...working so far since installing the system.
I would run a test, directly connet 1 Satellite to the back of the Orbi router and see if you exhibit the same problems or not. Be sure to use good quality LAN cabling. CAT 6 recommneded. if probllem still happens here as well, you may have a bad unit which would need to be RMAd.
Dsdeck wrote:
Thanks for letting me know. It's a TP-Link un-managed gigabit switch. Maybe that's the problem?
