Community Forum

T3 / T4 Timeouts - Intermittent Drops & Slow Downs

Highlighted
Regular Visitor

T3 / T4 Timeouts - Intermittent Drops & Slow Downs

I have a C7000-100NAS Cable Modem & Router.  WiFi is turned off, so only using it for modem and DHCP.  Probably doesn't matter, but I'm using a Orbi system for wireless (in AP mode).

 

Past several weeks, the internet connectivity has been sketchy.  Sometimes it is slow, sometimes it just drops.  I chatted with Comcast support today and they told me that there is something wrong with my modem.  Its been rebooted several times, so another reboot doesn't seem likely to solve the issue long term.  Looking at other threads though, seems like there could be other causes that need to be explored before I buy new equipment.  Appreciate anyone's additional throughts and analysis of the problem.  Log data below.  Thanks!

 

Time Priority Description
2020-4-16, 10:44:03 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:7f:b9:e1:3a:d0;CMTS-MAC=00:56:2b:77:ce:b2;CM-QOS=1.1;CM-VER=3.0;
2020-4-16, 09:39:26 Warning (5) MDD message timeout;CM-MAC=b0:7f:b9:e1:3a:d0;CMTS-MAC=00:56:2b:77:ce:b2;CM-QOS=1.1;CM-VER=3.0;
2020-4-16, 09:39:26 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:7f:b9:e1:3a:d0;CMTS-MAC=00:56:2b:77:ce:b2;CM-QOS=1.1;CM-VER=3.0;
2020-4-16, 09:39:18 Warning (5) MDD message timeout;CM-MAC=b0:7f:b9:e1:3a:d0;CMTS-MAC=00:56:2b:77:ce:b2;CM-QOS=1.1;CM-VER=3.0;
2020-4-16, 09:38:12 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:7f:b9:e1:3a:d0;CMTS-MAC=00:56:2b:77:ce:b2;CM-QOS=1.1;CM-VER=3.0;
2020-4-16, 09:37:36 Warning (5) MDD message timeout;CM-MAC=b0:7f:b9:e1:3a:d0;CMTS-MAC=00:56:2b:77:ce:b2;CM-QOS=1.1;CM-VER=3.0;
2020-4-16, 09:35:30 Warning (5) ToD request sent - No Response received;CM-MAC=b0:7f:b9:e1:3a:d0;CMTS-MAC=00:56:2b:77:ce:b2;CM-QOS=1.1;CM-VER=3.0;
2020-4-16, 09:35:21 Notice (6) Honoring MDD; IP provisioning mode = IPv6
2020-4-16, 09:34:32 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:7f:b9:e1:3a:d0;CMTS-MAC=00:56:2b:77:ce:b2;CM-QOS=1.1;CM-VER=3.0;
2020-4-16, 09:34:23 Warning (5) Dynamic Range Window violation
2020-4-16, 09:34:19 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=b0:7f:b9:e1:3a:d0;CMTS-MAC=00:56:2b:77:ce:b2;CM-QOS=1.1;CM-VER=3.0;
2020-4-16, 09:34:13 Warning (5) Dynamic Range Window violation
2020-4-16, 09:34:12 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:7f:b9:e1:3a:d0;CMTS-MAC=00:56:2b:77:ce:b2;CM-QOS=1.1;CM-VER=3.0;
2020-4-16, 09:34:03 Warning (5) Dynamic Range Window violation
2020-4-16, 09:34:00 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=b0:7f:b9:e1:3a:d0;CMTS-MAC=00:56:2b:77:ce:b2;CM-QOS=1.1;CM-VER=3.0;
2020-4-16, 09:33:43 Warning (5) Dynamic Range Window violation
2020-4-16, 09:33:40 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=b0:7f:b9:e1:3a:d0;CMTS-MAC=00:56:2b:77:ce:b2;CM-QOS=1.1;CM-VER=3.0;
2020-4-16, 09:23:24 Warning (5) Dynamic Range Window violation
2020-4-14, 14:41:00 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:7f:b9:e1:3a:d0;CMTS-MAC=00:56:2b:77:ce:b2;CM-QOS=1.1;CM-VER=3.0;
2020-4-14, 14:41:00 Warning (5) MDD message timeout;CM-MAC=b0:7f:b9:e1:3a:d0;CMTS-MAC=00:56:2b:77:ce:b2;CM-QOS=1.1;CM-VER=3.0;
2020-4-14, 14:41:00 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:7f:b9:e1:3a:d0;CMTS-MAC=00:56:2b:77:ce:b2;CM-QOS=1.1;CM-VER=3.0;
2020-4-14, 14:40:31 Warning (5) MDD message timeout;CM-MAC=b0:7f:b9:e1:3a:d0;CMTS-MAC=00:56:2b:77:ce:b2;CM-QOS=1.1;CM-VER=3.0;
2020-4-14, 09:16:03 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:7f:b9:e1:3a:d0;CMTS-MAC=00:56:2b:77:ce:b2;CM-QOS=1.1;CM-VER=3.0;
2020-4-14, 09:16:03 Warning (5) MDD message timeout;CM-MAC=b0:7f:b9:e1:3a:d0;CMTS-MAC=00:56:2b:77:ce:b2;CM-QOS=1.1;CM-VER=3.0;
2020-4-14, 09:09:35 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:7f:b9:e1:3a:d0;CMTS-MAC=00:56:2b:77:ce:b2;CM-QOS=1.1;CM-VER=3.0;
2020-4-14, 09:09:34 Warning (5) MDD message timeout;CM-MAC=b0:7f:b9:e1:3a:d0;CMTS-MAC=00:56:2b:77:ce:b2;CM-QOS=1.1;CM-VER=3.0;
2020-4-14, 09:09:34 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:7f:b9:e1:3a:d0;CMTS-MAC=00:56:2b:77:ce:b2;CM-QOS=1.1;CM-VER=3.0;
2020-4-13, 23:31:54 Warning (5) MDD message timeout;CM-MAC=b0:7f:b9:e1:3a:d0;CMTS-MAC=00:56:2b:77:ce:b2;CM-QOS=1.1;CM-VER=3.0;
2020-4-13, 23:31:54 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:7f:b9:e1:3a:d0;CMTS-MAC=00:56:2b:77:ce:b2;CM-QOS=1.1;CM-VER=3.0;
2020-4-13, 23:31:54 Warning (5) MDD message timeout;CM-MAC=b0:7f:b9:e1:3a:d0;CMTS-MAC=00:56:2b:77:ce:b2;CM-QOS=1.1;CM-VER=3.0;
2020-4-13, 23:31:54 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:7f:b9:e1:3a:d0;CMTS-MAC=00:56:2b:77:ce:b2;CM-QOS=1.1;CM-VER=3.0;
2020-4-13, 23:31:29 Warning (5) MDD message timeout;CM-MAC=b0:7f:b9:e1:3a:d0;CMTS-MAC=00:56:2b:77:ce:b2;CM-QOS=1.1;CM-VER=3.0;
2020-4-13, 23:03:44 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:7f:b9:e1:3a:d0;CMTS-MAC=00:56:2b:77:ce:b2;CM-QOS=1.1;CM-VER=3.0;
2020-4-13, 23:03:44 Warning (5) MDD message timeout;CM-MAC=b0:7f:b9:e1:3a:d0;CMTS-MAC=00:56:2b:77:ce:b2;CM-QOS=1.1;CM-VER=3.0;
2020-4-13, 23:03:44 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:7f:b9:e1:3a:d0;CMTS-MAC=00:56:2b:77:ce:b2;CM-QOS=1.1;CM-VER=3.0;
2020-4-13, 23:03:44 Warning (5) MDD message timeout;CM-MAC=b0:7f:b9:e1:3a:d0;CMTS-MAC=00:56:2b:77:ce:b2;CM-QOS=1.1;CM-VER=3.0;
2020-4-13, 23:01:54 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:7f:b9:e1:3a:d0;CMTS-MAC=00:56:2b:77:ce:b2;CM-QOS=1.1;CM-VER=3.0;
2020-4-13, 23:01:54 Warning (5) MDD message timeout;CM-MAC=b0:7f:b9:e1:3a:d0;CMTS-MAC=00:56:2b:77:ce:b2;CM-QOS=1.1;CM-VER=3.0;
2020-4-13, 23:01:54 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:7f:b9:e1:3a:d0;CMTS-MAC=00:56:2b:77:ce:b2;CM-QOS=1.1;CM-VER=3.0;
2020-4-13, 23:01:53 Warning (5) MDD message timeout;CM-MAC=b0:7f:b9:e1:3a:d0;CMTS-MAC=00:56:2b:77:ce:b2;CM-QOS=1.1;CM-VER=3.0;
Startup Procedure
Procedure Status Comment
Acquire Downstream Channel 645000000 Hz Locked
Connectivity State OK Operational
Boot State OK Operational
Security Enabled BPI+
IP Provisioning Mode Honor MDD honorMdd(4)
 
