NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
RBK50 keeps dropping 2.4GHz connections
Just unboxed new Orbi + satellite today and went about setting it up to relace a creaking network built out of three different access points (to cover large house & garden). Lots of "2.4GHz only" cli...
FURRYe38 wrote:
What is the Mfr and model# of the ISP modem the NG router is connected too?
What is the size of your home? Sq Ft?
What is the distance between the router and satellite(s)? 30 feet is recommended in between them to begin with depending upon building materials.What channels are you using? Auto? Try setting manual channel 1, 6 or 11 on 2.4Ghz and any unused channel on 5Ghz.
Any Wifi Neighbors near by? If so, how many?....
You probably didn't even read the post. just spamming
Are the devices configured with a fixed IP or do they obtain one from the DHCP server?
if they obtain one I would just try without reservation... or assign a fixed IP outside of the DHCP range
to one of the devices which don't behave normally and see if it still disconnets
I've reconnected Orbis once more to test. This is SO hard to get a grip on. I have some devices (electric imps) that cannot be given fixed IPs - unnecessary anyway as everything is mediated by the cloud agent. These therefore get IPs assigned through DHCP. These are also the most problematic clients. Their logs show frequent disconnections. When they are connecting on the 2.4GHz radio they typically have very strong signals -29 dBm. They are mature WiFi designs and I've not seen any hint of this sort of behaviour before.
The ESP8266 clients are getting their IPs through reservation by MAC address, a preferred method given that I need them at a fixed IP address but one that I can control via the router interface. Being embedded means not easily being able to configure them for a static IP set outside the DHCP pool. We won't call their WiFi implementations mature but again, I've not encountered disconnections like this when they have good signal levels.
The Base and Satellite are separated by exactly 33 feet. Modem details are irrelevant as this is purely a LAN issue. Toggling "Enable Daisy-Chain Topology" hasn't made any difference that I can notice.
You can try this:
Advanced Wireless Settings both 2.4GHz and 5GHz changed CTS/RTS Threshold to 2307.
https://community.netgear.com/t5/Orbi/Orbi-RBR40-RBS40-V2-1-4-16-mesh-network-drops-connection-to/m-p/1601598/highlight/true#M35230
https://community.netgear.com/t5/Orbi/Have-to-keep-rebooting-my-RBR50/m-p/1658603/highlight/false#M44420
Change the CTR/RTS threshold values for both 2.4 GHz and 5 GHz (2341 and 2345 respectively), changed preamble modes to long preamble, and Set 20/40Mhz Coexistence to 40Mhz only.Are these devices the only ones getting disconnections or does everything get disconnected?
Only other thing to do would be to contact NG support and ask for a RMA. Possible that your system is bad. Get it exchanged while you can.
AdrianM wrote:
I've reconnected Orbis once more to test. This is SO hard to get a grip on. I have some devices (electric imps) that cannot be given fixed IPs - unnecessary anyway as everything is mediated by the cloud agent. These therefore get IPs assigned through DHCP. These are also the most problematic clients. Their logs show frequent disconnections. When they are connecting on the 2.4GHz radio they typically have very strong signals -29 dBm. They are mature WiFi designs and I've not seen any hint of this sort of behaviour before.
The ESP8266 clients are getting their IPs through reservation by MAC address, a preferred method given that I need them at a fixed IP address but one that I can control via the router interface. Being embedded means not easily being able to configure them for a static IP set outside the DHCP pool. We won't call their WiFi implementations mature but again, I've not encountered disconnections like this when they have good signal levels.
The Base and Satellite are separated by exactly 33 feet. Modem details are irrelevant as this is purely a LAN issue. Toggling "Enable Daisy-Chain Topology" hasn't made any difference that I can notice.
Most WiFi clients now seem happy after resetting to factory defaults, power cycling everything and waiting plenty of time for base and satellite to sync. There were however still some problems. I think one of the issues was the DHCP reservations which, when applied individually, seem to have a major effect on all clients. It certainly takes a long time for the network to come back up after hitting apply and some clients were failing to reconnect without being power-cycled each time. These were not the clients destined for newly reserved IPs, those obviously needed to get their new addresses by reconnecting.
Also, the default Auto selection for 2.4GHz RF channel was causing a problem due to its habit of picking channel 13 which is ouside the range of the US designed electric imp. I was well aware of this issue so manually selected a lower fixed channel - however, while the Base Orbi responded to this setting change straight away it seems the satellite did not. This only added to the confusion. I've since learned that any setting change may need several minutes to propogate across the system.
Whats the routers IP address pool size? 1.2 thru .254? If it is, I recommend changing it to .100 thru .200. I've also seen various odd DHCP issues including some reservation issues as well here and there.
Making some changes seem to take up to 5 minutes to fully stablize.
