Community Forum

connection issues.

Frequent Visitor

connection issues.

Could someone take a look at this modem log and help direct me to the right person to get some help for connection issues?  

 

09/24/2019 05:10 82000200 3 "No Ranging Response received - T3 time-out;CM-MAC=d4:3f:cb:e6:37:cd;CMTS-MAC=00:01:5c:7d:72:68;CM-QOS=1.1;CM-VER=3.1;"
09/24/2019 05:09 82000800 3 "16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=d4:3f:cb:e6:37:cd;CMTS-MAC=00:01:5c:7d:72:68;CM-QOS=1.1;CM-VER=3.1;"
09/24/2019 05:09 82000300 3 "Ranging Request Retries exhausted;CM-MAC=d4:3f:cb:e6:37:cd;CMTS-MAC=00:01:5c:7d:72:68;CM-QOS=1.1;CM-VER=3.1;"
09/24/2019 05:09 82000200 3 "No Ranging Response received - T3 time-out;CM-MAC=d4:3f:cb:e6:37:cd;CMTS-MAC=00:01:5c:7d:72:68;CM-QOS=1.1;CM-VER=3.1;"
09/24/2019 05:09 82000800 3 "16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=d4:3f:cb:e6:37:cd;CMTS-MAC=00:01:5c:7d:72:68;CM-QOS=1.1;CM-VER=3.1;"
09/24/2019 05:09 82000300 3 "Ranging Request Retries exhausted;CM-MAC=d4:3f:cb:e6:37:cd;CMTS-MAC=00:01:5c:7d:72:68;CM-QOS=1.1;CM-VER=3.1;"
09/24/2019 05:09 82000200 3 "No Ranging Response received - T3 time-out;CM-MAC=d4:3f:cb:e6:37:cd;CMTS-MAC=00:01:5c:7d:72:68;CM-QOS=1.1;CM-VER=3.1;"
09/24/2019 05:07 82000800 3 "16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=d4:3f:cb:e6:37:cd;CMTS-MAC=00:01:5c:7d:72:68;CM-QOS=1.1;CM-VER=3.1;"
09/24/2019 05:07 82000300 3 "Ranging Request Retries exhausted;CM-MAC=d4:3f:cb:e6:37:cd;CMTS-MAC=00:01:5c:7d:72:68;CM-QOS=1.1;CM-VER=3.1;"
09/24/2019 05:07 82000200 3 "No Ranging Response received - T3 time-out;CM-MAC=d4:3f:cb:e6:37:cd;CMTS-MAC=00:01:5c:7d:72:68;CM-QOS=1.1;CM-VER=3.1;"
09/24/2019 05:04 82000800 3 "16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=d4:3f:cb:e6:37:cd;CMTS-MAC=00:01:5c:7d:72:68;CM-QOS=1.1;CM-VER=3.1;"
09/24/2019 05:04 82000300 3 "Ranging Request Retries exhausted;CM-MAC=d4:3f:cb:e6:37:cd;CMTS-MAC=00:01:5c:7d:72:68;CM-QOS=1.1;CM-VER=3.1;"
09/24/2019 05:04 82000200 3 "No Ranging Response received - T3 time-out;CM-MAC=d4:3f:cb:e6:37:cd;CMTS-MAC=00:01:5c:7d:72:68;CM-QOS=1.1;CM-VER=3.1;"
09/24/2019 05:03 82000800 3 "16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=d4:3f:cb:e6:37:cd;CMTS-MAC=00:01:5c:7d:72:68;CM-QOS=1.1;CM-VER=3.1;"
09/24/2019 05:03 82000300 3 "Ranging Request Retries exhausted;CM-MAC=d4:3f:cb:e6:37:cd;CMTS-MAC=00:01:5c:7d:72:68;CM-QOS=1.1;CM-VER=3.1;"
09/24/2019 05:03 82000200 3 "No Ranging Response received - T3 time-out;CM-MAC=d4:3f:cb:e6:37:cd;CMTS-MAC=00:01:5c:7d:72:68;CM-QOS=1.1;CM-VER=3.1;"
09/24/2019 05:02 82000800 3 "16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=d4:3f:cb:e6:37:cd;CMTS-MAC=00:01:5c:7d:72:68;CM-QOS=1.1;CM-VER=3.1;"
09/24/2019 05:02 82000300 3 "Ranging Request Retries exhausted;CM-MAC=d4:3f:cb:e6:37:cd;CMTS-MAC=00:01:5c:7d:72:68;CM-QOS=1.1;CM-VER=3.1;"
09/24/2019 05:02 82000200 3 "No Ranging Response received - T3 time-out;CM-MAC=d4:3f:cb:e6:37:cd;CMTS-MAC=00:01:5c:7d:72:68;CM-QOS=1.1;CM-VER=3.1;"
09/24/2019 04:59 82000800 3 "16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=d4:3f:cb:e6:37:cd;CMTS-MAC=00:01:5c:7d:72:68;CM-QOS=1.1;CM-VER=3.1;"
09/24/2019 04:59 82000300 3 "Ranging Request Retries exhausted;CM-MAC=d4:3f:cb:e6:37:cd;CMTS-MAC=00:01:5c:7d:72:68;CM-QOS=1.1;CM-VER=3.1;"
09/24/2019 04:59 82000200 3 "No Ranging Response received - T3 time-out;CM-MAC=d4:3f:cb:e6:37:cd;CMTS-MAC=00:01:5c:7d:72:68;CM-QOS=1.1;CM-VER=3.1;"
09/24/2019 04:57 82000800 3 "16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=d4:3f:cb:e6:37:cd;CMTS-MAC=00:01:5c:7d:72:68;CM-QOS=1.1;CM-VER=3.1;"
09/24/2019 04:57 82000300 3 "Ranging Request Retries exhausted;CM-MAC=d4:3f:cb:e6:37:cd;CMTS-MAC=00:01:5c:7d:72:68;CM-QOS=1.1;CM-VER=3.1;"
09/24/2019 04:57 82000200 3 "No Ranging Response received - T3 time-out;CM-MAC=d4:3f:cb:e6:37:cd;CMTS-MAC=00:01:5c:7d:72:68;CM-QOS=1.1;CM-VER=3.1;"
09/24/2019 04:57 82000800 3 "16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=d4:3f:cb:e6:37:cd;CMTS-MAC=00:01:5c:7d:72:68;CM-QOS=1.1;CM-VER=3.1;"
09/24/2019 04:57 82000300 3 "Ranging Request Retries exhausted;CM-MAC=d4:3f:cb:e6:37:cd;CMTS-MAC=00:01:5c:7d:72:68;CM-QOS=1.1;CM-VER=3.1;"
09/24/2019 04:57 82000200 3 "No Ranging Response received - T3 time-out;CM-MAC=d4:3f:cb:e6:37:cd;CMTS-MAC=00:01:5c:7d:72:68;CM-QOS=1.1;CM-VER=3.1;"
09/24/2019 04:52 82000800 3 "16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=d4:3f:cb:e6:37:cd;CMTS-MAC=00:01:5c:7d:72:68;CM-QOS=1.1;CM-VER=3.1;"
09/24/2019 04:52 82000300 3 "Ranging Request Retries exhausted;CM-MAC=d4:3f:cb:e6:37:cd;CMTS-MAC=00:01:5c:7d:72:68;CM-QOS=1.1;CM-VER=3.1;"
09/24/2019 04:52 82000200 3 "No Ranging Response received - T3 time-out;CM-MAC=d4:3f:cb:e6:37:cd;CMTS-MAC=00:01:5c:7d:72:68;CM-QOS=1.1;CM-VER=3.1;"
09/24/2019 04:52 82000800 3 "16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=d4:3f:cb:e6:37:cd;CMTS-MAC=00:01:5c:7d:72:68;CM-QOS=1.1;CM-VER=3.1;"
09/24/2019 04:52 82000300 3 "Ranging Request Retries exhausted;CM-MAC=d4:3f:cb:e6:37:cd;CMTS-MAC=00:01:5c:7d:72:68;CM-QOS=1.1;CM-VER=3.1;"
09/24/2019 04:52 82000200 3 "No Ranging Response received - T3 time-out;CM-MAC=d4:3f:cb:e6:37:cd;CMTS-MAC=00:01:5c:7d:72:68;CM-QOS=1.1;CM-VER=3.1;"
09/24/2019 04:51 82000800 3 "16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=d4:3f:cb:e6:37:cd;CMTS-MAC=00:01:5c:7d:72:68;CM-QOS=1.1;CM-VER=3.1;"
09/24/2019 04:51 82000300 3 "Ranging Request Retries exhausted;CM-MAC=d4:3f:cb:e6:37:cd;CMTS-MAC=00:01:5c:7d:72:68;CM-QOS=1.1;CM-VER=3.1;"
09/24/2019 04:51 82000200 3 "No Ranging Response received - T3 time-out;CM-MAC=d4:3f:cb:e6:37:cd;CMTS-MAC=00:01:5c:7d:72:68;CM-QOS=1.1;CM-VER=3.1;"
09/24/2019 04:47 82000800 3 "16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=d4:3f:cb:e6:37:cd;CMTS-MAC=00:01:5c:7d:72:68;CM-QOS=1.1;CM-VER=3.1;"
09/24/2019 04:47 82000300 3 "Ranging Request Retries exhausted;CM-MAC=d4:3f:cb:e6:37:cd;CMTS-MAC=00:01:5c:7d:72:68;CM-QOS=1.1;CM-VER=3.1;"
09/24/2019 04:47 82000200 3 "No Ranging Response received - T3 time-out;CM-MAC=d4:3f:cb:e6:37:cd;CMTS-MAC=00:01:5c:7d:72:68;CM-QOS=1.1;CM-VER=3.1;"
09/24/2019 04:46 82000800 3 "16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=d4:3f:cb:e6:37:cd;CMTS-MAC=00:01:5c:7d:72:68;CM-QOS=1.1;CM-VER=3.1;"
09/24/2019 04:46 82000300 3 "Ranging Request Retries exhausted;CM-MAC=d4:3f:cb:e6:37:cd;CMTS-MAC=00:01:5c:7d:72:68;CM-QOS=1.1;CM-VER=3.1;"
09/24/2019 04:46 82000200 3 "No Ranging Response received - T3 time-out;CM-MAC=d4:3f:cb:e6:37:cd;CMTS-MAC=00:01:5c:7d:72:68;CM-QOS=1.1;CM-VER=3.1;"
09/24/2019 04:45 82000800 3 "16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=d4:3f:cb:e6:37:cd;CMTS-MAC=00:01:5c:7d:72:68;CM-QOS=1.1;CM-VER=3.1;"
09/24/2019 04:45 82000300 3 "Ranging Request Retries exhausted;CM-MAC=d4:3f:cb:e6:37:cd;CMTS-MAC=00:01:5c:7d:72:68;CM-QOS=1.1;CM-VER=3.1;"
09/24/2019 04:45 82000200 3 "No Ranging Response received - T3 time-out;CM-MAC=d4:3f:cb:e6:37:cd;CMTS-MAC=00:01:5c:7d:72:68;CM-QOS=1.1;CM-VER=3.1;"
09/24/2019 04:41 82000800 3 "16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=d4:3f:cb:e6:37:cd;CMTS-MAC=00:01:5c:7d:72:68;CM-QOS=1.1;CM-VER=3.1;"
09/24/2019 04:41 82000300 3 "Ranging Request Retries exhausted;CM-MAC=d4:3f:cb:e6:37:cd;CMTS-MAC=00:01:5c:7d:72:68;CM-QOS=1.1;CM-VER=3.1;"
09/24/2019 04:41 82000200 3 "No Ranging Response received - T3 time-out;CM-MAC=d4:3f:cb:e6:37:cd;CMTS-MAC=00:01:5c:7d:72:68;CM-QOS=1.1;CM-VER=3.1;"
09/24/2019 04:41 82000800 3 "16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=d4:3f:cb:e6:37:cd;CMTS-MAC=00:01:5c:7d:72:68;CM-QOS=1.1;CM-VER=3.1;"

 

 
Frequent Visitor