Downstream Bonded Channels
Channel Lock Status Modulation Channel ID Frequency Power SNR Correctables Uncorrectables
1 Locked QAM256 33 645000000 Hz 13.7 dBmV 37.2 dB 69287 0
2 Locked QAM256 17 549000000 Hz 13.5 dBmV 37.5 dB 17123 0
3 Locked QAM256 18 555000000 Hz 13.5 dBmV 37.5 dB 17860 0
4 Locked QAM256 19 561000000 Hz 13.6 dBmV 37.5 dB 19445 0
5 Locked QAM256 20 567000000 Hz 13.7 dBmV 37.5 dB 22587 0
6 Locked QAM256 21 573000000 Hz 13.6 dBmV 37.5 dB 24291 0
7 Locked QAM256 22 579000000 Hz 13.6 dBmV 37.5 dB 27561 0
8 Locked QAM256 23 585000000 Hz 13.6 dBmV 37.4 dB 32510 0
9 Locked QAM256 24 591000000 Hz 13.4 dBmV 37.2 dB 36517 0
10 Locked QAM256 25 597000000 Hz 13.4 dBmV 37.2 dB 39778 0
11 Locked QAM256 26 603000000 Hz 13.8 dBmV 37.5 dB 33995 0
12 Locked QAM256 27 609000000 Hz 13.6 dBmV 37.3 dB 41383 0
13 Locked QAM256 28 615000000 Hz 13.7 dBmV 37.2 dB 43013 0
14 Locked QAM256 29 621000000 Hz 13.8 dBmV 37.4 dB 49304 0
15 Locked QAM256 30 627000000 Hz 13.4 dBmV 37 dB 65868 0
16 Locked QAM256 31 633000000 Hz 13.5 dBmV 37.1 dB 68939 0
17 Locked QAM256 32 639000000 Hz -17.9 dBmV 39 dB 3 0
18 Locked QAM256 34 651000000 Hz -18 dBmV 39 dB 1 0
19 Locked QAM256 35 657000000 Hz -17.8 dBmV 39 dB 4 0
20 Locked QAM256 36 663000000 Hz -18.2 dBmV 38.6 dB 4 0
21 Locked QAM256 37 669000000 Hz -18.3 dBmV 38.6 dB 4 0
22 Locked QAM256 38 675000000 Hz -18.4 dBmV 38 dB 3 0
23 Locked QAM256 39 681000000 Hz -18.4 dBmV 38.2 dB 2 0
24 Locked QAM256 40 687000000 Hz -18.8 dBmV 37.9 dB 7 0
 
