NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
XR500 dropping connection constantly
Here it is now 2+ years later than some people have reported these issues, and 2+ months since some of these recent issues; which appear to be the SAME issue - random, infuriating disconnects - my br...
- Netgear are continuing to work on a fix for that issue, in the meantime the best workaround is in LAN Settings, 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 that stops the disconnects.
Update:
My router with the frequent disconnect issues is:
Nighthawk XR500 gaming router - XR 500 V2.3.2.134
DumaOS 3.0.202
fw: V2.3.2.134
Prior - very stable router was a Netgear Nighthawk AC1900 R7000
- Netgear are continuing to work on a fix for that issue, in the meantime the best workaround is in LAN Settings, 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 that stops the disconnects.
AHA - this makes sense, to some degree. For example, Netgear OS should ALWAYS check if DHCP address already is assigned or "in use" by another wired or wireless device & automatically exclude it.
Also, PLEASE provide MUCH BETTER reporting on "duplicate IP" addresses! I did see what appears to be duplicate IPs, and not just in the 1-50 range; for example, a wired device has a specific address, let's say n.n.n.253, but then the Netgear router seems to still try to assign that address, so there's some issues there. Also, we need much better documentation on when/how/where to use 'reserved' IPs? If I reserve an IP on a hardwired device, then Netgear OS should recognize this, without having to also reserve on the router; but I will make sure to do what you said and limit my range of DHCP addresses.
Your reporting showed NOTHING about duplicates and yet, when the .253 address of my physical hardwired device 'disconnected,' i was still able to ping that same n.n.n.253 device - meaning it appears to be a duplicate.
I'll restrict that DHCP IP range and let you know my results - thank you.