Re: connection issues.

Connection

The status listed show the connection state of the cable modem. They are used by your service provider to evaluate the operation of the cable modem.

Startup Procedure
Procedure Status Comment
Acquire Downstream Channel 483000000 Hz Locked
Connectivity State OK Operational
Boot State OK Operational
Configuration File OK
Security Enabled BPI+
DOCSIS Network Access Enabled Allowed  

 
Downstream Bonded Channels
Channel ID Lock Status Modulation Frequency Power SNR/MER Corrected Uncorrectables
2 Locked QAM256 483000000 Hz -8.8 dBmV 41.3 dB 25 61
1 Locked QAM256 477000000 Hz -8.8 dBmV 41.4 dB 26 55
3 Locked QAM256 489000000 Hz -8.7 dBmV 41.3 dB 23 69
4 Locked QAM256 495000000 Hz -8.6 dBmV 41.4 dB 18 77
5 Locked QAM256 501000000 Hz -8.7 dBmV 41.3 dB 19 73
6 Locked QAM256 507000000 Hz -8.6 dBmV 41.4 dB 20 78
7 Locked QAM256 513000000 Hz -8.6 dBmV 41.4 dB 15 88
8 Locked QAM256 519000000 Hz -8.7 dBmV 41.1 dB 25 72
9 Locked QAM256 525000000 Hz -8.9 dBmV 41.0 dB 17 47
10 Locked QAM256 531000000 Hz -8.9 dBmV 41.0 dB 12 53
11 Locked QAM256 537000000 Hz -9.2 dBmV 40.7 dB 38 57
12 Locked QAM256 543000000 Hz -9.3 dBmV 40.6 dB 16 54
13 Locked QAM256 555000000 Hz -9.3 dBmV 40.5 dB 14 53
14 Locked QAM256 561000000 Hz -9.3 dBmV 40.4 dB 9 57
15 Locked QAM256 567000000 Hz -9.1 dBmV 40.5 dB 12 52
16 Locked QAM256 573000000 Hz -9.3 dBmV 40.3 dB 15 89
17 Locked QAM256 579000000 Hz -9.5 dBmV 40.2 dB 33 70
18 Locked QAM256 585000000 Hz -9.6 dBmV 40.1 dB 17 52
19 Locked QAM256 591000000 Hz -9.9 dBmV 40.1 dB 43 58
20 Locked QAM256 597000000 Hz -10.0 dBmV 39.8 dB 13 55
21 Locked QAM256 603000000 Hz -10.0 dBmV 39.9 dB 15 51
22 Locked QAM256 609000000 Hz -10.5 dBmV 39.7 dB 14 56
23 Locked QAM256 615000000 Hz -10.6 dBmV 39.6 dB 29 58
24 Locked QAM256 621000000 Hz -10.6 dBmV 39.0 dB 24 81
25 Locked QAM256 627000000 Hz -11.0 dBmV 39.0 dB 11 58
26 Locked QAM256 633000000 Hz -10.9 dBmV 39.4 dB 12 61
27 Locked QAM256 639000000 Hz -11.0 dBmV 39.3 dB 15 54
33 Locked Other 690000000 Hz -11.1 dBmV 35.8 dB 2294064596 3
34 Not Locked QAM256 0 Hz 0.0 dBmV 42.1 dB 19 64
35 Locked QAM256 453000000 Hz -7.7 dBmV 40.5 dB 10 38
36 Locked QAM256 459000000 Hz -8.1 dBmV 41.8 dB 10 34
37 Locked QAM256 465000000 Hz -8.4 dBmV 41.5 dB 28 36



 
Upstream Bonded Channels
Channel Channel ID Lock Status US Channel Type Frequency Width Power
1 1 Locked SC-QAM Upstream 35800000 Hz 6400000 Hz 54.0 dBmV
2 2 Locked SC-QAM Upstream 29400000 Hz 6400000 Hz 49.0 dBmV
3 3 Locked SC-QAM Upstream 23000000 Hz 6400000 Hz 43.0 dBmV
4 4 Locked SC-QAM Upstream 16600000 Hz 6400000 Hz 54.0 dBmV



 