Upstream Bonded Channels
Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power
1 Locked ATDMA 1 5120 Ksym/sec 36100000 Hz 33.8 dBmV
2 Locked ATDMA 2 5120 Ksym/sec 29600000 Hz 33.8 dBmV
3 Locked ATDMA 3 5120 Ksym/sec 23000000 Hz 32.3 dBmV
4 Locked ATDMA 4 5120 Ksym/sec 16500000 Hz 33.8 dBmV
5 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV
6 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV
7 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV
8 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV
 
Extended Upstream Transmit Power
Enable Extended Upstream Transmit Power
 
Current System Time:Thu Apr 16 11:52:20 2020
System Up Time:3 days 19:35:26
Highlighted
Diamond Problem Solver

Re: T3 / T4 Timeouts - Intermittent Drops & Slow Downs

You have a 30 dB swing in your downstream levels +13 to -17/18, thats no good at all. Best case to prove inside vs outside vs modem, hook up your modem to the point of entry/ground block before any splitters and post those levels. If the big swing is still there, it’s going to generally be an outside issue. Your upstream is also a couple of dB short of spec but downstream is the bigger concern

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!
Highlighted
Expert

Re: T3 / T4 Timeouts - Intermittent Drops & Slow Downs

WOW ! FWIW, never seen that much of a reverse tilt before !!



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!
Highlighted
Regular Visitor

