Community Forum

No Ranging Response received - T3 time-out

Xfinity Forum Archive
About the archive project

Xfinity Forum Archive...

This is an archived section of the community.

Content in this area has been identified as outdated or irrelevant.

This change was done in an effort to make the forum easier to use and to keep only the most helpful and recent content active.

Post your questions in the Xfinity Community

Frequent Visitor

No Ranging Response received - T3 time-out

For the past 5 years or better every year around February - March I get these issues and they persist for months on end where I have intermittent connection issues. I have had Comcast technicians come to my home (multiple technictions) I have a brand new modem (Motorola MB8600) and router (Asus AC880U AC3100). The drop is about 5 feet from my computer (literally). Here is my modems logs. 

 

 Time   Priority   Description 
 Mon Feb 26 17:59:56 2018    Critical (3)   No Ranging Response received - T3 time-out;CM-MAC=00:40:36:49:e1:68;CMTS-MAC=00:01:5c:89:a4:59;CM-QOS=1.1;CM-VER=3.1;" 
 Mon Feb 26 18:00:01 2018    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:49:e1:68;CMTS-MAC=00:01:5c:89:a4:59;CM-QOS=1.1;CM-VER=3.1;" 
 Mon Feb 26 18:00:08 2018    Critical (3)   No Ranging Response received - T3 time-out;CM-MAC=00:40:36:49:e1:68;CMTS-MAC=00:01:5c:89:a4:59;CM-QOS=1.1;CM-VER=3.1;" 
 Mon Feb 26 18:00:25 2018    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:49:e1:68;CMTS-MAC=00:01:5c:89:a4:59;CM-QOS=1.1;CM-VER=3.1;" 
 Mon Feb 26 18:00:25 2018    Critical (3)   Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=00:40:36:49:e1:68;CMTS-MAC=00:01:5c:89:a4:59;CM-QOS=1.1;CM-VER=3.1;" 
 Mon Feb 26 18:00:25 2018    Critical (3)   16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=00:40:36:49:e1:68;CMTS-MAC=00:01:5c:89:a4:59;CM-QOS=1.1;CM-VER=3.1;" 
 Mon Feb 26 18:00:30 2018    Critical (3)   No Ranging Response received - T3 time-out;CM-MAC=00:40:36:49:e1:68;CMTS-MAC=00:01:5c:89:a4:59;CM-QOS=1.1;CM-VER=3.1;" 
 Mon Feb 26 18:00:41 2018    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:49:e1:68;CMTS-MAC=00:01:5c:89:a4:59;CM-QOS=1.1;CM-VER=3.1;" 
 Mon Feb 26 18:00:41 2018    Critical (3)   Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=00:40:36:49:e1:68;CMTS-MAC=00:01:5c:89:a4:59;CM-QOS=1.1;CM-VER=3.1;" 
 Mon Feb 26 18:00:41 2018    Critical (3)   16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=00:40:36:49:e1:68;CMTS-MAC=00:01:5c:89:a4:59;CM-QOS=1.1;CM-VER=3.1;" 
 Mon Feb 26 18:01:01 2018    Critical (3)   No Ranging Response received - T3 time-out;CM-MAC=00:40:36:49:e1:68;CMTS-MAC=00:01:5c:89:a4:59;CM-QOS=1.1;CM-VER=3.1;" 
 Mon Feb 26 18:01:39 2018    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:49:e1:68;CMTS-MAC=00:01:5c:89:a4:59;CM-QOS=1.1;CM-VER=3.1;" 
 Mon Feb 26 18:01:50 2018    Critical (3)   No Ranging Response received - T3 time-out;CM-MAC=00:40:36:49:e1:68;CMTS-MAC=00:01:5c:89:a4:59;CM-QOS=1.1;CM-VER=3.1;" 
 Mon Feb 26 18:02:27 2018    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:49:e1:68;CMTS-MAC=00:01:5c:89:a4:59;CM-QOS=1.1;CM-VER=3.1;" 
 Mon Feb 26 18:02:34 2018    Critical (3)   No Ranging Response received - T3 time-out;CM-MAC=00:40:36:49:e1:68;CMTS-MAC=00:01:5c:89:a4:59;CM-QOS=1.1;CM-VER=3.1;" 
 Mon Feb 26 18:02:51 2018    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:49:e1:68;CMTS-MAC=00:01:5c:89:a4:59;CM-QOS=1.1;CM-VER=3.1;" 
 Mon Feb 26 18:03:13 2018    Critical (3)   No Ranging Response received - T3 time-out;CM-MAC=00:40:36:49:e1:68;CMTS-MAC=00:01:5c:89:a4:59;CM-QOS=1.1;CM-VER=3.1;" 
 Mon Feb 26 18:03:39 2018    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:49:e1:68;CMTS-MAC=00:01:5c:89:a4:59;CM-QOS=1.1;CM-VER=3.1;" 
 Mon Feb 26 18:03:46 2018    Critical (3)   No Ranging Response received - T3 time-out;CM-MAC=00:40:36:49:e1:68;CMTS-MAC=00:01:5c:89:a4:59;CM-QOS=1.1;CM-VER=3.1;" 
 Mon Feb 26 18:04:03 2018    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:49:e1:68;CMTS-MAC=00:01:5c:89:a4:59;CM-QOS=1.1;CM-VER=3.1;" 
 Mon Feb 26 18:04:23 2018    Critical (3)   No Ranging Response received - T3 time-out;CM-MAC=00:40:36:49:e1:68;CMTS-MAC=00:01:5c:89:a4:59;CM-QOS=1.1;CM-VER=3.1;" 
 Mon Feb 26 18:04:48 2018    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:49:e1:68;CMTS-MAC=00:01:5c:89:a4:59;CM-QOS=1.1;CM-VER=3.1;" 
 Mon Feb 26 18:04:49 2018    Critical (3)   No Ranging Response received - T3 time-out;CM-MAC=00:40:36:49:e1:68;CMTS-MAC=00:01:5c:89:a4:59;CM-QOS=1.1;CM-VER=3.1;" 
 Mon Feb 26 18:04:49 2018    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:49:e1:68;CMTS-MAC=00:01:5c:89:a4:59;CM-QOS=1.1;CM-VER=3.1;" 
 Mon Feb 26 18:04:50 2018    Critical (3)   No Ranging Response received - T3 time-out;CM-MAC=00:40:36:49:e1:68;CMTS-MAC=00:01:5c:89:a4:59;CM-QOS=1.1;CM-VER=3.1;" 
 Mon Feb 26 18:04:54 2018    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:49:e1:68;CMTS-MAC=00:01:5c:89:a4:59;CM-QOS=1.1;CM-VER=3.1;" 
 Mon Feb 26 18:05:08 2018    Critical (3)   No Ranging Response received - T3 time-out;CM-MAC=00:40:36:49:e1:68;CMTS-MAC=00:01:5c:89:a4:59;CM-QOS=1.1;CM-VER=3.1;" 
 Mon Feb 26 18:05:43 2018    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:49:e1:68;CMTS-MAC=00:01:5c:89:a4:59;CM-QOS=1.1;CM-VER=3.1;" 
 Mon Feb 26 18:05:43 2018    Critical (3)   Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=00:40:36:49:e1:68;CMTS-MAC=00:01:5c:89:a4:59;CM-QOS=1.1;CM-VER=3.1;" 
 Mon Feb 26 18:05:43 2018    Critical (3)   16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=00:40:36:49:e1:68;CMTS-MAC=00:01:5c:89:a4:59;CM-QOS=1.1;CM-VER=3.1;" 
 Mon Feb 26 18:05:49 2018    Critical (3)   No Ranging Response received - T3 time-out;CM-MAC=00:40:36:49:e1:68;CMTS-MAC=00:01:5c:89:a4:59;CM-QOS=1.1;CM-VER=3.1;" 
 Mon Feb 26 18:14:24 2018    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:49:e1:68;CMTS-MAC=00:01:5c:89:a4:59;CM-QOS=1.1;CM-VER=3.1;" 
     
     
       
     