Current System Time: Tue Sep 24 05:24:04 2019

Diamond Problem Solver

Re: connection issues.

All of your signal levels are too low and out of spec. You need at least 7 dB back, try and see if you can either remove any extra splitters or have a tech out

I am a Retired Official Comcast Employee
We ask that you post publicly so people with similar questions may benefit from the conversation.
Was your question answered? Mark a post as the Best Answer!
Expert

Re: connection issues.

In a self troubleshooting 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-1002 MHz, bi-directional, and no gold colored garbage types like GE, RadioShack, RCA, Philips, Leviton, Magnavox, and Rocketfish from big box stores like Home Depot, Lowes, Target, Wal-Mart etc. Splitters should be swapped with known to be good / new ones to test

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.



I am not a Comcast Employee.
I am a Customer Expert volunteering my time to help other customers here in the Forums.
We ask that you post publicly so people with similar questions may benefit from the conversation.
Was your question answered? Mark the post as Best Answer!
Frequent Visitor

Re: connection issues.

Thank you both.

Would I just call and ask for a tech to come out. When I talk to them on the phone, they say the line is fine.  The speed test work fine ect. just have severe latency and lag issues.

 

Diamond Problem Solver

Re: connection issues.

I escalated it here, there’ll be a response soon from an Official Employee and work with them to get an appointment

