U

Visitor

 • 

4 Messages

Wednesday, July 6th, 2022 5:08 PM

Closed

Intermittent Internet Issues with Arris S33 Modem

Hi everyone. As the title suggests, I am having issues with my Arris S33 modem frequently disconnecting. I have been researching common issues and I believe (but am not entirely sure) that the modem is receiving too much power on the upstream bonded channels. That said, the uncorrectables are slightly concerning too as they seem very high. Mind you I just reset my modem less than an hour ago. Below I am posting my stats from the modem. If anyone has any suggestions that would be great. Thank you for your help!
Downstream Bonded Channels
Channel ID Lock Status Modulation Frequency Power SNR/MER Corrected Uncorrectables
5 Locked QAM256 507000000 Hz -2 dBmV 41 dB 1941 6142
1 Locked QAM256 477000000 Hz -2 dBmV 41 dB 1807 5896
2 Locked QAM256 483000000 Hz -2 dBmV 41 dB 8660 24579
3 Locked QAM256 489000000 Hz -2 dBmV 41 dB 8682 24725
4 Locked QAM256 495000000 Hz -2 dBmV 41 dB 8808 24736
6 Locked QAM256 513000000 Hz -2 dBmV 41 dB 8935 24295
7 Locked QAM256 519000000 Hz -2 dBmV 41 dB 1911 5736
8 Locked QAM256 525000000 Hz -2 dBmV 41 dB 8613 23685
9 Locked QAM256 531000000 Hz -3 dBmV 41 dB 8698 24452
10 Locked QAM256 537000000 Hz -2 dBmV 41 dB 8667 23624
11 Locked QAM256 543000000 Hz -3 dBmV 41 dB 8606 23329
12 Locked QAM256 549000000 Hz -2 dBmV 41 dB 8847 23693
13 Locked QAM256 555000000 Hz -3 dBmV 40 dB 8854 23636
14 Locked QAM256 561000000 Hz -3 dBmV 40 dB 8815 23905
15 Locked QAM256 567000000 Hz -3 dBmV 40 dB 8853 23788
16 Locked QAM256 573000000 Hz -3 dBmV 40 dB 8816 23812
17 Locked QAM256 579000000 Hz -3 dBmV 40 dB 8934 23417
18 Locked QAM256 585000000 Hz -3 dBmV 40 dB 9020 23421
19 Locked QAM256 591000000 Hz -3 dBmV 40 dB 8968 23418
29 Locked QAM256 453000000 Hz -1 dBmV 42 dB 8690 24744
34 Locked QAM256 459000000 Hz -1 dBmV 42 dB 8383 24833
35 Locked QAM256 465000000 Hz -1 dBmV 41 dB 8516 24720
36 Locked QAM256 471000000 Hz -2 dBmV 41 dB 8839 25014
37 Locked OFDM PLC 690000000 Hz -5 dBmV 38 dB 13875621 3306
38 Locked QAM256 423000000 Hz -1 dBmV 42 dB 8835 25898
39 Locked QAM256 435000000 Hz -2 dBmV 42 dB 8828 25112
40 Locked QAM256 441000000 Hz -2 dBmV 41 dB 8726 25096
41 Locked QAM256 447000000 Hz -2 dBmV 41 dB 8784 24957
42 Locked QAM256 399000000 Hz 0 dBmV 42 dB 9025 25979
43 Locked QAM256 405000000 Hz 0 dBmV 42 dB 8797 25928
44 Locked QAM256 411000000 Hz 0 dBmV 42 dB 9018 25848
45 Locked QAM256 417000000 Hz -1 dBmV 42 dB 8742 25751

 
Upstream Bonded Channels
Channel ID Lock Status US Channel Type Frequency Width Power
1 Locked SC-QAM 35600000 Hz 6400000 51.0 dBmV
2 Not Locked SC-QAM 29200000 Hz 6400000 54.8 dBmV
3 Not Locked SC-QAM 22800000 Hz 6400000 53.3 dBmV
4 Not Locked SC-QAM 16400000 Hz 6400000 49.5 dBmV
8 Locked SC-QAM 39600000 Hz 1600000 50.3 dBmV

Expert

 • 

111.3K Messages

3 years ago

FWIW. The downstream power is what is "received" by the modem from the Comcast system. The upstream power is *transmitted* by the modem to the system.

That said. The downstream is o/k / in spec but the upstream power is marginal to out of spec, and it may be intermittently fluctuating even farther out of spec. That can cause random disconnects, spontaneous re-booting of the modem, speed, packet loss, latency problems, and the un-bonding of channels.

In an effort to try to obtain better connectivity / more wiggle room, check to see if there are there any excess/unneeded coax cable splitters in the line leading to the modem that can be eliminated/re-configured. Any splitters that remain should be high quality and cable rated for 5-1000 MHz, bi-directional, and no gold colored garbage from Radio Shack, Home Depot, Target, etc. Splitters should be swapped with known to be good / new ones to test.