Expert

Re: No Ranging Response received - T3 time-out

What do the signal stats look like ? 

Please post the *Downstream Power Level*, the *Upstream Power Level*, and the *SNR* (Signal to Noise Ratio) numbers.




I am not a Comcast Employee.
I am a fellow customer, 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: No Ranging Response received - T3 time-out

Startup Step Status Comment

  
   Acquire Downstream Channel 651000000 Hz Locked
  
   Upstream Connection OK Operational
  
   Boot State OK Operational

  
   Configuration File OK d11_m_mb8600_widebandshowcaseblast_c01.cm
  
   Security Enabled BPI+
  



   Connection Status    
   System Up Time 1 days 00h:48m:06s.00  
  
   Network Access Allowed  
  



   Downstream Bonded Channels  
  
   Channel Lock Status Modulation Channel ID Freq. (MHz) Pwr (dBmV) SNR (d Corrected Uncorrected
1 Locked QAM256 23 651.0 6.8 41.5 0 0
2 Locked QAM256 1 519.0 5.0 41.5 36 130
3 Locked QAM256 2 525.0 5.4 41.8 39 110
4 Locked QAM256 3 531.0 5.4 41.8 25 68
5 Locked QAM256 4 537.0 5.7 41.8 36 23
6 Locked QAM256 5 543.0 5.4 41.7 21 55
7 Locked QAM256 6 549.0 5.4 41.7 21 89
8 Locked QAM256 7 555.0 5.6 41.6 30 80
9 Locked QAM256 8 561.0 5.3 41.4 15 73
10 Locked QAM256 9 567.0 5.9 41.7 35 123
11 Locked QAM256 10 573.0 5.6 41.2 49 91
12 Locked QAM256 11 579.0 6.2 41.7 43 59
13 Locked QAM256 12 585.0 6.0 41.5 27 49
14 Locked QAM256 13 591.0 6.3 41.6 52 11
15 Locked QAM256 14 597.0 6.3 41.6 45 30
16 Locked QAM256 15 603.0 6.3 41.5 22 55
17 Locked QAM256 16 609.0 6.4 41.4 23 51
18 Locked QAM256 17 615.0 6.1 41.5 22 65
19 Locked QAM256 18 621.0 6.8 41.6 27 60
20 Locked QAM256 19 627.0 6.4 41.6 25 59
21 Locked QAM256 20 633.0 6.4 41.5 47 0
22 Locked QAM256 21 639.0 6.2 41.5 0 0
23 Locked QAM256 22 645.0 6.4 41.6 30 1
24 Locked QAM256 24 657.0 6.3 41.2 27 0
25 Locked OFDM PLC 25 708.0 6.5 40.0 0 0



   Upstream Bonded Channels  
  
   Channel Lock Status Channel Type Channel ID Symb. Rate (Ksym/sec) Freq. (MHz) Pwr (dBmV)
1 Locked SC-QAM 57 5120 35.8 41.3
2 Locked SC-QAM 59 5120 23.0 41.8
3 Locked SC-QAM 60 5120 16.6 41.0
4 Locked SC-QAM 58 5120 29.4 41.5
Expert

Re: No Ranging Response received - T3 time-out

Well that's all good but there are three additional signal stats that can cause T3 errors which can't be read by the modem. They can only be read from their end by them polling the CMTS (Cable Modem Termination System) at the local headend facility.

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.

You can call in and ask what these figures are. The Upstream Receive Power Level should fall within the range of -2dB to +2dB with 0dB being in the middle and perfect.

The Upstream SNR should be least 31dB, and the higher it is the better.

The ICFR should be no higher than 2 dB.

You could have an intermittent noise ingress issue in only the upstream channel(s) / return path only somewhere.

They will be able to see whether or not everything is in the green zone and also see a history plot for the modem.




I am not a Comcast Employee.
I am a fellow customer, 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: No Ranging Response received - T3 time-out

Thanks for the Info. I'm pretty familiar with all that, as I said this has been an on and off problem for the past 5 years or better. I've spoken with Comcast Corporate offices a few times about it and they send out the Line technicians to fix everything up. But they never seem to quite fix everything. The only other outlet I haven't reached out to was this forum, so here I am. 

 

And yes I know its the upstream. That is what it has always been in the past. The SNR drops down to around 25dB when the intermittent issue occurs. But like I said for the past 5+ years the Line Technicians, supervising technicians and their regular in-home technicians haven't been able to or don't care enough to fix the issue completely. 

 

It also always happens at the same time. This year it seems to happen every night so far at 5:50PM. It goes for however long (it varies) and then its fine for a little while. Goes out again in the morning. Then again in the afternoon for a little bit. Then again at 5:50PM. It happens throughout the day, but at 5:50PM it goes out like clockwork. Last year it was around 11am and 11pm. The year before that it was around 8PM. 

Frequent Visitor

Re: No Ranging Response received - T3 time-out

This still isn't fixed. Still intermittent issues and packet loss all over the place. Multiple tech visits. One where the guy didn't even show up for the appointment. Multiple calls into tech support. Nobody can help. This is beyond frustrating. 

Frequent Visitor

Re: No Ranging Response received - T3 time-out

Event Log
   Log  
  
 Time   Priority   Description 
 Sun Mar 4 15:45:54 2018    Critical (3)   SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=00:40:36:49:e1:68;CMTS-MAC=00:01:5c:89:a4:59;CM-QOS=1.1;CM-VER=3.1;" 
 Sun Mar 4 15:45:54 2018    Critical (3)   Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:40:36:49:e1:68;CMTS-MAC=00:01:5c:89:a4:59;CM-QOS=1.1;CM-VER=3.1;" 
 Sun Mar 4 15:45:58 2018    Critical (3)   SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=00:40:36:49:e1:68;CMTS-MAC=00:01:5c:89:a4:59;CM-QOS=1.1;CM-VER=3.1;" 
 Sun Mar 4 15:45:58 2018    Critical (3)   Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:40:36:49:e1:68;CMTS-MAC=00:01:5c:89:a4:59;CM-QOS=1.1;CM-VER=3.1;" 
 Sun Mar 4 15:46:04 2018    Critical (3)   SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=00:40:36:49:e1:68;CMTS-MAC=00:01:5c:89:a4:59;CM-QOS=1.1;CM-VER=3.1;" 
 Sun Mar 4 15:46:04 2018    Critical (3)   Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:40:36:49:e1:68;CMTS-MAC=00:01:5c:89:a4:59;CM-QOS=1.1;CM-VER=3.1;" 
 Sun Mar 4 15:47:04 2018    Critical (3)   SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=00:40:36:49:e1:68;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;" 
 Sun Mar 4 15:47:12 2018    Notice (6)   Honoring MDD; IP provisioning mode = IPv6" 
 Sun Mar 4 15:47:22 2018    Warning (5)   ToD request sent- No Response received;CM-MAC=00:40:36:49:e1:68;CMTS-MAC=00:01:5c:89:a4:59;CM-QOS=1.1;CM-VER=3.1;" 
 Sun Mar 4 15:47:23 2018    Critical (3)   SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=00:40:36:49:e1:68;CMTS-MAC=00:01:5c:89:a4:59;CM-QOS=1.1;CM-VER=3.1;" 
 Sun Mar 4 15:47:23 2018    Critical (3)   TFTP Request Retries exceeded, CM unable to register " 
 Sun Mar 4 15:47:25 2018    Warning (5)   ToD request sent- No Response received;CM-MAC=00:40:36:49:e1:68;CMTS-MAC=00:01:5c:89:a4:59;CM-QOS=1.1;CM-VER=3.1;" 
 Sun Mar 4 15:47:28 2018    Critical (3)   SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=00:40:36:49:e1:68;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;" 
 Sun Mar 4 15:47:33 2018    Critical (3)   No Ranging Response received - T3 time-out;CM-MAC=00:40:36:49:e1:68;CMTS-MAC=00:01:5c:89:a4:59;CM-QOS=1.1;CM-VER=3.1;" 
 Sun Mar 4 15:47:36 2018    Notice (6)   Honoring MDD; IP provisioning mode = IPv6" 
 Sun Mar 4 15:46:40 2018    Notice (6)   TLV-11 - unrecognized OID;CM-MAC=00:40:36:49:e1:68;CMTS-MAC=00:01:5c:89:a4:59;CM-QOS=1.1;CM-VER=3.1;" 
 Sun Mar 4 15:53:36 2018    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:49:e1:68;CMTS-MAC=00:01:5c:89:a4:59;CM-QOS=1.1;CM-VER=3.1;" 
 Sun Mar 4 16:11:42 2018    Critical (3)   SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=00:40:36:49:e1:68;CMTS-MAC=00:01:5c:89:a4:59;CM-QOS=1.1;CM-VER=3.1;" 
 Sun Mar 4 16:13:11 2018    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:49:e1:68;CMTS-MAC=00:01:5c:89:a4:59;CM-QOS=1.1;CM-VER=3.1;" 
 Sun Mar 4 16:13:11 2018    Critical (3)   Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=00:40:36:49:e1:68;CMTS-MAC=00:01:5c:89:a4:59;CM-QOS=1.1;CM-VER=3.1;" 
 Sun Mar 4 16:13:11 2018    Critical (3)   16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=00:40:36:49:e1:68;CMTS-MAC=00:01:5c:89:a4:59;CM-QOS=1.1;CM-VER=3.1;" 
 Sun Mar 4 16:13:18 2018    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:49:e1:68;CMTS-MAC=00:01:5c:89:a4:59;CM-QOS=1.1;CM-VER=3.1;" 
 Sun Mar 4 16:17:00 2018    Critical (3)   Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:40:36:49:e1:68;CMTS-MAC=00:01:5c:89:a4:59;CM-QOS=1.1;CM-VER=3.1;" 
 Sun Mar 4 16:17:12 2018    Critical (3)   No Ranging Response received - T3 time-out;CM-MAC=00:40:36:49:e1:68;CMTS-MAC=00:01:5c:89:a4:59;CM-QOS=1.1;CM-VER=3.1;" 
 Sun Mar 4 16:17:13 2018    Critical (3)   Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:40:36:49:e1:68;CMTS-MAC=00:01:5c:89:a4:59;CM-QOS=1.1;CM-VER=3.1;" 
 Sun Mar 4 16:17:16 2018    Critical (3)   No Ranging Response received - T3 time-out;CM-MAC=00:40:36:49:e1:68;CMTS-MAC=00:01:5c:89:a4:59;CM-QOS=1.1;CM-VER=3.1;" 
 Sun Mar 4 16:17:16 2018    Critical (3)   Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:40:36:49:e1:68;CMTS-MAC=00:01:5c:89:a4:59;CM-QOS=1.1;CM-VER=3.1;" 
 Sun Mar 4 16:17:17 2018    Critical (3)   No Ranging Response received - T3 time-out;CM-MAC=00:40:36:49:e1:68;CMTS-MAC=00:01:5c:89:a4:59;CM-QOS=1.1;CM-VER=3.1;" 
 Sun Mar 4 16:17:18 2018    Critical (3)   Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:40:36:49:e1:68;CMTS-MAC=00:01:5c:89:a4:59;CM-QOS=1.1;CM-VER=3.1;" 
 Sun Mar 4 16:17:30 2018    Notice (6)   Honoring MDD; IP provisioning mode = IPv6" 
 Sun Mar 4 16:17:39 2018    Notice (6)   TLV-11 - unrecognized OID;CM-MAC=00:40:36:49:e1:68;CMTS-MAC=00:01:5c:89:a4:59;CM-QOS=1.1;CM-VER=3.1;" 
 Sun Mar 4 20:17:40 2018    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:49:e1:68;CMTS-MAC=00:01:5c:89:a4:59;CM-QOS=1.1;CM-VER=3.1;" 

 

 

   Downstream Bonded Channels  
  
   Channel Lock Status Modulation Channel ID Freq. (MHz) Pwr (dBmV) SNR (d Corrected Uncorrected
1 Locked QAM256 7 555.0 5.6 41.6 693 1149
2 Locked QAM256 1 519.0 5.0 41.8 761 1530
3 Locked QAM256 2 525.0 5.3 41.8 738 1435
4 Locked QAM256 3 531.0 5.3 41.8 785 1626
5 Locked QAM256 4 537.0 5.6 41.9 754 1560
6 Locked QAM256 5 543.0 5.3 41.9 907 1795
7 Locked QAM256 6 549.0 5.4 41.6 703 1734
8 Locked QAM256 8 561.0 5.2 41.2 826 2009
9 Locked QAM256 9 567.0 5.9 41.8 643 1380
10 Locked QAM256 10 573.0 5.4 41.6 740 1664
11 Locked QAM256 11 579.0 6.2 41.8 736 1554
12 Locked QAM256 12 585.0 5.9 41.6 759 1748
13 Locked QAM256 13 591.0 6.3 41.6 950 2111
14 Locked QAM256 14 597.0 6.3 41.8 983 2021
15 Locked QAM256 15 603.0 6.2 41.6 741 1912
16 Locked QAM256 16 609.0 6.4 41.6 952 1850
17 Locked QAM256 17 615.0 6.0 41.6 738 1809
18 Locked QAM256 18 621.0 6.7 41.5 975 1969
19 Locked QAM256 19 627.0 6.4 41.5 910 1733
20 Locked QAM256 20 633.0 6.3 41.6 1009 2091
21 Locked QAM256 21 639.0 6.2 41.5 798 1827
22 Locked QAM256 22 645.0 6.3 41.4 1123 2325
23 Locked QAM256 23 651.0 6.7 41.7 952 2175
24 Locked QAM256 24 657.0 6.2 41.5 1052 2388
25 Locked OFDM PLC 25 708.0 6.6 40.0 0 0



   Upstream Bonded Channels  
  
   Channel Lock Status Channel Type Channel ID Symb. Rate (Ksym/sec) Freq. (MHz) Pwr (dBmV)
1 Locked SC-QAM 59 5120 23.0 40.0
2 Locked SC-QAM 60 5120 16.6 39.3
3 Locked SC-QAM 58 5120 29.4 40.0
4 Locked SC-QAM 57 5120 35.8 39.5

 

Expert

Re: No Ranging Response received - T3 time-out

Hi @J2323 

We aren't going to be able to resolve this for you on the forums by looking at some signal levels from your modem. If you've had this issue for such a long time, we are going to have to get a corporate employee involved to motivate your local system to get this resolved for you.

 

I've asked a Comcast corporate employee to help you. You should expect a reply in this thread. 

 


I am not an employee.
Official Employee

Re: No Ranging Response received - T3 time-out

 

Hello J2323, I show that we have a technician scheduled to come out and repair this issue for you tomorrow. I will reach back out to you to confirm this problem has been resolved, have a good day. 

I am an Official Comcast Employee.
Official Employees are from multiple teams within Comcast: Product, Support, 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: No Ranging Response received - T3 time-out

The Technician never showed up. This is the second time this has happened in two weeks. 

Expert

Re: No Ranging Response received - T3 time-out

You'll want to send @ComcastAmir a message to let them know of the issue. 

 

FYI: They owe you a $20 credit for every tech visit after the first for the same problem.Anda  $20 credit for each missed tech visit. You can also get a credit for your service from the time you first reported the issue until it is resolved. 


I am not an employee.
Official Employee

Re: No Ranging Response received - T3 time-out

 

J2323 wrote: The Technician never showed up. This is the second time this has happened in two weeks.

 

I can get a tech scheduled to come back out, and I can credit you for your missed appointments. Please send me a private message with your full name, street address, and account number by clicking on my name (ComcastAmir) and then "private message me".

I am an Official Comcast Employee.
Official Employees are from multiple teams within Comcast: Product, Support, 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!