NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Orbi RBR850 Extremely Poor Performance
[cross posting from general Orbi forum]
My Orbi system has very poor performance. Symptoms include:
* Extremely poor ping times
* Extremely long dns resolution time
* speedtest still shows full 200Mbps connection rate
* Streaming video is fine but can take a long time to start
* rebooting the orbi and netgear cable modem dailiy seem to have an effect but it could be only psychological.
firmware version V4.6.3.16_2.0.51
I have a 4500 sqft house with 3 floors plus a basement and the walls are plaster and lath. All my wifi tests are performed in the same room as the router but the symptoms are consistent throughout the house. Base station and sattelites are over 30 feet apart with router on the second floor and the sattelites on the opposite sides of the first and third floors. My neighborhood has a lot of WiFi coverage from houses and the city's system but I have my system on two surprisingly empty channels. There are 24 devices currently connected to my network and 3 or 4 I haven't managed to get set back up after the latest factory reset.
Here's a ping sample over wifi:
$ ping 192.168.1.1
PING 192.168.1.1 (192.168.1.1): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
64 bytes from 192.168.1.1: icmp_seq=0 ttl=64 time=2762.054 ms
64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=1761.484 ms
64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=761.153 ms
Here's a ping sample wired to the same device via a switch and cable
$ ping 192.168.1.1
PING 192.168.1.1 (192.168.1.1): 56 data bytes
64 bytes from 192.168.1.1: icmp_seq=0 ttl=64 time=0.627 ms
64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=0.778 ms
64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=0.726 ms
64 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=0.812 ms
Things I have tried:
* daily reboots
* reducing power output
* changing CTS/RTS threshold
* leaving one sattelite off
* enabling/disabling IPv6
* factory reset and re-install
* wired backhaul (sattelites disappear from network map when wired)
18 Replies
BenZvan wrote:
[cross posting from general Orbi forum]
What is the Mfr and model# of the Internet Service Providers modem/ONT the NG router is connected too?
My Orbi system has very poor performance. Symptoms include:
* Extremely poor ping times
* Extremely long dns resolution time
* speedtest still shows full 200Mbps connection rate
* Streaming video is fine but can take a long time to start
* rebooting the orbi and netgear cable modem dailiy seem to have an effect but it could be only psychological.
firmware version V4.6.3.16_2.0.51
I have a 4500 sqft house with 3 floors plus a basement and the walls are plaster and lath. All my wifi tests are performed in the same room as the router but the symptoms are consistent throughout the house. Base station and sattelites are over 30 feet apart with router on the second floor and the sattelites on the opposite sides of the first and third floors. My neighborhood has a lot of WiFi coverage from houses and the city's system but I have my system on two surprisingly empty channels.
What channels are you using?
There are 24 devices currently connected to my network and 3 or 4 I haven't managed to get set back up after the latest factory reset.
What are your results with ALL devices turned OFF, includeing the RBS and leaving just the 1 wired PC ON for testing?
Here's a ping sample over wifi:
$ ping 192.168.1.1
PING 192.168.1.1 (192.168.1.1): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
64 bytes from 192.168.1.1: icmp_seq=0 ttl=64 time=2762.054 ms
64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=1761.484 ms
64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=761.153 msHere's a ping sample wired to the same device via a switch and cable
$ ping 192.168.1.1
PING 192.168.1.1 (192.168.1.1): 56 data bytes
64 bytes from 192.168.1.1: icmp_seq=0 ttl=64 time=0.627 ms
64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=0.778 ms
64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=0.726 ms
64 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=0.812 msThings I have tried:
* daily reboots
* reducing power output
* changing CTS/RTS threshold
* leaving one sattelite off
* enabling/disabling IPv6
* factory reset and re-install
* wired backhaul (sattelites disappear from network map when wired)
Are the RBS directly connected to the back of the RBR or is there a LAN switch in between?
What CAT# cable are you using? CAT6 is recommended.
When i had the wired backhaul set up, it was:
cable modem -> wire -> RBR -> wire -> 24-port switch -> wire -> RBS
The house is wired with cat 6e.
The symptom then was the sattellites wouldn't show up on the network map and all the devices connected to them showed up as "wired" in the list of connected devices. I also had an incident where the sattelites took it upon themselves to disable WPA authentication and leave my WiFi completely open but that hasn't happened again.
BenZvan wrote:
When i had the wired backhaul set up, it was:
What is the Mfr and model# of the Internet Service Providers modem/ONT the NG router is connected too?cable modem -> wire -> RBR -> wire -> 24-port switch -> wire -> RBS
What is the Mfr and model# of the ethernet switch in the configuration?
The house is wired with cat 6e. 5e or 6? There is no 6e.
The symptom then was the sattellites wouldn't show up on the network map and all the devices connected to them showed up as "wired" in the list of connected devices. I also had an incident where the sattelites took it upon themselves to disable WPA authentication and leave my WiFi completely open but that hasn't happened again.
You need to first sync them wirelessly to the RBR and ensure they are FULLY Synced wirelessly. Once the BLUE LED turns OFF and you ensure the security IS setting on the RBS, and status reports GOOD on the RBR, then connect the ethernet cable to the RBS. Lets check your switch first. There are known issues with some switches causing problems.