I am a Retired Official Comcast Employee
We ask that you post publicly so people with similar questions may benefit from the conversation.
Was your question answered? Mark a post as the Best Answer!
Frequent Visitor

Re: connection issues.

Thank you.  Just an update.

I removed all splitters and all cable drops going to the TV's and only have the cable coming into the house, one barrel conector and a 30 foot cable going to my modem. The numbers looks way better i think. Here they are.

Startup Procedure
Procedure Status Comment
Acquire Downstream Channel 483000000 Hz Locked
Connectivity State OK Operational
Boot State OK Operational
Configuration File OK
Security Enabled BPI+
DOCSIS Network Access Enabled Allowed  

 

 
Downstream Bonded Channels
Channel ID Lock Status Modulation Frequency Power SNR/MER Corrected Uncorrectables
2 Locked QAM256 483000000 Hz 1.2 dBmV 42.6 dB 0 0
1 Locked QAM256 477000000 Hz 1.3 dBmV 42.7 dB 0 0
3 Locked QAM256 489000000 Hz 1.2 dBmV 42.6 dB 0 0
4 Locked QAM256 495000000 Hz 1.2 dBmV 42.7 dB 0 0
5 Locked QAM256 501000000 Hz 1.2 dBmV 42.7 dB 0 0
6 Locked QAM256 507000000 Hz 1.3 dBmV 42.6 dB 0 0
7 Locked QAM256 513000000 Hz 1.3 dBmV 42.6 dB 0 0
8 Locked QAM256 519000000 Hz 1.2 dBmV 42.4 dB 0 0
9 Locked QAM256 525000000 Hz 1.1 dBmV 42.4 dB 0 0
10 Locked QAM256 531000000 Hz 1.1 dBmV 42.2 dB 0 0
11 Locked QAM256 537000000 Hz 1.2 dBmV 42.2 dB 0 0
12 Locked QAM256 543000000 Hz 1.1 dBmV 42.0 dB 0 0
13 Locked QAM256 555000000 Hz 1.1 dBmV 42.0 dB 0 0
14 Locked QAM256 561000000 Hz 1.1 dBmV 42.1 dB 0 0
15 Locked QAM256 567000000 Hz 1.1 dBmV 42.0 dB 0 0
16 Locked QAM256 573000000 Hz 1.0 dBmV 42.0 dB 0 0
17 Locked QAM256 579000000 Hz 0.9 dBmV 41.8 dB 0 0
18 Locked QAM256 585000000 Hz 0.7 dBmV 41.7 dB 0 0
19 Locked QAM256 591000000 Hz 0.8 dBmV 41.7 dB 0 0
20 Locked QAM256 597000000 Hz 0.8 dBmV 41.7 dB 0 0
21 Locked QAM256 603000000 Hz 0.7 dBmV 41.5 dB 0 0
22 Locked QAM256 609000000 Hz 0.5 dBmV 41.4 dB 0 0
23 Locked QAM256 615000000 Hz 0.3 dBmV 41.5 dB 0 0
24 Locked QAM256 621000000 Hz 0.3 dBmV 41.4 dB 0 0
25 Locked QAM256 627000000 Hz -0.1 dBmV 41.2 dB 0 0
26 Locked QAM256 633000000 Hz -0.1 dBmV 41.3 dB 0 0
27 Locked QAM256 639000000 Hz -0.2 dBmV 41.3 dB 0 0
33 Locked Other 690000000 Hz 0.1 dBmV 39.8 dB 95075191 0
34 Not Locked QAM256 0 Hz 0.0 dBmV 43.3 dB 0 0
35 Locked QAM256 453000000 Hz 2.1 dBmV 43.1 dB 0 0
36 Locked QAM256 459000000 Hz 1.8 dBmV 43.0 dB 0 0
37 Locked QAM256 465000000 Hz 1.7 dBmV 42.8 dB 0 0


 

 
Upstream Bonded Channels
Channel Channel ID Lock Status US Channel Type Frequency Width Power
1 1 Locked SC-QAM Upstream 35800000 Hz 6400000 Hz 46.0 dBmV
2 2 Locked SC-QAM Upstream 29400000 Hz 6400000 Hz 38.0 dBmV
3 3 Locked SC-QAM Upstream 23000000 Hz 6400000 Hz 46.0 dBmV
4 4 Locked SC-QAM Upstream 16600000 Hz 6400000 Hz 43.0 dBmV


 

 

