NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Cm1000 xfinity issue dropping connection
I am having trouble with my connection dropping through out the day comcast tells me my modem is losing its bootfiles or something and that my connection is good on there end I have pulled my modems logs but I honestly dont know what im looking at and if someone here might be able to help me.
| 2022-02-28, 13:03:47 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=14:59:c0:f6:18:80;CMTS-MAC=00:90:f0:2b:05:00;CM-QOS=1.1;CM-VER=3.1; |
| 2022-02-28, 13:03:15 | Warning (5) | Dynamic Range Window violation |
| 2022-02-28, 13:03:15 | Warning (5) | RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=14:59:c0:f6:18:80;CMTS-MAC=00:90:f0:2b:05:00;CM-QOS=1.1;CM-VER=3.1; |
| 2022-02-28, 12:59:31 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=14:59:c0:f6:18:80;CMTS-MAC=00:90:f0:2b:05:00;CM-QOS=1.1;CM-VER=3.1; |
| 2022-02-28, 12:54:39 | Warning (5) | Dynamic Range Window violation |
| 2022-02-28, 12:54:39 | Warning (5) | RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=14:59:c0:f6:18:80;CMTS-MAC=00:90:f0:2b:05:00;CM-QOS=1.1;CM-VER=3.1; |
| 2022-02-28, 12:34:51 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=14:59:c0:f6:18:80;CMTS-MAC=00:90:f0:2b:05:00;CM-QOS=1.1;CM-VER=3.1; |
| 2022-02-28, 12:34:06 | Notice (6) | CM-STATUS message sent. Event Type Code: 24; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=14:59:c0:f6:18:80;CMTS-MAC=00:90:f0:2b:05:00;CM-QOS=1.1;CM-VER=3.1; |
| 2022-02-28, 12:33:38 | Notice (6) | CM-STATUS message sent. Event Type Code: 16; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=14:59:c0:f6:18:80;CMTS-MAC=00:90:f0:2b:05:00;CM-QOS=1.1;CM-VER=3.1; |
| 2022-02-28, 12:32:37 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=14:59:c0:f6:18:80;CMTS-MAC=00:90:f0:2b:05:00;CM-QOS=1.1;CM-VER=3.1; |
| 2022-02-28, 12:32:18 | Warning (5) | Dynamic Range Window violation |
| 2022-02-28, 12:32:18 | Warning (5) | RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=14:59:c0:f6:18:80;CMTS-MAC=00:90:f0:2b:05:00;CM-QOS=1.1;CM-VER=3.1; |
| 2022-02-28, 12:18:29 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=14:59:c0:f6:18:80;CMTS-MAC=00:90:f0:2b:05:00;CM-QOS=1.1;CM-VER=3.1; |
| 2022-02-28, 12:17:35 | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=14:59:c0:f6:18:80;CMTS-MAC=00:90:f0:2b:05:00;CM-QOS=1.1;CM-VER=3.1; |
| 2022-02-28, 11:56:09 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=14:59:c0:f6:18:80;CMTS-MAC=00:90:f0:2b:05:00;CM-QOS=1.1;CM-VER=3.1; |
| 2022-02-28, 11:49:05 | Warning (5) | Dynamic Range Window violation |
| 2022-02-28, 11:49:05 | Warning (5) | RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=14:59:c0:f6:18:80;CMTS-MAC=00:90:f0:2b:05:00;CM-QOS=1.1;CM-VER=3.1; |
| 2022-02-28, 11:21:05 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=14:59:c0:f6:18:80;CMTS-MAC=00:90:f0:2b:05:00;CM-QOS=1.1;CM-VER=3.1; |
| 2022-02-28, 10:42:37 | Notice (6) | CM-STATUS message sent. Event Type Code: 24; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=14:59:c0:f6:18:80;CMTS-MAC=00:90:f0:2b:05:00;CM-QOS=1.1;CM-VER=3.1; |
| 2022-02-28, 10:41:53 | Notice (6) | CM-STATUS message sent. Event Type Code: 16; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=14:59:c0:f6:18:80;CMTS-MAC=00:90:f0:2b:05:00;CM-QOS=1.1;CM-VER=3.1; |
| 2022-02-28, 10:41:47 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=14:59:c0:f6:18:80;CMTS-MAC=00:90:f0:2b:05:00;CM-QOS=1.1;CM-VER=3.1; |
| 2022-02-28, 10:25:48 | Notice (6) | CM-STATUS message sent. Event Type Code: 24; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=14:59:c0:f6:18:80;CMTS-MAC=00:90:f0:2b:05:00;CM-QOS=1.1;CM-VER=3.1; |
| 2022-02-28, 10:25:01 | Notice (6) | CM-STATUS message sent. Event Type Code: 16; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=14:59:c0:f6:18:80;CMTS-MAC=00:90:f0:2b:05:00;CM-QOS=1.1;CM-VER=3.1; |
| 2022-02-28, 10:24:39 | Notice (6) | CM-STATUS message sent. Event Type Code: 24; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=14:59:c0:f6:18:80;CMTS-MAC=00:90:f0:2b:05:00;CM-QOS=1.1;CM-VER=3.1; |
| 2022-02-28, 10:24:09 | Warning (5) | Dynamic Range Window violation |
| 2022-02-28, 10:24:09 | Warning (5) | RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=14:59:c0:f6:18:80;CMTS-MAC=00:90:f0:2b:05:00;CM-QOS=1.1;CM-VER=3.1; |
| 2022-02-28, 10:23:55 | Notice (6) | CM-STATUS message sent. Event Type Code: 16; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=14:59:c0:f6:18:80;CMTS-MAC=00:90:f0:2b:05:00;CM-QOS=1.1;CM-VER=3.1; |
| 2022-02-28, 10:23:22 | Notice (6) | CM-STATUS message sent. Event Type Code: 24; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=14:59:c0:f6:18:80;CMTS-MAC=00:90:f0:2b:05:00;CM-QOS=1.1;CM-VER=3.1; |
| 2022-02-28, 10:23:10 | Notice (6) | CM-STATUS message sent. Event Type Code: 4; Chan ID: 11 15; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=14:59:c0:f6:18:80;CMTS-MAC=00:90:f0:2b:05:00;CM-QOS=1.1;CM-VER=3.1; |
| 2022-02-28, 10:22:46 | Warning (5) | MDD message timeout;CM-MAC=14:59:c0:f6:18:80;CMTS-MAC=00:90:f0:2b:05:00;CM-QOS=1.1;CM-VER=3.1; |
| 2022-02-28, 10:22:40 | Notice (6) | CM-STATUS message sent. Event Type Code: 16; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=14:59:c0:f6:18:80;CMTS-MAC=00:90:f0:2b:05:00;CM-QOS=1.1;CM-VER=3.1; |
| 2022-02-28, 10:22:38 | Notice (6) | CM-STATUS message sent. Event Type Code: 24; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=14:59:c0:f6:18:80;CMTS-MAC=00:90:f0:2b:05:00;CM-QOS=1.1;CM-VER=3.1; |
| 2022-02-28, 10:22:12 | Notice (6) | CM-STATUS message sent. Event Type Code: 16; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=14:59:c0:f6:18:80;CMTS-MAC=00:90:f0:2b:05:00;CM-QOS=1.1;CM-VER=3.1; |
| 2022-02-28, 10:18:22 | Notice (6) | CM-STATUS message sent. Event Type Code: 24; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=14:59:c0:f6:18:80;CMTS-MAC=00:90:f0:2b:05:00;CM-QOS=1.1;CM-VER=3.1; |
| 2022-02-28, 10:17:41 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=14:59:c0:f6:18:80;CMTS-MAC=00:90:f0:2b:05:00;CM-QOS=1.1;CM-VER=3.1; |
| 2022-02-28, 10:17:38 | Notice (6) | CM-STATUS message sent. Event Type Code: 16; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=14:59:c0:f6:18:80;CMTS-MAC=00:90:f0:2b:05:00;CM-QOS=1.1;CM-VER=3.1; |
| 2022-02-28, 05:56:33 | Notice (6) | CM-STATUS message sent. Event Type Code: 24; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=14:59:c0:f6:18:80;CMTS-MAC=00:90:f0:2b:05:00;CM-QOS=1.1;CM-VER=3.1; |
| 2022-02-28, 05:55:46 | Notice (6) | CM-STATUS message sent. Event Type Code: 16; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=14:59:c0:f6:18:80;CMTS-MAC=00:90:f0:2b:05:00;CM-QOS=1.1;CM-VER=3.1; |
| 2022-02-28, 05:41:13 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=14:59:c0:f6:18:80;CMTS-MAC=00:90:f0:2b:05:00;CM-QOS=1.1;CM-VER=3.1; |
| 2022-02-28, 05:24:17 | Warning (5) | Dynamic Range Window violation |
4 Replies
Your logs indicate line issues. got a screen snip of the cable connections page as well?
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, 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.Here is a snip of my cable connection page
lots of errors in there. go through what I outlined prior. If it doesn't help or your connection is still the same, then the ISP needs to check the line.
