NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
XR1000v2 Randomly Loses Internet, requires reboot
Twice in the last two days this has occurred. My router will stop providing internet access to all devices, wired and wireless. Restarting the router via the power button restores access. My ...
- It does not, the internet LED remains white. The router simply becomes unresponsive to clients although it can still be pinged.
- I'm using Shielded CAT 8 from modem to router
- My Modem is a Netgear Nighthawk CM1200
- I purchased the router maybe 1 month ago. It was already factory reset and then I updated the firmware to the latest
What devices do you have all connected to it?
What is the default DHCP IP address pool range now? I recommend using .100 thru .200.
How is the WiFi settings configured? Basic and Advanced menus please.
Can you please post the following from the CM modem:
Please post a copy and paste of the modems connection status and event log page.
https://kb.netgear.com/30007/How-do-I-obtain-the-cable-connection-information-from-a-NETGEAR-cable-modem-modem-router
https://kb.netgear.com/30008/How-do-I-view-or-clear-the-event-logs-on-my-NETGEAR-cable-modem-or-modem-router
Be sure to disable any MAC Address randomizers on phones and pads while at home:
https://community.netgear.com/t5/Nighthawk-App/NETGEAR-Mobile-Applications-and-Apple-Devices-FAQ/td-p/2220015/jump-to/first-unread-message
I'm using 192.168.0.21-254. I dont use any DHCP reservations, nor would an IP conflict cause my entire network to lock up;
Also keep in mind this impacted both wireless and wired clients.
My last lock up occured around 9:10am CST. Looking at my modem logs which i believe are in UTC, i do not see any events around that time.
Cable Connection Stats (Keep in mind i did not have to restart modem to resolve issue):Please try DHCP IP address range .100 to .200 on the XR router.
Any Criticals, Errors or Warnings seen in the event logs needs to be reviewed and resolved by the ISP. Indicates a signal issue on the ISP line up to the modem.
Signal Power is too high on the modem. You'll end up burning it up:
https://kb.netgear.com/24311/Power-level-guidelines-for-a-NETGEAR-cable-modem-router
I see lots of correctables and un-correctables that should be zeros.
Have the ISP check the signal and line quality UP to the modem. Be sure the ISP provisions the modem correctly.
Be sure there are no coax cable line splitters in the between the modem and ISP service box.
Be sure your using good quality RG6 coax cable up to the modem.
Start with removing any amplifiers, signal attenuators, or splitters from the coax.
From there check the line for kinks, damage, moisture in the line.
Check the connectors for improperly made ends, foil touching the copper coax line, loose connections, bad/old/cheap connectors, or corroded connections. Replace them if you do.
Be sure to power OFF the modem for 1 minute then back ON.
https://community.netgear.com/t5/Cable-Modems-Routers/General-info-and-Troubleshooting-for-Cable-Modems/m-p/1530376#M12853
https://www.duckware.com/tech/solving-intermittent-cable-modem-issues.html
https://highspeed.tips/docsis-events/So you're blaming the modem for the issues with the router? The DumaOS web UI is completely unavailable during the outage. Why would a modem connected via ethernet have the ability to lock up an entire operating system of another device?
I appreciate your help but this seems a little farfetched. I'll try a factory reset and your DHCP ranges later this weekend when I have time though