Current System Time: Tue Sep 24 12:34:00 2019

 

Diamond Problem Solver

Re: connection issues.

It does, how many/what did you remove? If you put them back, put the line to your modem first in line on the splitters and see what you get.

I am a Retired Official Comcast Employee
We ask that you post publicly so people with similar questions may benefit from the conversation.
Was your question answered? Mark a post as the Best Answer!
Frequent Visitor

Re: connection issues.

Ok not sure why they decided to run it the way they did, but the cable modem was the last itme on a the string. So they came into the crawl space with cable from pole. to a barrel connector, then 35 foot cable to a spliter. off of that spliter one 10 foot cable to tv then another 35 foot cable back into crawl space to another spliter. off of this splitter are two. 35 foot cables one to the cable modem and one to the second tv.. I removed it all but the barrel connector and one, 35 foot cable to modem.

Diamond Problem Solver

Re: connection issues.

The best option would be a 2 way splitter, one output to your modem and the other output feeds the rest. Then retest your levels

I am a Retired Official Comcast Employee
We ask that you post publicly so people with similar questions may benefit from the conversation.
Was your question answered? Mark a post as the Best Answer!
Frequent Visitor

Re: connection issues.

Yes sir, I agree.

First I will wait and see if this fixes the problem before continuing. I still have a lot of this showing up in the log.

