Re: C3700 drops internet frequently

Naragun · ‎2019-11-06

I've been having constant issues with my router/modem since moving into our new apartment. The connection (LAN and WiFi) randomly drops throughout the day. This is sometimes every few hours and sometimes every 10 minutes, but it disconnects every device from the internet and screws up whatever I was doing. I've contacted my ISP and they've confirmed that the issue isn't on their end. Just dropped again while writing this. I've tried multiple things already but i'd like to hear any possible solutions please. I'll put a copy of my event log, and will provide any other information that could help.

Time Priority Description 2019-11-6, 16:09:25 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:0c:6b:6f:9c:80;CMTS-MAC=80:e0:1d:6d:5b:1e;CM-QOS=1.1;CM-VER=3.0; 2019-11-6, 16:09:25 Warning (5) MDD message timeout;CM-MAC=10:0c:6b:6f:9c:80;CMTS-MAC=80:e0:1d:6d:5b:1e;CM-QOS=1.1;CM-VER=3.0; 2019-11-6, 15:23:52 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:0c:6b:6f:9c:80;CMTS-MAC=80:e0:1d:6d:5b:1e;CM-QOS=1.1;CM-VER=3.0; 2019-11-6, 15:23:52 Warning (5) MDD message timeout;CM-MAC=10:0c:6b:6f:9c:80;CMTS-MAC=80:e0:1d:6d:5b:1e;CM-QOS=1.1;CM-VER=3.0; 2019-11-6, 13:53:14 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:0c:6b:6f:9c:80;CMTS-MAC=80:e0:1d:6d:5b:1e;CM-QOS=1.1;CM-VER=3.0; 2019-11-6, 13:53:14 Warning (5) MDD message timeout;CM-MAC=10:0c:6b:6f:9c:80;CMTS-MAC=80:e0:1d:6d:5b:1e;CM-QOS=1.1;CM-VER=3.0; 2019-11-6, 13:36:59 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:0c:6b:6f:9c:80;CMTS-MAC=80:e0:1d:6d:5b:1e;CM-QOS=1.1;CM-VER=3.0; 2019-11-6, 13:36:59 Warning (5) MDD message timeout;CM-MAC=10:0c:6b:6f:9c:80;CMTS-MAC=80:e0:1d:6d:5b:1e;CM-QOS=1.1;CM-VER=3.0; 2019-11-6, 13:03:16 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:0c:6b:6f:9c:80;CMTS-MAC=80:e0:1d:6d:5b:1e;CM-QOS=1.1;CM-VER=3.0; 2019-11-6, 13:03:16 Warning (5) MDD message timeout;CM-MAC=10:0c:6b:6f:9c:80;CMTS-MAC=80:e0:1d:6d:5b:1e;CM-QOS=1.1;CM-VER=3.0; 2019-11-6, 11:40:21 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:0c:6b:6f:9c:80;CMTS-MAC=80:e0:1d:6d:5b:1e;CM-QOS=1.1;CM-VER=3.0; 2019-11-6, 11:40:20 Warning (5) MDD message timeout;CM-MAC=10:0c:6b:6f:9c:80;CMTS-MAC=80:e0:1d:6d:5b:1e;CM-QOS=1.1;CM-VER=3.0; 2019-11-6, 11:18:23 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:0c:6b:6f:9c:80;CMTS-MAC=80:e0:1d:6d:5b:1e;CM-QOS=1.1;CM-VER=3.0; 2019-11-6, 11:18:22 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=10:0c:6b:6f:9c:80;CMTS-MAC=80:e0:1d:6d:5b:1e;CM-QOS=1.1;CM-VER=3.0; 2019-11-6, 11:18:22 Warning (5) MDD message timeout;CM-MAC=10:0c:6b:6f:9c:80;CMTS-MAC=80:e0:1d:6d:5b:1e;CM-QOS=1.1;CM-VER=3.0; 2019-11-6, 10:54:22 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:0c:6b:6f:9c:80;CMTS-MAC=80:e0:1d:6d:5b:1e;CM-QOS=1.1;CM-VER=3.0; 2019-11-6, 10:54:22 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=10:0c:6b:6f:9c:80;CMTS-MAC=80:e0:1d:6d:5b:1e;CM-QOS=1.1;CM-VER=3.0; 2019-11-6, 10:54:22 Warning (5) MDD message timeout;CM-MAC=10:0c:6b:6f:9c:80;CMTS-MAC=80:e0:1d:6d:5b:1e;CM-QOS=1.1;CM-VER=3.0; 2019-11-6, 09:02:54 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:0c:6b:6f:9c:80;CMTS-MAC=80:e0:1d:6d:5b:1e;CM-QOS=1.1;CM-VER=3.0; 2019-11-6, 09:02:54 Warning (5) MDD message timeout;CM-MAC=10:0c:6b:6f:9c:80;CMTS-MAC=80:e0:1d:6d:5b:1e;CM-QOS=1.1;CM-VER=3.0; 2019-11-6, 08:56:51 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:0c:6b:6f:9c:80;CMTS-MAC=80:e0:1d:6d:5b:1e;CM-QOS=1.1;CM-VER=3.0; 2019-11-6, 08:56:50 Warning (5) MDD message timeout;CM-MAC=10:0c:6b:6f:9c:80;CMTS-MAC=80:e0:1d:6d:5b:1e;CM-QOS=1.1;CM-VER=3.0; 2019-11-6, 08:52:44 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:0c:6b:6f:9c:80;CMTS-MAC=80:e0:1d:6d:5b:1e;CM-QOS=1.1;CM-VER=3.0; 2019-11-6, 08:52:44 Warning (5) MDD message timeout;CM-MAC=10:0c:6b:6f:9c:80;CMTS-MAC=80:e0:1d:6d:5b:1e;CM-QOS=1.1;CM-VER=3.0; 2019-11-6, 08:45:44 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:0c:6b:6f:9c:80;CMTS-MAC=80:e0:1d:6d:5b:1e;CM-QOS=1.1;CM-VER=3.0; 2019-11-6, 08:45:43 Warning (5) MDD message timeout;CM-MAC=10:0c:6b:6f:9c:80;CMTS-MAC=80:e0:1d:6d:5b:1e;CM-QOS=1.1;CM-VER=3.0; 2019-11-6, 08:13:30 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:0c:6b:6f:9c:80;CMTS-MAC=80:e0:1d:6d:5b:1e;CM-QOS=1.1;CM-VER=3.0; 2019-11-6, 08:13:30 Warning (5) MDD message timeout;CM-MAC=10:0c:6b:6f:9c:80;CMTS-MAC=80:e0:1d:6d:5b:1e;CM-QOS=1.1;CM-VER=3.0; 2019-11-6, 08:06:27 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:0c:6b:6f:9c:80;CMTS-MAC=80:e0:1d:6d:5b:1e;CM-QOS=1.1;CM-VER=3.0; 2019-11-6, 08:06:27 Warning (5) MDD message timeout;CM-MAC=10:0c:6b:6f:9c:80;CMTS-MAC=80:e0:1d:6d:5b:1e;CM-QOS=1.1;CM-VER=3.0; 2019-11-6, 07:42:41 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:0c:6b:6f:9c:80;CMTS-MAC=80:e0:1d:6d:5b:1e;CM-QOS=1.1;CM-VER=3.0; 2019-11-6, 07:42:41 Warning (5) MDD message timeout;CM-MAC=10:0c:6b:6f:9c:80;CMTS-MAC=80:e0:1d:6d:5b:1e;CM-QOS=1.1;CM-VER=3.0; 2019-11-6, 06:58:55 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:0c:6b:6f:9c:80;CMTS-MAC=80:e0:1d:6d:5b:1e;CM-QOS=1.1;CM-VER=3.0; 2019-11-6, 06:58:55 Warning (5) MDD message timeout;CM-MAC=10:0c:6b:6f:9c:80;CMTS-MAC=80:e0:1d:6d:5b:1e;CM-QOS=1.1;CM-VER=3.0; 2019-11-6, 06:53:04 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:0c:6b:6f:9c:80;CMTS-MAC=80:e0:1d:6d:5b:1e;CM-QOS=1.1;CM-VER=3.0; 2019-11-6, 06:53:04 Warning (5) MDD message timeout;CM-MAC=10:0c:6b:6f:9c:80;CMTS-MAC=80:e0:1d:6d:5b:1e;CM-QOS=1.1;CM-VER=3.0; 2019-11-6, 06:52:28 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:0c:6b:6f:9c:80;CMTS-MAC=80:e0:1d:6d:5b:1e;CM-QOS=1.1;CM-VER=3.0; 2019-11-6, 06:52:28 Warning (5) MDD message timeout;CM-MAC=10:0c:6b:6f:9c:80;CMTS-MAC=80:e0:1d:6d:5b:1e;CM-QOS=1.1;CM-VER=3.0; 2019-11-6, 06:22:25 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:0c:6b:6f:9c:80;CMTS-MAC=80:e0:1d:6d:5b:1e;CM-QOS=1.1;CM-VER=3.0; 2019-11-6, 06:22:25 Warning (5) MDD message timeout;CM-MAC=10:0c:6b:6f:9c:80;CMTS-MAC=80:e0:1d:6d:5b:1e;CM-QOS=1.1;CM-VER=3.0;

FURRYe38 · ‎2019-11-06

Have the ISP check the signal on the line and quality up to the modem.

Be sure there are no coax cable line splitters in between the ISP service box and the modem.

Naragun · ‎2019-11-07

The ISP said everything was good on their end. And there are no splitters at all unless they're built into the wall or something.

FURRYe38 · ‎2019-11-08

Try a factory reset on the modem and setup from scratch.

What channels are you using? Auto? Try setting manual channel 1, 6 or 11 on 2.4Ghz and any unused channel on 5Ghz.
Any Wifi Neighbors near by? If so, how many?

Naragun · ‎2019-11-08

I've tried resetting it as well as switching to each available channel and using unpopular ones.

FURRYe38 · ‎2019-11-11

If this continues, you may need to try a different modem combo unit to see if this still happens. Possible your modem unit is becoming faulty. Contact NG support to see if there are any other options.