Re: T3 / T4 Timeouts - Intermittent Drops & Slow Downs

Thank you for the quick response.  I'll do a bit of troublehshooting as you suggest and see what I can rule out.  To be honest, I'm glad to at least know something looks strange and that I'm not completely crazy.  Now if I can just get my wife to stop blaming me for the bad internet.  🙂  

Highlighted
Regular Visitor

Re: T3 / T4 Timeouts - Intermittent Drops & Slow Downs

ok.  So I'm sitting on my driveway in the dark, with my cable model connected to the feed line coming of the box.  Unfortunatley, when I moved the modem it completely reset itself... perhaps another indication that the hardware is bad.  Below are my connection details, seems the problem still exists.  Seems it now thinks it is also 1970?!?!?!

 

Startup Procedure
Procedure Status Comment
Acquire Downstream Channel 645000000 Hz Locked
Connectivity State OK Operational
Boot State OK Operational
Security Enabled BPI+
IP Provisioning Mode Honor MDD honorMdd(4)
 
Downstream Bonded Channels
Channel Lock Status Modulation Channel ID Frequency Power SNR Correctables Uncorrectables
1 Locked QAM256 33 645000000 Hz 19.7 dBmV 37.5 dB 51 0
2 Locked QAM256 17 549000000 Hz 19.2 dBmV 37.7 dB 7 0
3 Locked QAM256 18 555000000 Hz 19.3 dBmV 37.7 dB 6 0
4 Locked QAM256 19 561000000 Hz 19.4 dBmV 37.7 dB 8 0
5 Locked QAM256 20 567000000 Hz 19.7 dBmV 37.8 dB 11 0
6 Locked QAM256 21 573000000 Hz 19.5 dBmV 37.8 dB 15 0
7 Locked QAM256 22 579000000 Hz 19.7 dBmV 37.8 dB 7 0
8 Locked QAM256 23 585000000 Hz 19.6 dBmV 37.7 dB 10 0
9 Locked QAM256 24 591000000 Hz 19.6 dBmV 37.6 dB 14 0
10 Locked QAM256 25 597000000 Hz 19.5 dBmV 37.5 dB 21 0
11 Locked QAM256 26 603000000 Hz 20.2 dBmV 38 dB 12 0
12 Locked QAM256 27 609000000 Hz 19.9 dBmV 37.8 dB 28 0
13 Locked QAM256 28 615000000 Hz 20.2 dBmV 37.7 dB 13 0
14 Locked QAM256 29 621000000 Hz 20.3 dBmV 37.9 dB 28 0
15 Locked QAM256 30 627000000 Hz 19.9 dBmV 37.5 dB 33 0
16 Locked QAM256 31 633000000 Hz 19.8 dBmV 37.5 dB 32 0
17 Locked QAM256 32 639000000 Hz -11.6 dBmV 39.4 dB 0 0
18 Locked QAM256 34 651000000 Hz -11.9 dBmV 39.1 dB 0 0
19 Locked QAM256 35 657000000 Hz -11.6 dBmV 39 dB 0 0
20 Locked QAM256 36 663000000 Hz -11.7 dBmV 39 dB 0 0
21 Locked QAM256 37 669000000 Hz -11.7 dBmV 38.9 dB 0 0
22 Locked QAM256 38 675000000 Hz -11.7 dBmV 38.2 dB 0 0
23 Locked QAM256 39 681000000 Hz -11.7 dBmV 38.6 dB 0 0
24 Locked QAM256 40 687000000 Hz -11.9 dBmV 38.3 dB 0 0
 
Upstream Bonded Channels
Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power
1 Locked ATDMA 3 5120 Ksym/sec 23000000 Hz 30.8 dBmV
2 Locked ATDMA 1 5120 Ksym/sec 36100000 Hz 30.8 dBmV
3 Locked ATDMA 2 5120 Ksym/sec 29600000 Hz 30.8 dBmV
4 Locked ATDMA 4 5120 Ksym/sec 16500000 Hz 30.8 dBmV
5 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV
6 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV
7 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV
8 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV
 