Date Time Event ID Event Level Description
09/24/2019 13:09 82000200 3 "No Ranging Response received - T3 time-out;CM-MAC=d4:3f:cb:e6:37:cd;CMTS-MAC=00:01:5c:7d:72:68;CM-QOS=1.1;CM-VER=3.1;"
09/24/2019 13:09 82000800 3 "16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=d4:3f:cb:e6:37:cd;CMTS-MAC=00:01:5c:7d:72:68;CM-QOS=1.1;CM-VER=3.1;"
09/24/2019 13:09 82000300 3 "Ranging Request Retries exhausted;CM-MAC=d4:3f:cb:e6:37:cd;CMTS-MAC=00:01:5c:7d:72:68;CM-QOS=1.1;CM-VER=3.1;"
09/24/2019 13:09 82000200 3 "No Ranging Response received - T3 time-out;CM-MAC=d4:3f:cb:e6:37:cd;CMTS-MAC=00:01:5c:7d:72:68;CM-QOS=1.1;CM-VER=3.1;"
09/24/2019 13:07 82000800 3 "16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=d4:3f:cb:e6:37:cd;CMTS-MAC=00:01:5c:7d:72:68;CM-QOS=1.1;CM-VER=3.1;"
09/24/2019 13:07 82000300 3 "Ranging Request Retries exhausted;CM-MAC=d4:3f:cb:e6:37:cd;CMTS-MAC=00:01:5c:7d:72:68;CM-QOS=1.1;CM-VER=3.1;"
09/24/2019 13:07 82000200 3 "No Ranging Response received - T3 time-out;CM-MAC=d4:3f:cb:e6:37:cd;CMTS-MAC=00:01:5c:7d:72:68;CM-QOS=1.1;CM-VER=3.1;"
09/24/2019 13:04 82000800 3 "16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=d4:3f:cb:e6:37:cd;CMTS-MAC=00:01:5c:7d:72:68;CM-QOS=1.1;CM-VER=3.1;"
09/24/2019 13:04 82000300 3 "Ranging Request Retries exhausted;CM-MAC=d4:3f:cb:e6:37:cd;CMTS-MAC=00:01:5c:7d:72:68;CM-QOS=1.1;CM-VER=3.1;"
09/24/2019 13:04 82000200 3 "No Ranging Response received - T3 time-out;CM-MAC=d4:3f:cb:e6:37:cd;CMTS-MAC=00:01:5c:7d:72:68;CM-QOS=1.1;CM-VER=3.1;"
09/24/2019 13:02 82000800 3 "16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=d4:3f:cb:e6:37:cd;CMTS-MAC=00:01:5c:7d:72:68;CM-QOS=1.1;CM-VER=3.1;"
09/24/2019 13:02 82000300 3 "Ranging Request Retries exhausted;CM-MAC=d4:3f:cb:e6:37:cd;CMTS-MAC=00:01:5c:7d:72:68;CM-QOS=1.1;CM-VER=3.1;"
09/24/2019 13:02 82000200 3 "No Ranging Response received - T3 time-out;CM-MAC=d4:3f:cb:e6:37:cd;CMTS-MAC=00:01:5c:7d:72:68;CM-QOS=1.1;CM-VER=3.1;"
09/24/2019 13:02 82000800 3 "16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=d4:3f:cb:e6:37:cd;CMTS-MAC=00:01:5c:7d:72:68;CM-QOS=1.1;CM-VER=3.1;"
09/24/2019 13:02 82000300 3 "Ranging Request Retries exhausted;CM-MAC=d4:3f:cb:e6:37:cd;CMTS-MAC=00:01:5c:7d:72:68;CM-QOS=1.1;CM-VER=3.1;"
09/24/2019 13:02 82000200 3 "No Ranging Response received - T3 time-out;CM-MAC=d4:3f:cb:e6:37:cd;CMTS-MAC=00:01:5c:7d:72:68;CM-QOS=1.1;CM-VER=3.1;"
09/24/2019 12:59 82000800 3 "16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=d4:3f:cb:e6:37:cd;CMTS-MAC=00:01:5c:7d:72:68;CM-QOS=1.1;CM-VER=3.1;"
09/24/2019 12:59 82000300 3 "Ranging Request Retries exhausted;CM-MAC=d4:3f:cb:e6:37:cd;CMTS-MAC=00:01:5c:7d:72:68;CM-QOS=1.1;CM-VER=3.1;"
09/24/2019 12:59 82000200 3 "No Ranging Response received - T3 time-out;CM-MAC=d4:3f:cb:e6:37:cd;CMTS-MAC=00:01:5c:7d:72:68;CM-QOS=1.1;CM-VER=3.1;"
09/24/2019 12:57 82000800 3 "16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=d4:3f:cb:e6:37:cd;CMTS-MAC=00:01:5c:7d:72:68;CM-QOS=1.1;CM-VER=3.1;"
09/24/2019 12:57 82000300 3 "Ranging Request Retries exhausted;CM-MAC=d4:3f:cb:e6:37:cd;CMTS-MAC=00:01:5c:7d:72:68;CM-QOS=1.1;CM-VER=3.1;"
09/24/2019 12:57 82000200 3 "No Ranging Response received - T3 time-out;CM-MAC=d4:3f:cb:e6:37:cd;CMTS-MAC=00:01:5c:7d:72:68;CM-QOS=1.1;CM-VER=3.1;"
09/24/2019 12:55 82000800 3 "16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=d4:3f:cb:e6:37:cd;CMTS-MAC=00:01:5c:7d:72:68;CM-QOS=1.1;CM-VER=3.1;"
09/24/2019 12:55 82000300 3 "Ranging Request Retries exhausted;CM-MAC=d4:3f:cb:e6:37:cd;CMTS-MAC=00:01:5c:7d:72:68;CM-QOS=1.1;CM-VER=3.1;"
09/24/2019 12:55 82000200 3 "No Ranging Response received - T3 time-out;CM-MAC=d4:3f:cb:e6:37:cd;CMTS-MAC=00:01:5c:7d:72:68;CM-QOS=1.1;CM-VER=3.1;"
09/24/2019 12:52 82000800 3 "16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=d4:3f:cb:e6:37:cd;CMTS-MAC=00:01:5c:7d:72:68;CM-QOS=1.1;CM-VER=3.1;"
09/24/2019 12:52 82000300 3 "Ranging Request Retries exhausted;CM-MAC=d4:3f:cb:e6:37:cd;CMTS-MAC=00:01:5c:7d:72:68;CM-QOS=1.1;CM-VER=3.1;"
09/24/2019 12:52 82000200 3 "No Ranging Response received - T3 time-out;CM-MAC=d4:3f:cb:e6:37:cd;CMTS-MAC=00:01:5c:7d:72:68;CM-QOS=1.1;CM-VER=3.1;"
09/24/2019 12:51 82000800 3 "16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=d4:3f:cb:e6:37:cd;CMTS-MAC=00:01:5c:7d:72:68;CM-QOS=1.1;CM-VER=3.1;"
09/24/2019 12:51 82000300 3 "Ranging Request Retries exhausted;CM-MAC=d4:3f:cb:e6:37:cd;CMTS-MAC=00:01:5c:7d:72:68;CM-QOS=1.1;CM-VER=3.1;"
09/24/2019 12:51 82000200 3 "No Ranging Response received - T3 time-out;CM-MAC=d4:3f:cb:e6:37:cd;CMTS-MAC=00:01:5c:7d:72:68;CM-QOS=1.1;CM-VER=3.1;"
09/24/2019 12:49 82000800 3 "16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=d4:3f:cb:e6:37:cd;CMTS-MAC=00:01:5c:7d:72:68;CM-QOS=1.1;CM-VER=3.1;"
09/24/2019 12:49 82000300 3 "Ranging Request Retries exhausted;CM-MAC=d4:3f:cb:e6:37:cd;CMTS-MAC=00:01:5c:7d:72:68;CM-QOS=1.1;CM-VER=3.1;"
09/24/2019 12:49 82000200 3 "No Ranging Response received - T3 time-out;CM-MAC=d4:3f:cb:e6:37:cd;CMTS-MAC=00:01:5c:7d:72:68;CM-QOS=1.1;CM-VER=3.1;"
09/24/2019 12:46 82000800 3 "16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=d4:3f:cb:e6:37:cd;CMTS-MAC=00:01:5c:7d:72:68;CM-QOS=1.1;CM-VER=3.1;"
09/24/2019 12:46 82000300 3 "Ranging Request Retries exhausted;CM-MAC=d4:3f:cb:e6:37:cd;CMTS-MAC=00:01:5c:7d:72:68;CM-QOS=1.1;CM-VER=3.1;"
09/24/2019 12:46 82000200 3 "No Ranging Response received - T3 time-out;CM-MAC=d4:3f:cb:e6:37:cd;CMTS-MAC=00:01:5c:7d:72:68;CM-QOS=1.1;CM-VER=3.1;"
09/24/2019 12:46 82000800 3 "16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=d4:3f:cb:e6:37:cd;CMTS-MAC=00:01:5c:7d:72:68;CM-QOS=1.1;CM-VER=3.1;"
09/24/2019 12:46 82000300 3 "Ranging Request Retries exhausted;CM-MAC=d4:3f:cb:e6:37:cd;CMTS-MAC=00:01:5c:7d:72:68;CM-QOS=1.1;CM-VER=3.1;"
09/24/2019 12:46 82000200 3 "No Ranging Response received - T3 time-out;CM-MAC=d4:3f:cb:e6:37:cd;CMTS-MAC=00:01:5c:7d:72:68;CM-QOS=1.1;CM-VER=3.1;"
09/24/2019 12:45 82000800 3 "16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=d4:3f:cb:e6:37:cd;CMTS-MAC=00:01:5c:7d:72:68;CM-QOS=1.1;CM-VER=3.1;"
09/24/2019 12:45 82000300 3 "Ranging Request Retries exhausted;CM-MAC=d4:3f:cb:e6:37:cd;CMTS-MAC=00:01:5c:7d:72:68;CM-QOS=1.1;CM-VER=3.1;"
09/24/2019 12:45 82000200 3 "No Ranging Response received - T3 time-out;CM-MAC=d4:3f:cb:e6:37:cd;CMTS-MAC=00:01:5c:7d:72:68;CM-QOS=1.1;CM-VER=3.1;"
09/24/2019 12:41 82000800 3 "16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=d4:3f:cb:e6:37:cd;CMTS-MAC=00:01:5c:7d:72:68;CM-QOS=1.1;CM-VER=3.1;"
09/24/2019 12:41 82000300 3 "Ranging Request Retries exhausted;CM-MAC=d4:3f:cb:e6:37:cd;CMTS-MAC=00:01:5c:7d:72:68;CM-QOS=1.1;CM-VER=3.1;"
09/24/2019 12:41 82000200 3 "No Ranging Response received - T3 time-out;CM-MAC=d4:3f:cb:e6:37:cd;CMTS-MAC=00:01:5c:7d:72:68;CM-QOS=1.1;CM-VER=3.1;"
09/24/2019 12:40 82000800 3 "16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=d4:3f:cb:e6:37:cd;CMTS-MAC=00:01:5c:7d:72:68;CM-QOS=1.1;CM-VER=3.1;"
09/24/2019 12:40 82000300 3 "Ranging Request Retries exhausted;CM-MAC=d4:3f:cb:e6:37:cd;CMTS-MAC=00:01:5c:7d:72:68;CM-QOS=1.1;CM-VER=3.1;"
09/24/2019 12:40 82000200 3 "No Ranging Response received - T3 time-out;CM-MAC=d4:3f:cb:e6:37:cd;CMTS-MAC=00:01:5c:7d:72:68;CM-QOS=1.1;CM-VER=3.1;"
09/24/2019 12:39 82000800 3 "16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=d4:3f:cb:e6:37:cd;CMTS
Frequent Visitor

