NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
XR500 Router Intermittent Disconnections (Please help)
Router is less than a year old, has latest firmware that has been properly installed.
I am not sure why my router disconnects from the internet at random times throughout the day/night. Everything else has no issues except the router; my ISP has not had any issues, my modem works very well, etc. Has anyone else been experiencing this issue? I have tried every logical solution and am curious if someone can help, thanks.
Also: yes, I have plugged it into a different outlet by itself and that has not done anything. I might replace the outlet if no one has any other ideas. The cables are all correct and are working properly.
14 Replies
What Firmware version is currently loaded?
What is the Mfr and model# of the Internet Service Providers modem/ONT the NG router is connected too?Has a factory reset and setup from scratch been performed since last FW update? A complete pull of the power adapter for a period of time after the factory reset then walk thru the setup wizard and setup from scratch. Also power OFF the ISP modem for 1 minute then back On. Complete the setup wizard.
The firmware is 2.3.2.130.
The modem is a Netgear CM1000; the modem works very well and I have had no issues with it. When connecting my computer directly to the modem, I experience no disconnects and all of the lights are illuminated green.
The router has been factory reset from within the DumaOS app. This issue has occured in the prior 3 beta firmware updates (I have dealth with this for a few months).
I did reboot both the modem and router after factory resetting for the firmware update (I've done this 3 times now. The issue remains the exact same). I also periodically reboot the modem and router by shutting off and pulling the cord for a minute.
Is there anything else I should try? I really don't know what to do.
- In addition to the above suggestions, changing the DHCP pool to start at a higher value e.g. 50 instead of 2 and then giving devices reserved IPs between .2 - .49 can help resolve the issue.
- Unlikely as it was present on that version also, couldn't say exactly, hopefully for the next version
