Community Forum

Modem Keeps Resetting even after Tech Visit

Highlighted
Frequent Visitor

Modem Keeps Resetting even after Tech Visit

Things have been working for months without any real issue.  All of a sudden I am having modem reset issues pretty frequently.  The TV doesn't go out but the modem seems to reset and dropping my connection.  A tech came on sight today to check things out and didn't see any issues despite witnessing the drop outs.  Said signal is clean and strong.  Not sure what to do now.  Need the service for work.

 

Here is a log from the Netgear Gateway C7800 from just today:

 

Time Priority Description
2020-07-14, 13:46:32 Notice (6) Honoring MDD; IP provisioning mode = IPv6
2020-07-14, 13:46:28 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=08:36:c9:cc:a4:a8;CMTS-MAC=00:01:5c:b3:b2:72;CM-QOS=1.1;CM-VER=3.1;
2020-07-14, 13:46:18 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=08:36:c9:cc:a4:a8;CMTS-MAC=00:01:5c:b3:b2:72;CM-QOS=1.1;CM-VER=3.1;
2020-07-14, 13:46:18 Warning (5) MDD message timeout;CM-MAC=08:36:c9:cc:a4:a8;CMTS-MAC=00:01:5c:b3:b2:72;CM-QOS=1.1;CM-VER=3.1;
2020-07-14, 13:46:15 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=08:36:c9:cc:a4:a8;CMTS-MAC=00:01:5c:b3:b2:72;CM-QOS=1.1;CM-VER=3.1;
2020-07-14, 13:46:00 Warning (5) MDD message timeout;CM-MAC=08:36:c9:cc:a4:a8;CMTS-MAC=00:01:5c:b3:b2:72;CM-QOS=1.1;CM-VER=3.1;
2020-07-14, 13:45:31 Notice (6) Honoring MDD; IP provisioning mode = IPv6
2020-07-14, 13:45:20 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=08:36:c9:cc:a4:a8;CMTS-MAC=00:01:5c:b3:b2:72;CM-QOS=1.1;CM-VER=3.1;
2020-07-14, 13:45:15 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=08:36:c9:cc:a4:a8;CMTS-MAC=00:01:5c:b3:b2:72;CM-QOS=1.1;CM-VER=3.1;
2020-07-14, 13:45:14 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=08:36:c9:cc:a4:a8;CMTS-MAC=00:01:5c:b3:b2:72;CM-QOS=1.1;CM-VER=3.1;
2020-07-14, 13:41:50 Warning (5) MDD message timeout;CM-MAC=08:36:c9:cc:a4:a8;CMTS-MAC=00:01:5c:b3:b2:72;CM-QOS=1.1;CM-VER=3.1;
2020-07-14, 13:38:24 Notice (6) Honoring MDD; IP provisioning mode = IPv6
2020-07-14, 13:38:12 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=08:36:c9:cc:a4:a8;CMTS-MAC=00:01:5c:b3:b2:72;CM-QOS=1.1;CM-VER=3.1;
2020-07-14, 13:38:12 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=08:36:c9:cc:a4:a8;CMTS-MAC=00:01:5c:b3:b2:72;CM-QOS=1.1;CM-VER=3.1;
2020-07-14, 13:38:11 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=08:36:c9:cc:a4:a8;CMTS-MAC=00:01:5c:b3:b2:72;CM-QOS=1.1;CM-VER=3.1;
2020-07-14, 13:38:11 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=08:36:c9:cc:a4:a8;CMTS-MAC=00:01:5c:b3:b2:72;CM-QOS=1.1;CM-VER=3.1;
2020-07-14, 13:38:11 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=08:36:c9:cc:a4:a8;CMTS-MAC=00:01:5c:b3:b2:72;CM-QOS=1.1;CM-VER=3.1;
2020-07-14, 13:34:14 Warning (5) MDD message timeout;CM-MAC=08:36:c9:cc:a4:a8;CMTS-MAC=00:01:5c:b3:b2:72;CM-QOS=1.1;CM-VER=3.1;
2020-07-14, 13:34:04 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:cc:a4:a8;CMTS-MAC=00:01:5c:b3:b2:72;CM-QOS=1.1;CM-VER=3.1;
2020-07-14, 13:34:04 Warning (5) MDD message timeout;CM-MAC=08:36:c9:cc:a4:a8;CMTS-MAC=00:01:5c:b3:b2:72;CM-QOS=1.1;CM-VER=3.1;
2020-07-14, 13:34:03 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:cc:a4:a8;CMTS-MAC=00:01:5c:b3:b2:72;CM-QOS=1.1;CM-VER=3.1;
2020-07-14, 13:34:02 Warning (5) MDD message timeout;CM-MAC=08:36:c9:cc:a4:a8;CMTS-MAC=00:01:5c:b3:b2:72;CM-QOS=1.1;CM-VER=3.1;
2020-07-14, 13:34:00 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:cc:a4:a8;CMTS-MAC=00:01:5c:b3:b2:72;CM-QOS=1.1;CM-VER=3.1;
2020-07-14, 13:33:32 Warning (5) MDD message timeout;CM-MAC=08:36:c9:cc:a4:a8;CMTS-MAC=00:01:5c:b3:b2:72;CM-QOS=1.1;CM-VER=3.1;
2020-07-14, 13:31:11 Notice (6) Honoring MDD; IP provisioning mode = IPv6
2020-07-14, 13:31:01 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=08:36:c9:cc:a4:a8;CMTS-MAC=00:01:5c:b3:b2:72;CM-QOS=1.1;CM-VER=3.1;
2020-07-14, 13:31:00 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=08:36:c9:cc:a4:a8;CMTS-MAC=00:01:5c:b3:b2:72;CM-QOS=1.1;CM-VER=3.1;
2020-07-14, 13:31:00 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=08:36:c9:cc:a4:a8;CMTS-MAC=00:01:5c:b3:b2:72;CM-QOS=1.1;CM-VER=3.1;
2020-07-14, 13:30:56 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=08:36:c9:cc:a4:a8;CMTS-MAC=00:01:5c:b3:b2:72;CM-QOS=1.1;CM-VER=3.1;
2020-07-14, 13:30:56 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=08:36:c9:cc:a4:a8;CMTS-MAC=00:01:5c:b3:b2:72;CM-QOS=1.1;CM-VER=3.1;
2020-07-14, 13:27:30 Warning (5) MDD message timeout;CM-MAC=08:36:c9:cc:a4:a8;CMTS-MAC=00:01:5c:b3:b2:72;CM-QOS=1.1;CM-VER=3.1;
2020-07-14, 13:25:56 Notice (6) Honoring MDD; IP provisioning mode = IPv6
2020-07-14, 13:25:43 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=08:36:c9:cc:a4:a8;CMTS-MAC=00:01:5c:b3:b2:72;CM-QOS=1.1;CM-VER=3.1;
2020-07-14, 13:25:26 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=08:36:c9:cc:a4:a8;CMTS-MAC=00:01:5c:b3:b2:72;CM-QOS=1.1;CM-VER=3.1;
2020-07-14, 13:25:26 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=08:36:c9:cc:a4:a8;CMTS-MAC=00:01:5c:b3:b2:72;CM-QOS=1.1;CM-VER=3.1;
2020-07-14, 13:25:21 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=08:36:c9:cc:a4:a8;CMTS-MAC=00:01:5c:b3:b2:72;CM-QOS=1.1;CM-VER=3.1;
2020-07-14, 13:25:20 Warning (5) MDD message timeout;CM-MAC=08:36:c9:cc:a4:a8;CMTS-MAC=00:01:5c:b3:b2:72;CM-QOS=1.1;CM-VER=3.1;
2020-07-14, 13:25:19 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=08:36:c9:cc:a4:a8;CMTS-MAC=00:01:5c:b3:b2:72;CM-QOS=1.1;CM-VER=3.1;
2020-07-14, 13:17:56 Warning (5) MDD message timeout;CM-MAC=08:36:c9:cc:a4:a8;CMTS-MAC=00:01:5c:b3:b2:72;CM-QOS=1.1;CM-VER=3.1;
2020-07-14, 13:13:05 Notice (6) Honoring MDD; IP provisioning mode = IPv6
Highlighted
Frequent Visitor

Re: Modem Keeps Resetting even after Tech Visit

I have the EXACT same issue and <Edited> I already tried everything in the FAQ and so has the OP. My event log from my modem looks exactly like yours. My internet goes out at 10 am every day like clock work since July the 3rd. Sometimes it comes back after 15 minutes others like yesterday its out until 8pm.