NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
djsquared69
Oct 26, 2021Initiate
xr1000 slow 2.4 and won't connect to Ring devices
Hey everyone Just upgraded from my A1900 Nighthawk to the XR1000. Everything was able to connect and worked fine except my ring devices. I have purposly set up a 2.4 guest wifi for the cameras to go...
chadamski
Feb 04, 2022Aspirant
I have this same problem. The 2.4 band just stops accepting connections from certain smart home devices for hours at a time, then usually eventually corrects itself. Extremely annoying and inexcusable for such an expensive router.
Netduma-Liam
Feb 04, 2022NetDuma Partner
As Fraser mentioned above, please set NAT to Open in WAN Settings, also make the antennae on the router look like this _ | | _ for optimum range. Disable Smart Connect for WiFi and see if you're then getting more consistent connectivity out of them.
- chadamskiFeb 04, 2022Aspirant
Uh, yeah. I've tried everything in this thread. And everything in all of the other threads. It's still a persistent issue, unfortunately.
- Netduma-FraserFeb 04, 2022NetDuma PartnerSet the DHCP range to start at .50, then assign reserved IP addresses to devices between .2 & .49 so they're out of the DHCP range, apply, reboot from the interface, wait 2 minutes and see if resolves the issue
- chadamskiFeb 04, 2022Aspirant
Netduma-Fraser wrote:
Set the DHCP range to start at .50, then assign reserved IP addresses to devices between .2 & .49 so they're out of the DHCP range, apply, reboot from the interface, wait 2 minutes and see if resolves the issueYeh, I've also tried this, as well as a few other DHCP configurations, just to make sure. The router still just randomly drops the entire 2.4ghz band. During these periods, the band sometimes fails to show up even in the Nighthawk app on my phone. My smart home devices regularly drop connection, even when IP addresses are reserved. In addition, this router randomly and frequently resets itself to factory on reboot, even just a soft restart (not from a power outage, though outages also cause factory resets), so it's been a pretty frustrating thing to try to diagnose.