Also check the coax cable for any damage such as cuts, nicks, kinks, sharp bends, etc.

If there aren't any unneeded splitters that can be eliminated and if your coax wiring setup can't be reconfigured so that there is a single two-way splitter connected directly off of the drop from the street / pole with one port feeding the modem and the other port feeding the rest of the house/equipment with additional splits as needed and you've checked all the wiring and fittings for integrity and tightness and refresh them by taking them apart then check for and clean off any corrosion / oxidation on the center wire and put them back together again, then perhaps it's best to book a tech visit to investigate and correct.


Good luck with it !

Visitor

 • 

4 Messages

3 years ago

Thank you for your response!

I replaced the splitter with one within the parameters you suggested earlier today. You are correct. The Upstream does fluctuate even further out of spec. I just checked again and it appears even worse than when I looked earlier. I could attempt to remove the splitter to see if it helps but we have a cable box in the room with the modem, hence the splitter.

I have also checked the wiring to the best of my ability and it all seems to be in good shape. It looks like a tech visit may be the best solution as you suggested unless you have any other ideas before I take that route.

I will also include error messages below with the updated upstream bonded channels. 

Thanks again!

Upstream Bonded Channels
Channel ID Lock Status US Channel Type Frequency Width Power
1 Locked SC-QAM 35600000 Hz 6400000 51.0 dBmV
2 Not Locked SC-QAM 29200000 Hz 6400000 55.5 dBmV
3 Not Locked SC-QAM 22800000 Hz 6400000 50.3 dBmV
4 Not Locked SC-QAM 16400000 Hz 6400000 54.8 dBmV
8 Locked SC-QAM 39600000 Hz 1600000 50.3 dBmV
6/7/2022
11:42:11
6 CM-STATUS message sent. Event Type Code: 24; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
6/7/2022
11:42:14
3 No Ranging Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
6/7/2022
11:42:20
3 Successful LAN WebGUI login from 68.51.56.169 on 22/07/06 at 11:42 AM.
6/7/2022
11:43:21
3 No Ranging Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
6/7/2022
11:43:21
3 Ranging Request Retries exhausted;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
6/7/2022
11:43:21
3 16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
6/7/2022
11:46:16
3 No Ranging Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
6/7/2022
11:46:16
3 Ranging Request Retries exhausted;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
6/7/2022
11:46:16
3 16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
6/7/2022
11:48:56
3 No Ranging Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
6/7/2022
11:48:56
3 Ranging Request Retries exhausted;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
6/7/2022
11:48:56
3 16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
6/7/2022
11:49:01
3 No Ranging Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
6/7/2022
11:49:01
3 Ranging Request Retries exhausted;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
6/7/2022
11:49:01
3 16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
6/7/2022
11:51:17
3 No Ranging Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
6/7/2022
11:51:17
3 Ranging Request Retries exhausted;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
6/7/2022
11:51:17
3 16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
6/7/2022
11:53:50
3 No Ranging Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
6/7/2022
11:53:50
3 Ranging Request Retries exhausted;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
6/7/2022
11:53:50
3 16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
6/7/2022
11:56:07
3 No Ranging Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
6/7/2022
11:56:07
3 Ranging Request Retries exhausted;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
6/7/2022
11:56:07
3 16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
6/7/2022
11:56:28
3 No Ranging Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
6/7/2022
11:56:28
3 Ranging Request Retries exhausted;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
6/7/2022
11:56:28
3 16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
6/7/2022
11:58:48
3 No Ranging Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
6/7/2022
11:58:48
3 Ranging Request Retries exhausted;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
6/7/2022
11:58:48
3 16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
6/7/2022
12:00:27
3 No Ranging Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
6/7/2022
12:00:27
3 Ranging Request Retries exhausted;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
6/7/2022
12:00:27
3 16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
6/7/2022
12:00:59
3 No Ranging Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
6/7/2022
12:01:05
6 CM-STATUS message sent. Event Type Code: 16; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
6/7/2022
12:01:31
3 No Ranging Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
6/7/2022
12:01:31
3 Ranging Request Retries exhausted;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
6/7/2022
12:01:31
3 16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
6/7/2022
12:04:06
3 No Ranging Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
6/7/2022
12:04:17
6 CM-STATUS message sent. Event Type Code: 24; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
6/7/2022
12:04:21
3 No Ranging Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
6/7/2022
12:04:21
3 Ranging Request Retries exhausted;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
6/7/2022
12:04:21
3 16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
6/7/2022
12:05:12
3 No Ranging Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
6/7/2022
12:05:12
3 Ranging Request Retries exhausted;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
6/7/2022
12:05:12
3 16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
6/7/2022
12:05:44
3 No Ranging Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
6/7/2022
12:05:44
3 Ranging Request Retries exhausted;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
6/7/2022
12:05:44
3 16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
6/7/2022
12:06:49
3 No Ranging Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
6/7/2022
12:07:00
6 CM-STATUS message sent. Event Type Code: 16; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
6/7/2022
12:07:11
3 No Ranging Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
6/7/2022
12:07:22
6 CM-STATUS message sent. Event Type Code: 20; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
6/7/2022
12:07:36
6 CM-STATUS message sent. Event Type Code: 5; Chan ID: 15 17 18 19 38 41 42 43 44; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
6/7/2022
12:09:26
3 No Ranging Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
6/7/2022
12:09:47
6 CM-STATUS message sent. Event Type Code: 22; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
6/7/2022
12:10:13
3 No Ranging Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
6/7/2022
12:10:13
3 Ranging Request Retries exhausted;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
6/7/2022
12:10:13
3 16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
6/7/2022
12:11:18
3 No Ranging Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
6/7/2022
12:11:18
3 Ranging Request Retries exhausted;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
6/7/2022
12:11:18
3 16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
6/7/2022
12:11:42
3 No Ranging Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
6/7/2022
12:11:42
3 Ranging Request Retries exhausted;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
6/7/2022
12:11:42
3 16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=c[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
6/7/2022
12:11:47
3 No Ranging Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
6/7/2022
12:11:49
6 CM-STATUS message sent. Event Type Code: 24; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
6/7/2022
12:13:45
3 No Ranging Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
6/7/2022
12:13:45
3 Ranging Request Retries exhausted;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
6/7/2022
12:13:45
3 16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
6/7/2022
12:16:50
3 No Ranging Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
6/7/2022
12:16:50
3 Ranging Request Retries exhausted;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
6/7/2022
12:16:50
3 16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
6/7/2022
12:17:19
3 No Ranging Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
6/7/2022
12:17:19
3 Ranging Request Retries exhausted;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
6/7/2022
12:17:19
3 16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
6/7/2022
12:19:18
3 No Ranging Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
6/7/2022
12:19:18
3 Ranging Request Retries exhausted;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
6/7/2022
12:19:18
3 16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
6/7/2022
12:21:42
3 No Ranging Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
6/7/2022
12:21:42
3 Ranging Request Retries exhausted;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
6/7/2022
12:21:42
3 16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
6/7/2022
12:22:27
3 No Ranging Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
6/7/2022
12:22:35
3 Successful LAN WebGUI login from 68.51.56.169 on 22/07/06 at 12:22 PM.
6/7/2022
12:22:43
3 No Ranging Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
6/7/2022
12:22:43
3 Ranging Request Retries exhausted;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
6/7/2022
12:22:43
3 16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
6/7/2022
12:25:26
3 No Ranging Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
6/7/2022
12:25:26
3 Ranging Request Retries exhausted;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
6/7/2022
12:25:26
3 16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
6/7/2022
12:27:30
3 No Ranging Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
6/7/2022
12:27:30
3 Ranging Request Retries exhausted;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
6/7/2022
12:27:30
3 16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
6/7/2022
12:27:37
3 No Ranging Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
6/7/2022
12:27:37
3 Ranging Request Retries exhausted;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
6/7/2022
12:27:37
3 16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
6/7/2022
12:31:24
3 No Ranging Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
6/7/2022
12:31:24
3 Ranging Request Retries exhausted;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
6/7/2022
12:31:24
3 16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
6/7/2022
12:33:14
3 No Ranging Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;

(edited)

Expert

 • 

111.3K Messages

3 years ago

@user_5ce29d 

Please redact all of the CM MAC and the CMTS MAC addresses in your error log entries for your privacy. They are considered to be personal information. The posting of personally identifiable information is a violation of their forum guidelines. The forum bot will not allow your post to be seen publically. It flagged your post as "Private".

Visitor

 • 

4 Messages

3 years ago

I fixed that. Very sorry.

Expert

 • 

111.3K Messages

3 years ago

No worries ! So if there is nothing more that can be done to improve the connection quality, then you'll need a tech visit as stated. 

Bear in mind that if the premises facing techs can not find or fix a problem at your home, it is they who are responsible for escalating it to their line / network / maintenance dept. techs. The problem may lie beyond your home in the local neighborhood infrastructure somewhere but it is their S.O.P. to start at the home. And if the problem is found to be on their side of the demarcation point, there will not be any charge.


Good luck !

Visitor

 • 

4 Messages

3 years ago

Thank you for your help! It is much appreciated.

Gold Problem Solver

 • 

7.2K Messages

Hi Kevin, thanks for taking the time to post here. I wanted to follow up to see how things are going. Did you get this issue taken care of? 

I no longer work for Comcast.

Expert

 • 

111.3K Messages

3 years ago

Quite welcome ! Please post back here with how things turn out, thanks.

forum icon

New to the Community?

Start Here