Netgear C7000v2 disconnects every 2 hours

Question

Hello, I'm connected through a C7000v2, and about every two hours, all of our devices lose internet for about 2 minutes, then it comes back without any action on my part. This happens to my wired PC and the wifi devices, and though all the lights on the router stay on (it does not seem to reset), I am also unable to connect to the router itself by accessing 192.168.1.1 until everything comes back.

Time	Priority	Description
2023-4-8, 08:13:48	Notice (6)	Honoring MDD; IP provisioning mode = IPv6
2023-4-8, 08:13:32	Critical (3)	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=44:a5:6e:35:d5:20;CMTS-MAC=00:90:f0:2c:04:00;CM-QOS=1.1;CM-VER=3.0;
2023-4-8, 08:12:27	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=44:a5:6e:35:d5:20;CMTS-MAC=00:90:f0:2c:04:00;CM-QOS=1.1;CM-VER=3.0;
2023-4-8, 08:12:27	Warning (5)	MDD message timeout;CM-MAC=44:a5:6e:35:d5:20;CMTS-MAC=00:90:f0:2c:04:00;CM-QOS=1.1;CM-VER=3.0;
2023-4-8, 07:12:25	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=44:a5:6e:35:d5:20;CMTS-MAC=00:90:f0:2c:04:00;CM-QOS=1.1;CM-VER=3.0;
2023-4-8, 06:20:03	Notice (6)	Honoring MDD; IP provisioning mode = IPv6
2023-4-8, 06:19:46	Critical (3)	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=44:a5:6e:35:d5:20;CMTS-MAC=00:90:f0:2c:04:00;CM-QOS=1.1;CM-VER=3.0;
2023-4-8, 06:18:41	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=44:a5:6e:35:d5:20;CMTS-MAC=00:90:f0:2c:04:00;CM-QOS=1.1;CM-VER=3.0;
2023-4-8, 06:18:41	Warning (5)	MDD message timeout;CM-MAC=44:a5:6e:35:d5:20;CMTS-MAC=00:90:f0:2c:04:00;CM-QOS=1.1;CM-VER=3.0;
2023-4-8, 04:13:32	Notice (6)	Honoring MDD; IP provisioning mode = IPv6
2023-4-8, 04:13:16	Critical (3)	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=44:a5:6e:35:d5:20;CMTS-MAC=00:90:f0:2c:04:00;CM-QOS=1.1;CM-VER=3.0;
2023-4-8, 04:12:11	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=44:a5:6e:35:d5:20;CMTS-MAC=00:90:f0:2c:04:00;CM-QOS=1.1;CM-VER=3.0;
2023-4-8, 04:12:10	Warning (5)	MDD message timeout;CM-MAC=44:a5:6e:35:d5:20;CMTS-MAC=00:90:f0:2c:04:00;CM-QOS=1.1;CM-VER=3.0;
2023-4-8, 02:07:18	Notice (6)	Honoring MDD; IP provisioning mode = IPv6
2023-4-8, 02:07:01	Critical (3)	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=44:a5:6e:35:d5:20;CMTS-MAC=00:90:f0:2c:04:00;CM-QOS=1.1;CM-VER=3.0;
2023-4-8, 02:05:56	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=44:a5:6e:35:d5:20;CMTS-MAC=00:90:f0:2c:04:00;CM-QOS=1.1;CM-VER=3.0;
2023-4-8, 02:05:56	Warning (5)	MDD message timeout;CM-MAC=44:a5:6e:35:d5:20;CMTS-MAC=00:90:f0:2c:04:00;CM-QOS=1.1;CM-VER=3.0;
2023-4-8, 00:11:29	Notice (6)	Honoring MDD; IP provisioning mode = IPv6
2023-4-8, 00:11:13	Critical (3)	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=44:a5:6e:35:d5:20;CMTS-MAC=00:90:f0:2c:04:00;CM-QOS=1.1;CM-VER=3.0;
2023-4-8, 00:10:08	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=44:a5:6e:35:d5:20;CMTS-MAC=00:90:f0:2c:04:00;CM-QOS=1.1;CM-VER=3.0;
2023-4-8, 00:10:08	Warning (5)	MDD message timeout;CM-MAC=44:a5:6e:35:d5:20;CMTS-MAC=00:90:f0:2c:04:00;CM-QOS=1.1;CM-VER=3.0;
2023-4-7, 22:06:13	Notice (6)	Honoring MDD; IP provisioning mode = IPv6
2023-4-7, 22:05:56	Critical (3)	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=44:a5:6e:35:d5:20;CMTS-MAC=00:90:f0:2c:04:00;CM-QOS=1.1;CM-VER=3.0;
2023-4-7, 22:04:52	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=44:a5:6e:35:d5:20;CMTS-MAC=00:90:f0:2c:04:00;CM-QOS=1.1;CM-VER=3.0;
2023-4-7, 22:04:52	Warning (5)	MDD message timeout;CM-MAC=44:a5:6e:35:d5:20;CMTS-MAC=00:90:f0:2c:04:00;CM-QOS=1.1;CM-VER=3.0;
2023-4-7, 19:53:35	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=44:a5:6e:35:d5:20;CMTS-MAC=00:90:f0:2c:04:00;CM-QOS=1.1;CM-VER=3.0;
2023-4-7, 19:53:35	Warning (5)	MDD message timeout;CM-MAC=44:a5:6e:35:d5:20;CMTS-MAC=00:90:f0:2c:04:00;CM-QOS=1.1;CM-VER=3.0;
2023-4-7, 17:56:42	Notice (6)	Honoring MDD; IP provisioning mode = IPv6
2023-4-7, 17:56:26	Critical (3)	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=44:a5:6e:35:d5:20;CMTS-MAC=00:90:f0:2c:04:00;CM-QOS=1.1;CM-VER=3.0;
2023-4-7, 17:55:21	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=44:a5:6e:35:d5:20;CMTS-MAC=00:90:f0:2c:04:00;CM-QOS=1.1;CM-VER=3.0;
2023-4-7, 17:55:21	Warning (5)	MDD message timeout;CM-MAC=44:a5:6e:35:d5:20;CMTS-MAC=00:90:f0:2c:04:00;CM-QOS=1.1;CM-VER=3.0;
2023-4-7, 16:00:39	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=44:a5:6e:35:d5:20;CMTS-MAC=00:90:f0:2c:04:00;CM-QOS=1.1;CM-VER=3.0;
2023-4-7, 16:00:39	Warning (5)	MDD message timeout;CM-MAC=44:a5:6e:35:d5:20;CMTS-MAC=00:90:f0:2c:04:00;CM-QOS=1.1;CM-VER=3.0;
2023-4-7, 13:59:10	Notice (6)	Honoring MDD; IP provisioning mode = IPv6
2023-4-7, 13:58:47	Critical (3)	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=44:a5:6e:35:d5:20;CMTS-MAC=00:90:f0:2c:04:00;CM-QOS=1.1;CM-VER=3.0;
2023-4-7, 13:57:43	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=44:a5:6e:35:d5:20;CMTS-MAC=00:90:f0:2c:04:00;CM-QOS=1.1;CM-VER=3.0;
2023-4-7, 13:57:42	Warning (5)	MDD message timeout;CM-MAC=44:a5:6e:35:d5:20;CMTS-MAC=00:90:f0:2c:04:00;CM-QOS=1.1;CM-VER=3.0;
2023-4-7, 11:52:32	Notice (6)	Honoring MDD; IP provisioning mode = IPv6
2023-4-7, 11:52:13	Critical (3)	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=44:a5:6e:35:d5:20;CMTS-MAC=00:90:f0:2c:04:00;CM-QOS=1.1;CM-VER=3.0;
2023-4-7, 11:51:08	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=44:a5:6e:35:d5:20;CMTS-MAC=00:90:f0:2c:04:00;CM-QOS=1.1;CM-VER=3.0;

