NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
New - XR1000 Firmware Version 1.0.0.68 Released
NOTE: This FW is for Version 1 of the XR1000 gaming router line. This version of FW is NOT compatible with hardware Version 2 of the XR1000 router series product line. The label under the router sho...
- Looks like the issue for me is something to do with DHCP (yes I had the range set as 100-200) I set up my own DHCP server and set the lease time to 1 week and it's been stable ever since
What channel configurations are currently set on the router?
Try setting manual channel 1 on 2.4Ghz and 40 channel on 5Ghz.
Any Wifi Neighbors near by? If so, how many?
How is the Adavanced Wireless settings configured on the XR router?
What is the Mfr and model# of the Internet Service Providers modem/ONT the NG router is connected too?
Be sure your using a good quality LAN cable between the modem and router. CAT6 is recommended.
laneyy wrote:
I'm having the same issue with random disconnects too. Mainly noticing on my Google home hubs because the screen shows no internet but then will connect again themself later. Settings haven't changed and I have done a factory reset since upgrading firmware. Honestly thinking about going back to my old Asus RT66U because that just worked and I've had nothing but issues with the XR1000 since day one
Looks like the issue for me is something to do with DHCP (yes I had the range set as 100-200) I set up my own DHCP server and set the lease time to 1 week and it's been stable ever since
- Thanks for the update, good to know our theory is correct, it is something we've passed on before and will have to wait for NG to fix.
Hey Fraser. Would you mind explaining what is happening in regard to the DHCP issue? What is the rationale behind changing the range? What problems is it causing, etc.
Thanks for your time.
- Raustal sure thing, so the issue as far as I can tell is that when the DHCP lease renews it's kicking devices offline, now this isn't unusual if a device is getting a new IP but it should reconnect so quickly that it shouldn't be noticeable at all but that isn't happening. Leading me to believe there is an issue with the lease aspect of DHCP. Adjusting the range to a higher value provides a block of IP addresses that are unaffected by the lease, setting these as reserved for devices means they'll never change IP addresses.
You may think then that changing the range shouldn't matter but for some reason it still occurs if the IPs are within the range.