Extended Upstream Transmit Power
Enable Extended Upstream Transmit Power
 
Current System Time:Thu Apr 16 19:40:20 2020

System Up Time:00:31:22

 

1970-1-1, 00:01:02 Notice (6) Honoring MDD; IP provisioning mode = IPv6
1970-1-1, 00:00:47 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=b0:7f:b9:e1:3a:d0;CMTS-MAC=00:56:2b:77:ce:b2;CM-QOS=1.0;CM-VER=3.0;
1970-1-1, 00:00:41 Notice (6) WiFi Interface [wl1] set to Channel 153 (Side-Band Channel:N/A) - Reason:INIT
1970-1-1, 00:00:41 Notice (6) WiFi Interface [wl0] set to Channel 11 (Side-Band Channel:N/A) - Reason:INIT
1970-1-1, 00:00:39 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=b0:7f:b9:e1:3a:d0;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2020-4-16, 19:08:29 Critical (3) Resetting the cable modem due to docsDevResetNow
2020-4-16, 19:02:01 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:7f:b9:e1:3a:d0;CMTS-MAC=00:56:2b:77:ce:b2;CM-QOS=1.1;CM-VER=3.0;
1970-1-1, 00:00:44 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=b0:7f:b9:e1:3a:d0;CMTS-MAC=00:56:2b:77:ce:b2;CM-QOS=1.0;CM-VER=3.0;
1970-1-1, 00:00:37 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=b0:7f:b9:e1:3a:d0;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2020-4-16, 18:50:46 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:7f:b9:e1:3a:d0;CMTS-MAC=00:56:2b:77:ce:b2;CM-QOS=1.1;CM-VER=3.0;
1970-1-1, 00:00:45 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=b0:7f:b9:e1:3a:d0;CMTS-MAC=00:56:2b:77:ce:b2;CM-QOS=1.0;CM-VER=3.0;
2020-4-16, 18:40:19 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=b0:7f:b9:e1:3a:d0;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
1970-1-1, 00:01:39 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=b0:7f:b9:e1:3a:d0;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
1970-1-1, 00:01:38 Critical (3) No UCDs Received - Timeout;;CM-MAC=b0:7f:b9:e1:3a:d0;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
1970-1-1, 00:01:20 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=b0:7f:b9:e1:3a:d0;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
1970-1-1, 00:01:10 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=b0:7f:b9:e1:3a:d0;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
1970-1-1, 00:01:10 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=b0:7f:b9:e1:3a:d0;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
1970-1-1, 00:01:00 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=b0:7f:b9:e1:3a:d0;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
1970-1-1, 00:00:59 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=b0:7f:b9:e1:3a:d0;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
1970-1-1, 00:00:40 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=b0:7f:b9:e1:3a:d0;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
1970-1-1, 00:00:37 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=b0:7f:b9:e1:3a:d0;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Highlighted
Diamond Problem Solver

Re: T3 / T4 Timeouts - Intermittent Drops & Slow Downs

You probably should see about getting 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!
Highlighted
Expert

Re: T3 / T4 Timeouts - Intermittent Drops & Slow Downs

FWIW, the 1970 entries are what the modem defaults to went it cant talk to the time of day server because of connection problems.



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!
Highlighted
Regular Visitor

Re: T3 / T4 Timeouts - Intermittent Drops & Slow Downs

Wonderful... 

 

Response from Comcast "The Xfinity policy regarding Covid-19 related cases, we are currently unable to send the technician into your home. We are taking extra precautions during this period and I hope you understand. I can scheduled an appointment for 30 days from today. Also we can try to troubleshoot the issue and keep it under observation."

 

Keep trying to tell the guy that I don't want anyone to come into my house.  I want the outside line checked.  The hub is actually in my back yard.

 

Now he's blaming my use of VPN and wants to reset my modem.... sigh.  

 

I've got a modem ordered, but won't be here for several days.  Based on what y'all are saying, that likely not going to resolve the issue though.

Highlighted
Regular Visitor

Re: T3 / T4 Timeouts - Intermittent Drops & Slow Downs

Talked to someone and didn't make any further progress.  According to their system, I've not lost signal therefore they can't roll a technician.  Back to square one.  I'll see if a new modem does the trick.