Re: connection issues.

So that did not fix my connection issues. Around 8:30 pm EST we started getting extream lag in games and bring up web pages. I believe the problem lies outside my house,since i have removed all spliters and drops to the tv's. I only have one 35 foot coaxe  and a barrel conector left in the crawl space.  I could use a good number to call and get this resolved. If you look at all the T3 errors and the frequency, ( 16 every couple of minutes). I think this points towards the isp or thier connection. this trouble started 4 days ago. The modem is new as of yesterday and changing it did not fix the issue.

Frequent Visitor

Re: connection issues.

Update.  I have a tech coming out tomorrow. They are charging $70 unless the tech finds the trouble on comcast's side. Anything specific I should have him look at or check?

Official Employee

Re: connection issues.

Greetings, kbad! We appreciate you taking the time to reach out to us here on the forums. We hope you are having an amazing day. We also appreciate you trying to get this resolved on your own. We can certainly have a further look into the signals so you know what to mention to the tech when he comes out. Can you please send us a PM with your first and last name so we may further assist you?

 

To send a private message, please click the name "Comcast_Support" then select "Send a Message" on the right side.


I am an Official Comcast Employee.
Official Employees are from multiple teams within Comcast: CARE, Product, Leadership. We ask that you post publicly so people with similar questions may benefit from the conversation.
Was your question answered? Mark the post as Best Answer!
Frequent Visitor

Re: connection issues.

PM sent

 

Frequent Visitor

Re: connection issues.

Tech was out today. While explaining the problem and some of the symptoms to him he informed me he knew nothing about T3 ranging errors or that the modem could capture those errors. He proceded to tell me that i needed a noise filter and asked if i had " airplanes or big trucks go by frequently",  SMH.  So he installed an inline filter, then checked his phone ( the only piece of test equipment he used)., and said wait i see a problem and it is one the pole. I asked how he knew and he said because his phone program had 3 red X's. We walked to the pole and he looked up and said yep there is your problem, " a signal blocker".  He proceded to remove the "blocker" checked his phone and said that did it all fixed, no more red X's, I know have green check marks.  he did agree that I will need a new line from the pole to the house to a proper termination point or box.  We will see if the problem is fixed.   Oh I forgot about 45 min before he got there, after 4 days of constant T3 errors, they completly stopped.. 

 

I hope this or the new drop from the pole will finally put this trouble to rest.

Frequent Visitor

Re: connection issues.

Update for those following. After the T3 errors stoped, my connection has been rock solid. So if you event log looks anything like mine did, start your troubleshooting at the T3 errors.