NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Every 2-3 days I lose 90% of my speed on devices connected to the satellite
I've had the the RBR50 for a little over a month. Every 2-3 days, I lose 90% of my speed on any device connected to the satellite. Making any change that reboots the network will speed things up agai...
Thisjustin02 wrote:
I've had the the RBR50 for a little over a month. Every 2-3 days, I lose 90% of my speed on any device connected to the satellite. Making any change that reboots the network will speed things up again for a couple days, then it slows back down. I've connected a computer to the satellite via ethernet when this issue is happening and I get full speed, so it shouldn't be a communication issue between the satellite and the main. Netgear had me change the 2.4 and 5ghz channels, enable MU-MIMO, and enable Fast Roaming. It's only been a a couple hours, and so far, it kind of works? Now any device connected to the satellite is getting 100 Mbps less than the devices connected to the main, which isn't terrible, but....this doesn't make sense to me. Why would changing ANY setting be the solution if everything works at full speed for 1-2 days at a time? Anyone else seen this/have a solution?
What wired devices do you have connected to Orbi? Any mesh speakers (e.g. Sonos)?
I'll try to answer everyone's question at once.
My Orbi is connected to an Arris SURFboard SB6183.
The Orbi is running firmware V2.2.1.210.
I'm using 2.4 ch. 6 and 5.0 ch. 44. These were both previously set to auto, but the issue persists.
There are a ton of networks around me; I'm in a condo.
The main and satellite are probably 40 feet apart.
Again, the part that doen't make any sense is that, via ethernet, I can connect to the satellite at full speed...so I don't see how it could be any of the wireless settings. If my devices connect to the main wirelessly, they work fine.
I've made the changes you suggested, so we'll see how it goes...but I don't think it's going to work.
Thisjustin02 wrote:
The main and satellite are probably 40 feet apart.That might be a stretch in a noisy wifi environment.
Is the satellite at the far extreme of the property, or somewhere in the middle, between the extremities and the main router? The latter is better.
You might try setting the power output levels on the Orbi from 100% to 50% and see if this changes anything. Being in a noise or wifi congested environment can cause problems like this.
You might try turning OFF the Satellite for a short period of time and just test the router alone to see if the problem continues.
Thisjustin02 wrote:
I'll try to answer everyone's question at once.
My Orbi is connected to an Arris SURFboard SB6183.
The Orbi is running firmware V2.2.1.210.
I'm using 2.4 ch. 6 and 5.0 ch. 44. These were both previously set to auto, but the issue persists.
There are a ton of networks around me; I'm in a condo.
The main and satellite are probably 40 feet apart.
Again, the part that doen't make any sense is that, via ethernet, I can connect to the satellite at full speed...so I don't see how it could be any of the wireless settings. If my devices connect to the main wirelessly, they work fine.
I've made the changes you suggested, so we'll see how it goes...but I don't think it's going to work.
It took ten days, but the issue is back. If I connect via ethernet to the satellite, I get full speed. So...I don't think it an issue with the main communicating with the satellite. Otherwise ethernet wouudn't work at full speed. This seems like a firmware issue or something.
Did you try setting the power output levels on the Orbi from 100% to 50% and see if this changes anything. Being in a noisey or wifi congested environment can cause problems like this.
Thisjustin02 wrote:
It took ten days, but the issue is back. If I connect via ethernet to the satellite, I get full speed. So...I don't think it an issue with the main communicating with the satellite. Otherwise ethernet wouudn't work at full speed. This seems like a firmware issue or something.
