NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Orbi RBR50 + Sats refusing some device connections(ecobee & tplink Kasa Cams)
For about 8 months now I've had tremendous success with the Orbi and its 2 satellites. The number of devices simultaneously connected to the network number in the 30's. For 8 months, I've had no issues at all until tonight.
When I came home, I noticed that my 4 smart wifi switches were all disconnected and then I noticed that 2 out of 4 of my wireless Kasa cams were as well. Determining that the common issue was the Orbi. I rebooted Orbi and its satellites and I was able to connect the switches although it took an unusually long time. I noted that it didn't appear as if any new firmware updates had taken place and the satellites were connecting fine.
With that being said, I noticed that I could no longer connect the TP link Kasa cameras and an additional 2 ecobee devices could no longer connect, although a 3rd device had no issues.
I am on firmware V2.2.1.210 for all 3 Orbi devices. DHCP is on. Daisy Chain is off. Channel is Auto. Implicit Beamforming is enabled. For the most part, no settings were changed and I don't believe that any new devices have been introduced recently.
Any way to determine why the devices that were connected so readily yesterday no longer have the ability to connect today such as my Kasa Cams?
- Ok, I backed up my settings, reset the router and restored the settings and voila, I am now able to connect my Kasa Cams! So, I guess the problem was that something just went haywire and it needed to be fully reset to get back to working again.
16 Replies
What is the Mfr and model # of these smart switchs? Orbi seems to have some issues with manged, smart or green ethernet switches. Can you try the Orbi system with out the switches i the mix for a while to see if the problem continues
When you say Daisy chain is disbled, is the check mark uncheck next to the check box or is it checked? If you updated to recent FW v.210, try enabling Daisy Chain. Some have mentioned that this seems to be working in reverse order, enabling means disabled actually.
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.Try setting manual channel 1, 6 or 11 on 2.4Ghz and any unused channel on 5Ghz.
- My wall switches are Meross MSS510. My home is 3700 sq ft and I have 2 satellites. Daisy Chain is not checked and the network topology looks like the setting is indeed off. Network signal looks good. What doesn't seem to be happening is that the router isn't providing an ip address to select devices that are working fine this morning.
I see what your referring to in regards to your device.
What is the distance between the base 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?
What WPA security modes are you using? Try WPA then see if WPA2 only works betterTry disabling the following and see:
MIMO, Daisy Chain, Fast Roaming, IPv6 and Set 20/40Mhz Coexistence to 40Mhz only. Save settings and reboot the router and satellite(s).
I'm going to take this in a completely different direction and ask whether you have access control enabled (under advanced > security > access control), and, if so, whether you have the access rule set to allow or block new devices? There are issues with access control on this firmware version that can cause allowed devices to be erroneously blocked. Check the settings, and if access control is enabled, check whether the problem devices are listed as blocked. You can try changing them to allowed, but you may need to either set the default rule to allow new devices, or, failing that, disable access control altogether.
Hopefully, this will be resolved in future firmware updates. If you've checked, or access control is disabled, then disregard. It's just something that occurred to me that I haven't seen mentioned so far in this thread.
randomousity wrote:
I'm going to take this in a completely different direction and ask whether you have access control enabled (under advanced > security > access control), and, if so, whether you have the access rule set to allow or block new devices? There are issues with access control on this firmware version that can cause allowed devices to be erroneously blocked. Check the settings, and if access control is enabled, check whether the problem devices are listed as blocked. You can try changing them to allowed, but you may need to either set the default rule to allow new devices, or, failing that, disable access control altogether.
Hopefully, this will be resolved in future firmware updates. If you've checked, or access control is disabled, then disregard. It's just something that occurred to me that I haven't seen mentioned so far in this thread.
Thank you for considering this. It looks like all new devices are allowed and nothing seems to be blocked at the device level.
- Ok, I backed up my settings, reset the router and restored the settings and voila, I am now able to connect my Kasa Cams! So, I guess the problem was that something just went haywire and it needed to be fully reset to get back to working again.
