Regular Visitor
•
4 Messages
Unicast Maintenance Ranging - No Response received - T3 time-out
Hello,
I've been having issues with my SB8200 Modem, and my Nest Wifi Mesh Router constantly dropping my connection. I currently pay for the up to 1,000 Mbps speeds. However, I constantly find myself having to restart my internet because my speeds will be less 10 Mbps.
I recently had a tech come out to my house and change out the cable connected to the pedestal, he also changed out the connectors to the box outside my house and replaced the coax cable.
Below I'll have my modems event log.
10/02/2020 10:38 | 82000500 | 3 | "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=d4:3f:cb:e2:58:25;CMTS-MAC=00:56:2b:77:13:21;CM-QOS=1.1;CM-VER=3.1;" |
10/02/2020 08:21 | 2436694061 | 5 | "Dynamic Range Window violation" |
10/02/2020 08:21 | 82001100 | 5 | "RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=d4:3f:cb:e2:58:25;CMTS-MAC=00:56:2b:77:13:21;CM-QOS=1.1;CM-VER=3.1;" |
10/02/2020 07:39 | 2436694061 | 5 | "Dynamic Range Window violation" |
10/02/2020 07:39 | 82001100 | 5 | "RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=d4:3f:cb:e2:58:25;CMTS-MAC=00:56:2b:77:13:21;CM-QOS=1.1;CM-VER=3.1;" |
10/02/2020 07:23 | 2436694061 | 5 | "Dynamic Range Window violation" |
10/02/2020 07:23 | 82001100 | 5 | "RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=d4:3f:cb:e2:58:25;CMTS-MAC=00:56:2b:77:13:21;CM-QOS=1.1;CM-VER=3.1;" |
10/02/2020 07:11 | 82000500 | 3 | "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=d4:3f:cb:e2:58:25;CMTS-MAC=00:56:2b:77:13:21;CM-QOS=1.1;CM-VER=3.1;" |
10/02/2020 00:33 | 2436694061 | 5 | "Dynamic Range Window violation" |
10/02/2020 00:33 | 82001100 | 5 | "RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=d4:3f:cb:e2:58:25;CMTS-MAC=00:56:2b:77:13:21;CM-QOS=1.1;CM-VER=3.1;" |
10/02/2020 00:02 | 2436694061 | 5 | "Dynamic Range Window violation" |
10/02/2020 00:02 | 82001100 | 5 | "RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=d4:3f:cb:e2:58:25;CMTS-MAC=00:56:2b:77:13:21;CM-QOS=1.1;CM-VER=3.1;" |
10/01/2020 23:29 | 2436694061 | 5 | "Dynamic Range Window violation" |
10/01/2020 23:29 | 82001100 | 5 | "RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=d4:3f:cb:e2:58:25;CMTS-MAC=00:56:2b:77:13:21;CM-QOS=1.1;CM-VER=3.1;" |
10/01/2020 23:29 | 2436694061 | 5 | "Dynamic Range Window violation" |
10/01/2020 23:29 | 82001100 | 5 | "RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=d4:3f:cb:e2:58:25;CMTS-MAC=00:56:2b:77:13:21;CM-QOS=1.1;CM-VER=3.1;" |
10/01/2020 23:26 | 2436694061 | 5 | "Dynamic Range Window violation" |
10/01/2020 23:26 | 82001100 | 5 | "RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=d4:3f:cb:e2:58:25;CMTS-MAC=00:56:2b:77:13:21;CM-QOS=1.1;CM-VER=3.1;" |
10/01/2020 23:12 | 2436694061 | 5 | "Dynamic Range Window violation" |
10/01/2020 23:12 | 82001100 | 5 | "RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=d4:3f:cb:e2:58:25;CMTS-MAC=00:56:2b:77:13:21;CM-QOS=1.1;CM-VER=3.1;" |
10/01/2020 22:56 | 2436694061 | 5 | "Dynamic Range Window violation" |
10/01/2020 22:56 | 82001100 | 5 | "RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=d4:3f:cb:e2:58:25;CMTS-MAC=00:56:2b:77:13:21;CM-QOS=1.1;CM-VER=3.1;" |
10/01/2020 19:24 | 82000500 | 3 | "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=d4:3f:cb:e2:58:25;CMTS-MAC=00:56:2b:77:13:21;CM-QOS=1.1;CM-VER=3.1;" |
10/01/2020 14:47 | 2436694061 | 5 | "Dynamic Range Window violation" |
10/01/2020 14:47 | 82001100 | 5 | "RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=d4:3f:cb:e2:58:25;CMTS-MAC=00:56:2b:77:13:21;CM-QOS=1.1;CM-VER=3.1;" |
10/01/2020 08:52 | 2436694061 | 5 | "Dynamic Range Window violation" |
10/01/2020 08:52 | 82001100 | 5 | "RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=d4:3f:cb:e2:58:25;CMTS-MAC=00:56:2b:77:13:21;CM-QOS=1.1;CM-VER=3.1;" |
10/01/2020 08:46 | 2436694061 | 5 | "Dynamic Range Window violation" |
10/01/2020 08:46 | 82001100 | 5 | "RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=d4:3f:cb:e2:58:25;CMTS-MAC=00:56:2b:77:13:21;CM-QOS=1.1;CM-VER=3.1;" |
10/01/2020 08:25 | 2436694061 | 5 | "Dynamic Range Window violation" |
10/01/2020 08:25 | 82001100 | 5 | "RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=d4:3f:cb:e2:58:25;CMTS-MAC=00:56:2b:77:13:21;CM-QOS=1.1;CM-VER=3.1;" |
10/01/2020 08:09 | 2436694061 | 5 | "Dynamic Range Window violation" |
10/01/2020 08:09 | 82001100 | 5 | "RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=d4:3f:cb:e2:58:25;CMTS-MAC=00:56:2b:77:13:21;CM-QOS=1.1;CM-VER=3.1;" |
10/01/2020 07:59 | 2436694061 | 5 | "Dynamic Range Window violation" |
10/01/2020 07:59 | 82001100 | 5 | "RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=d4:3f:cb:e2:58:25;CMTS-MAC=00:56:2b:77:13:21;CM-QOS=1.1;CM-VER=3.1;" |
10/01/2020 07:53 | 2436694061 | 5 | "Dynamic Range Window violation" |
10/01/2020 07:53 | 82001100 | 5 | "RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=d4:3f:cb:e2:58:25;CMTS-MAC=00:56:2b:77:13:21;CM-QOS=1.1;CM-VER=3.1;" |
10/01/2020 07:53 | 82000500 | 3 | "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=d4:3f:cb:e2:58:25;CMTS-MAC=00:56:2b:77:13:21;CM-QOS=1.1;CM-VER=3.1;" |
10/01/2020 07:21 | 2436694061 | 5 | "Dynamic Range Window violation" |
10/01/2020 07:21 | 82001100 | 5 | "RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=d4:3f:cb:e2:58:25;CMTS-MAC=00:56:2b:77:13:21;CM-QOS=1.1;CM-VER=3.1;" |
10/01/2020 06:41 | 82000500 | 3 | "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=d4:3f:cb:e2:58:25;CMTS-MAC=00:56:2b:77:13:21;CM-QOS=1.1;CM-VER=3.1;" |
10/01/2020 02:37 | 2436694061 | 5 | "Dynamic Range Window violation" |
10/01/2020 02:37 | 82001100 | 5 | "RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=d4:3f:cb:e2:58:25;CMTS-MAC=00:56:2b:77:13:21;CM-QOS=1.1;CM-VER=3.1;" |
10/01/2020 02:33 | 2436694061 | 5 | "Dynamic Range Window violation" |
10/01/2020 02:33 | 82001100 | 5 | "RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=d4:3f:cb:e2:58:25;CMTS-MAC=00:56:2b:77:13:21;CM-QOS=1.1;CM-VER=3.1;" |
10/01/2020 02:03 | 2436694061 | 5 | "Dynamic Range Window violation" |
10/01/2020 02:03 | 82001100 | 5 | "RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=d4:3f:cb:e2:58:25;CMTS-MAC=00:56:2b:77:13:21;CM-QOS=1.1;CM-VER=3.1;" |
10/01/2020 01:43 | 2436694061 | 5 | "Dynamic Range Window violation" |
10/01/2020 01:43 | 82001100 | 5 | "RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=d4:3f:cb:e2:58:25;CMTS-MAC=00:56:2b:77:13:21;CM-QOS=1.1;CM-VER=3.1;" |
10/01/2020 01:29 | 2436694061 | 5 | "Dynamic Range Window violation" |
IkeaT93
New Poster
•
2 Messages
5 years ago
I just posted the same forum. If I find out anything I will let you know for sure.
https://pickmymodem.com/cable-modem-t3-and-t4-timeouts-error-messages-and-how-to-fix-them/
0
0
EG
Expert
•
111.4K Messages
5 years ago
.@Lunanestor
Please also post the *Downstream Power Level*, the *Upstream Power Level*, and the *SNR* (Signal to Noise Ratio) numbers.
0
0
Lunanestor
Regular Visitor
•
4 Messages
5 years ago
Upstream bonded channels
0
0
Lunanestor
Regular Visitor
•
4 Messages
5 years ago
Downstream Bonded Channels
0
0
EG
Expert
•
111.4K Messages
5 years ago
All good. Is it the same with a direct connection to the 8200 cable modem (no router in the mix) ?
0
0
Lunanestor
Regular Visitor
•
4 Messages
5 years ago
Yes it is.
0
0
EG
Expert
•
111.4K Messages
5 years ago
O/k. Even though the signal stats looked o/k at that snapshot in time, the error log entries confirm that something is going on. Perhaps there is noise ingress into the line(s) somewhere.
There are other signal stat figures that can't be read by the modem. They are the "Upstream Rx Power" (Upstream Receive Power Level), the "Upstream SNR Ch." (Upstream Signal To Noise Ratio), and the "Upstream ICFR" (In Channel Frequency Response). These are as equally important in diagnosing connectivity issues as are the modem's stats.
I'm going to escalate your issue to the Comcast corporate employees that are available to these boards. They can check the CMTS (Cable Modem Termination System) for any real time degradation and / or error reports, see your node / cable plant and modem health, and see whether or not everything is in the green zone. They can also see a history plot for the modem and poll for those upstream receive signal stats.
You should get a reply here in your topic. Good luck !
0
0
CCChe
Official Employee
•
6.9K Messages
5 years ago
Hi @Lunanestor,
Thanks for posting to the Xfinity Forum and sharing the details of your experience. I agree with @EG. I think there may be a bigger issue on your line/ at the node. I'd be happy to investigate further and work with you to help get this resolved. Can you send me a private message with your first and last name and service address? To send me a private message, click on "ComcastChe" and then click send a message.
0
LV11BangBang
New Poster
•
1 Message
5 years ago
I to am having the same issue. Please see below.
operation of the cable modem.
0
0