FURRYe38 · Answer

Please post a copy and paste of the modems connection status&nbsp; page.https://kb.netgear.com/30007/How-do-I-obtain-the-cable-connection-information-from-a-NETGEAR-cable-modem-modem-router
&nbsp;
Any Criticals, Errors or Warnings needs to be reviewed by the ISP and resolved by&nbsp; them.
Have the ISP check the signal and line quality UP to the modem.&nbsp;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.&nbsp;Be sure your using good quality RG6 coax cable up to the modem.&nbsp;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#M12853https://kb.netgear.com/24311/Power-level-guidelines-for-a-NETGEAR-cable-modem-routerhttps://www.duckware.com/tech/solving-intermittent-cable-modem-issues.html
&nbsp;

TheThirdDuke · Answer

lol

FURRYe38 · Answer

Whats funny?&nbsp;

plemans · Answer

Your logs are indicating a line issue. You can do some checking/work on your own.&nbsp;
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. If you can, simply connect the modem right where the coax comes into the home. This prevents wiring in the home from being the issue. And some ISP’s charge if the wiring issue is in the home. So this helps prevent this.
If that doesn't help, your cable connections page does help so we can give you better idea's of what could be going on.&nbsp;
And it can tell us if its something you might be able to fix or if the ISP needs to check it.&nbsp;

Forum Discussion

Netgear C7000v2 disconnects every 2 hours

4 Replies