NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
RBR50 FW v2.1.4.16 broke my ethernet backhaul with two RBS50 that previously worked for a year
Firmware v2.1.4.16 broke my system. finally, after many hours! and a complete system reset, figured out it was the ethernet backhaul and disconnected the ethernet cables to the satellites.
Backhaul works wirelessly now but one satalite, in the living room so sorta important!, has a "poor" wireless connection. On the weekend, I'll try to reconnect via ethernet.
Shouldn't have to spend so much time fixing a stable setup (or any setup really)
Honestly, I don't think it is the hardware. I'm only guessing though. My scenario is almost identical to yours, but a different layout in the house. LUCKILY Costco will refund your money! I kid you not, I just returned my system from last December and bought a new one to test it out. Unfortuantely the results were the same. I'm on my third now, which exhibit the same issues. I hoping it will last with this last hard reset, but my confidence level is very, very low.
15 Replies
After updating FW, the satellites should have been updated first, then the router. If you reset the router and satellites, you need to re-add the satelites via wiress first, one at a time, wait for the top led to turn on BLUE, then connect the wired LAN cable between the router and satellite, wait 5 miniutes, the top led will turn on PINK then BLUE. If you can get to this point, then do the same thing for the 2nd satellite. Re-add wirelessly, wait, connect wired, then wait.
Any network LAN switches in between the router and satellites?
- Many thanks for the speedy reply. I used the latest version of the iPhone app to update the firmware. In other words I tapped the “update firmware” button. There wasn’t an option or instruction to update the satellites first, then the router, then reconnect wirelessly then re-add Ethernet one at a time. How was I to know this? Sorry. I don’t mean this to be a snarky as it is sounding. I’m really describing what I did and then asking an honest question. Yes, I have three unmanaged switched at various points of my network. Usu try to use Ethernet over WiFi where I can. Thank you again.
If you don't think the FW update was a good installation, you can always manually download and install the FW to the satellites and router then reset an setup from scratch. Yes, the orbi app should work however doing FW updates is a important operation and for me personally, I'd rather not leave anything to chance. Wired PC with the satellites and routers for FW updates is the best way to update FW.
For Review:
So, in the end, FURRYe38's solution did NOT solve the problem. Initially, it worked -- two satellites added, both showing as a wired connection. However, on reboot, the two satellites are listed as connected devices albeit wired. And now as I write this one satellite moved to the satellite section by connected via 5G, not ethernet. Really did not want to spend my Saturday working on WiFi.
So with the LAN cable still connected the satellite is displayed in the connecte clients list on the router as wireless and not wired?
Was Daisy Chain enabled or disabled on the router?
One thing I would try, as I don't see that it may have been done, do a factory reset on the router and sateliltes, set the router and satellites up from scratch, add 1 satellites via wireless at a time until you get top led to turn on BLUE, then connect the LAN cable in between the 1st satellite and wait for it to turn on BLUE again. Then same thing for the 2nd satellite.
Only other idea is you could try reverting back to v.10 version of FW on the router and satellites....
A question on why should the solution to that the user has to let the router detect the satellite wirelessly?
Isnt it better to detect wired first and use wired as the backhaul rather than endlessly find the satellite via wirelessly?
Unless the wired has a problem, then only use the wireless.
I am having similar issues. But I have done even more troubleshooting and this is irritating me to no end. Long story short, I started with one RBR50, was convinced that was bad so I had it exchanged last week for another one but it did the same thing. So then I decided, let's go with the RBR40 and take advantage of the fact I can get it for 4 router/satellites for the same as the previous 3. But I'm back to square one. If I watch the status it is just jumping between working for a minute, then I see it is doing a "Config Sync", the network goes down and the process just keeps repeating itself. I too have a wired backhaul as I know there are signal issues in this old lat and plaster (using chicken mesh) walled house. That's the whole reason I went to the Orbi system.
So, my question: Are you telling me that if you can't set this up using wireless first, it won't work?? Is it a safe presumtion that you have to set-up the system, the wireless backhaul kicks off first and after that handshake is made it will look at a wired connection? That would really surprise and even worse, disappoint me. That seems backwards.
I would contact NG support and ask for more help and information about this. Ask for an RMA if you feel you can't keep the system working. There maybe something wrong with the HW.
Honestly, I don't think it is the hardware. I'm only guessing though. My scenario is almost identical to yours, but a different layout in the house. LUCKILY Costco will refund your money! I kid you not, I just returned my system from last December and bought a new one to test it out. Unfortuantely the results were the same. I'm on my third now, which exhibit the same issues. I hoping it will last with this last hard reset, but my confidence level is very, very low.
Were hoping so:
https://community.netgear.com/t5/Orbi/Orbi-restart-issues/m-p/1610805/highlight/true#M37867
cvoisey wrote:
Honestly, I don't think it is the hardware. I'm only guessing though. My scenario is almost identical to yours, but a different layout in the house. LUCKILY Costco will refund your money! I kid you not, I just returned my system from last December and bought a new one to test it out. Unfortuantely the results were the same. I'm on my third now, which exhibit the same issues. I hoping it will last with this last hard reset, but my confidence level is very, very low.
