Community Forum

dropping connection

Highlighted
Regular Visitor

dropping connection

I am having the same issue as others. A tech came out but it is just as bad.

Channel Lock Status Modulation Channel ID Freq. (MHz) Pwr (dBmV) SNR (dB) Corrected Uncorrected
1 Locked QAM256 17 579.0 -1.0 40.2 0 0
2 Locked QAM256 18 585.0 -1.3 40.2 0 0
3 Locked QAM256 19 591.0 -1.3 40.1 0 0
4 Locked QAM256 20 597.0 -1.2 40.2 0 0
5 Locked QAM256 21 603.0 -1.8 40.1 0 0
6 Locked QAM256 22 609.0 -1.1 40.2 0 0
7 Locked QAM256 23 615.0 -2.0 40.0 0 0
8 Locked QAM256 24 621.0 -1.6 40.1 0 0
9 Locked QAM256 26 627.0 -2.5 40.0 0 0
10 Locked QAM256 27 633.0 -1.9 40.1 0 0
11 Locked QAM256 28 639.0 -2.9 39.9 0 0
12 Locked QAM256 29 645.0 -2.3 40.0 0 0
13 Locked QAM256 30 651.0 -3.2 39.9 0 0
14 Locked QAM256 31 657.0 -2.6 40.0 0 0
15 Locked QAM256 32 663.0 -3.5 39.8 0 0
16 Locked QAM256 33 669.0 -3.1 39.8 0 0
Total             0 0



   Upstream Bonded Channels
 

 

 
 

 


  
   Channel Lock Status Channel Type Channel ID Symb. Rate (Ksym/sec) Freq. (MHz) Pwr (dBmV)
1 Locked ATDMA 1 5120 35.8 57.0
2 Not Locked Unknown 0 0 0 0.0
3 Not Locked Unknown 0 0 0 0.0
4 Not Locked Unknown 0 0 0 0.0
Event Log
   Log
 

 

 
 

 


  
 Time   Priority   Description 
 Sat Jun 27 16:43:22 2020    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:62:33:f2;CMTS-MAC=00:01:5c:71:b8:60;CM-QOS=1.1;CM-VER=3.0; 
 Sat Jun 27 16:47:42 2020    Critical (3)   Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:40:36:62:33:f2;CMTS-MAC=00:01:5c:71:b8:60;CM-QOS=1.1;CM-VER=3.0; 
 Sat Jun 27 16:48:07 2020    Critical (3)   No Ranging Response received - T3 time-out;CM-MAC=00:40:36:62:33:f2;CMTS-MAC=00:01:5c:71:b8:60;CM-QOS=1.0;CM-VER=3.0; 
 Sat Jun 27 17:43:51 2020    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:62:33:f2;CMTS-MAC=00:01:5c:71:b8:60;CM-QOS=1.1;CM-VER=3.0; 
 Sat Jun 27 17:43:51 2020    Critical (3)   Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=00:40:36:62:33:f2;CMTS-MAC=00:01:5c:71:b8:60;CM-QOS=1.1;CM-VER=3.0; 
 Sat Jun 27 17:43:51 2020    Critical (3)   16 consecutive T3 timeouts while trying to range on upstream channel 0;CM-MAC=00:40:36:62:33:f2;CMTS-MAC=00:01:5c:71:b8:60;CM-QOS=1.1;CM-VER=3.0; 
 Sat Jun 27 18:09:42 2020    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:62:33:f2;CMTS-MAC=00:01:5c:71:b8:60;CM-QOS=1.1;CM-VER=3.0; 
 Sat Jun 27 18:09:42 2020    Critical (3)   Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=00:40:36:62:33:f2;CMTS-MAC=00:01:5c:71:b8:60;CM-QOS=1.1;CM-VER=3.0; 
 Sat Jun 27 18:09:42 2020    Critical (3)   16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=00:40:36:62:33:f2;CMTS-MAC=00:01:5c:71:b8:60;CM-QOS=1.1;CM-VER=3.0; 
 Sat Jun 27 18:14:02 2020    Critical (3)   Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:40:36:62:33:f2;CMTS-MAC=00:01:5c:71:b8:60;CM-QOS=1.1;CM-VER=3.0; 
 Sat Jun 27 18:14:29 2020    Critical (3)   No Ranging Response received - T3 time-out;CM-MAC=00:40:36:62:33:f2;CMTS-MAC=00:01:5c:71:b8:60;CM-QOS=1.0;CM-VER=3.0; 
 Sat Jun 27 18:31:09 2020    Critical (3)   Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:40:36:62:33:f2;CMTS-MAC=00:01:5c:71:b8:60;CM-QOS=1.1;CM-VER=3.0; 
 Sat Jun 27 18:42:45 2020    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:62:33:f2;CMTS-MAC=00:01:5c:71:b8:60;CM-QOS=1.1;CM-VER=3.0; 
 Sat Jun 27 18:47:05 2020    Critical (3)   Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:40:36:62:33:f2;CMTS-MAC=00:01:5c:71:b8:60;CM-QOS=1.1;CM-VER=3.0; 
 Sat Jun 27 18:57:53 2020    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:62:33:f2;CMTS-MAC=00:01:5c:71:b8:60;CM-QOS=1.1;CM-VER=3.0; 
 Sat Jun 27 19:02:13 2020    Critical (3)   Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:40:36:62:33:f2;CMTS-MAC=00:01:5c:71:b8:60;CM-QOS=1.1;CM-VER=3.0; 
 Sat Jun 27 19:17:23 2020    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:62:33:f2;CMTS-MAC=00:01:5c:71:b8:60;CM-QOS=1.1;CM-VER=3.0; 
 Sat Jun 27 19:21:43 2020    Critical (3)   Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:40:36:62:33:f2;CMTS-MAC=00:01:5c:71:b8:60;CM-QOS=1.1;CM-VER=3.0; 
 Sat Jun 27 19:21:53 2020    Critical (3)   No Ranging Response received - T3 time-out;CM-MAC=00:40:36:62:33:f2;CMTS-MAC=00:01:5c:71:b8:60;CM-QOS=1.0;CM-VER=3.0; 
 Sat Jun 27 19:22:57 2020    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:62:33:f2;CMTS-MAC=00:01:5c:71:b8:60;CM-QOS=1.1;CM-VER=3.0; 
 Sat Jun 27 19:23:29 2020    Critical (3)   Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:40:36:62:33:f2;CMTS-MAC=00:01:5c:71:b8:60;CM-QOS=1.1;CM-VER=3.0; 
 Sat Jun 27 19:25:54 2020    Critical (3)   No Ranging Response received - T3 time-out;CM-MAC=00:40:36:62:33:f2;CMTS-MAC=00:01:5c:71:b8:60;CM-QOS=1.0;CM-VER=3.0; 
 Sat Jun 27 19:27:24 2020    Critical (3)   Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:40:36:62:33:f2;CMTS-MAC=00:01:5c:71:b8:60;CM-QOS=1.0;CM-VER=3.0; 
 Sat Jun 27 19:27:28 2020    Critical (3)   No Ranging Response received - T3 time-out;CM-MAC=00:40:36:62:33:f2;CMTS-MAC=00:01:5c:71:b8:60;CM-QOS=1.0;CM-VER=3.0; 
 Sun Jun 28 13:42:22 2020    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:62:33:f2;CMTS-MAC=00:01:5c:71:b8:60;CM-QOS=1.1;CM-VER=3.0; 
 Sun Jun 28 13:46:42 2020    Critical (3)   Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:40:36:62:33:f2;CMTS-MAC=00:01:5c:71:b8:60;CM-QOS=1.1;CM-VER=3.0; 
 Sun Jun 28 13:46:56 2020    Critical (3)   No Ranging Response received - T3 time-out;CM-MAC=00:40:36:62:33:f2;CMTS-MAC=00:01:5c:71:b8:60;CM-QOS=1.0;CM-VER=3.0; 
 Sun Jun 28 16:15:19 2020    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:62:33:f2;CMTS-MAC=00:01:5c:71:b8:60;CM-QOS=1.1;CM-VER=3.0; 
 Sun Jun 28 16:19:39 2020    Critical (3)   Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:40:36:62:33:f2;CMTS-MAC=00:01:5c:71:b8:60;CM-QOS=1.1;CM-VER=3.0; 
 Sun Jun 28 16:19:53 2020    Critical (3)   No Ranging Response received - T3 time-out;CM-MAC=00:40:36:62:33:f2;CMTS-MAC=00:01:5c:71:b8:60;CM-QOS=1.0;CM-VER=3.0; 
 Sun Jun 28 17:09:27 2020    Critical (3)   Resetting the cable modem due to docsDevResetNow 
 Time Not Established   Notice (6)   Honoring MDD; IP provisioning mode = IPv6 


Any help would be much appreciated   I am burning up my data plan on my phone due to this

Highlighted
Diamond Problem Solver

Re: dropping connection

You should have 2-4 more upstream channels but since it’s so high they’re probably not registering. You need to drop it at least 7 dB. Any splitters you can get rid of?

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

Re: dropping connection

no spliters that I know of
When the tech came out he switched the incoming from my living room to my bedroom  I only use my router and wireless. TV, phone, laptop ect all go through the wireless  I live alone so there is not any conflict with anyone else in the house

Highlighted
Regular Visitor

Re: dropping connection

I did a reset on my router do you think this was the issue?


   Upstream Bonded Channels
 

 

 
 

 


  
   Channel Lock Status Channel Type Channel ID Symb. Rate (Ksym/sec) Freq. (MHz) Pwr (dBmV)
1 Locked ATDMA 1 5120 35.8 43.0
2 Locked ATDMA 2 5120 29.4 42.8
3 Locked ATDMA 3 5120 23.0 43.3
4 Locked ATDMA 4 5120 16.6 42.8
Highlighted
Diamond Problem Solver

Re: dropping connection

You mean reset your modem and yes it looks better

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

Re: dropping connection

Yes I did reset my modem and it was better but that was short lived

Connection
   eRouter
 

 

   
   eRouter Provisioning Mode        
 

 







  


   Startup Sequence
 

 

   
   Startup Step Status Comment
 

 



  
   Acquire Downstream Channel 405000000 Hz Locked
 

 


  
   Upstream Connection OK Operational
 

 


  
   Boot State OK Operational
 

 



  
   Configuration File OK  
 

 


  
   Security Enabled BPI+
 

 


  


   Connection Status
 

 

   
   System Up Time 1 days 01h:31m:42s  
 

 


  
   Network Access Allowed  
 

 


  


   Downstream Bonded Channels
 

 

 
 

 


  
   Channel Lock Status Modulation Channel ID Freq. (MHz) Pwr (dBmV) SNR (dB) Corrected Uncorrected
1 Locked QAM256 38 405.0 -4.9 40.0 454 693
2 Locked QAM256 39 411.0 -5.3 39.9 496 518
3 Locked QAM256 40 417.0 -5.6 39.8 485 519
4 Locked QAM256 41 423.0 -5.2 39.9 516 501
5 Locked QAM256 42 429.0 -5.3 39.9 529 535
6 Locked QAM256 43 435.0 -5.6 39.9 539 567
7 Locked QAM256 44 441.0 -5.1 40.0 513 454
8 Locked QAM256 45 453.0 -5.7 39.9 467 525
9 Locked QAM256 25 459.0 -4.6 40.1 533 563
10 Locked QAM256 34 465.0 -5.1 39.9 505 890
11 Locked QAM256 35 471.0 -4.6 40.0 502 415
12 Locked QAM256 36 477.0 -4.4 40.1 484 651
13 Locked QAM256 1 483.0 -4.5 40.1 383 475
14 Locked QAM256 2 489.0 -4.0 40.2 452 411
15 Locked QAM256 3 495.0 -4.1 40.1 357 486
16 Locked QAM256 4 501.0 -3.9 40.1 387 636
Total             7602 8839


   Upstream Bonded Channels
 

 

 
 

 


  
   Channel Lock Status Channel Type Channel ID Symb. Rate (Ksym/sec) Freq. (MHz) Pwr (dBmV)
1 Locked ATDMA 1 5120 35.8 57.0
2 Not Locked Unknown 0 0 0 0.0
3 Not Locked Unknown 0 0 0 0.0
4 Not Locked Unknown 0 0 0 0.0


   Downstream Frequency Setting
 

 

   
   Downstream Frequency Select   
 

 


  


   Network WAN Connection
 

 

   
   IPv4 Address 73.255.220.106  
 

 




  
   Time Since Lease 😧 02 H: 19 M: 09 S: 03  
 

 



  
   Lease Expiration Time Thu Jul 02 13:47:12 2020  
 

 



  
   IPv6 Address fe80::240:36ff:fe62:33f3/64  
 

 



  
  2001:558:600b:3:d512:4c9d:f062:f55c/128    
   MAC Address 00:40:36:62:33:f3  
 

 


  
   IPv6 DNS Servers 2001:558:feed::1  
 

 


  
  2001:558:feed::2     
   WAN Connection Type DHCP  
 

 


  
       
    


   IPv4 DNS Servers
 

 

  
 

 


  
   Obtain Automatically from MSO  
 

 



  
   Primary DNS ...  
 

 


  
   Secondary DNS ...  
 

 


  
Event Log
   Log
 

 

 
 

 


  
 Time   Priority   Description 
 Mon Jun 29 16:02:14 2020    Critical (3)   No Ranging Response received - T3 time-out;CM-MAC=00:40:36:62:33:f2;CMTS-MAC=00:01:5c:71:b8:60;CM-QOS=1.0;CM-VER=3.0; 
 Mon Jun 29 16:02:38 2020    Notice (6)   Honoring MDD; IP provisioning mode = IPv6 
 Mon Jun 29 16:33:16 2020    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:62:33:f2;CMTS-MAC=00:01:5c:71:b8:60;CM-QOS=1.1;CM-VER=3.0; 
 Mon Jun 29 16:37:36 2020    Critical (3)   Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:40:36:62:33:f2;CMTS-MAC=00:01:5c:71:b8:60;CM-QOS=1.1;CM-VER=3.0; 
 Mon Jun 29 16:38:04 2020    Critical (3)   No Ranging Response received - T3 time-out;CM-MAC=00:40:36:62:33:f2;CMTS-MAC=00:01:5c:71:b8:60;CM-QOS=1.0;CM-VER=3.0; 
 Mon Jun 29 16:38:09 2020    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:62:33:f2;CMTS-MAC=00:01:5c:71:b8:60;CM-QOS=1.0;CM-VER=3.0; 
 Mon Jun 29 16:38:16 2020    Notice (6)   Honoring MDD; IP provisioning mode = IPv6 
 Mon Jun 29 16:47:11 2020    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:62:33:f2;CMTS-MAC=00:01:5c:71:b8:60;CM-QOS=1.1;CM-VER=3.0; 
 Mon Jun 29 16:51:31 2020    Critical (3)   Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:40:36:62:33:f2;CMTS-MAC=00:01:5c:71:b8:60;CM-QOS=1.1;CM-VER=3.0; 
 Mon Jun 29 16:51:51 2020    Critical (3)   No Ranging Response received - T3 time-out;CM-MAC=00:40:36:62:33:f2;CMTS-MAC=00:01:5c:71:b8:60;CM-QOS=1.0;CM-VER=3.0; 
 Mon Jun 29 16:52:06 2020    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:62:33:f2;CMTS-MAC=00:01:5c:71:b8:60;CM-QOS=1.0;CM-VER=3.0; 
 Mon Jun 29 16:52:13 2020    Notice (6)   Honoring MDD; IP provisioning mode = IPv6 
 Mon Jun 29 17:04:57 2020    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:62:33:f2;CMTS-MAC=00:01:5c:71:b8:60;CM-QOS=1.1;CM-VER=3.0; 
 Mon Jun 29 17:09:17 2020    Critical (3)   Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:40:36:62:33:f2;CMTS-MAC=00:01:5c:71:b8:60;CM-QOS=1.1;CM-VER=3.0; 
 Mon Jun 29 17:09:49 2020    Critical (3)   No Ranging Response received - T3 time-out;CM-MAC=00:40:36:62:33:f2;CMTS-MAC=00:01:5c:71:b8:60;CM-QOS=1.0;CM-VER=3.0; 
 Mon Jun 29 17:10:00 2020    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:62:33:f2;CMTS-MAC=00:01:5c:71:b8:60;CM-QOS=1.0;CM-VER=3.0; 
 Mon Jun 29 17:10:07 2020    Notice (6)   Honoring MDD; IP provisioning mode = IPv6 
 Mon Jun 29 17:49:28 2020    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:62:33:f2;CMTS-MAC=00:01:5c:71:b8:60;CM-QOS=1.1;CM-VER=3.0; 
 Mon Jun 29 17:49:28 2020    Critical (3)   Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=00:40:36:62:33:f2;CMTS-MAC=00:01:5c:71:b8:60;CM-QOS=1.1;CM-VER=3.0; 
 Mon Jun 29 17:49:28 2020    Critical (3)   16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=00:40:36:62:33:f2;CMTS-MAC=00:01:5c:71:b8:60;CM-QOS=1.1;CM-VER=3.0; 
 Mon Jun 29 17:49:29 2020    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:62:33:f2;CMTS-MAC=00:01:5c:71:b8:60;CM-QOS=1.1;CM-VER=3.0; 
 Mon Jun 29 17:53:49 2020    Critical (3)   Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:40:36:62:33:f2;CMTS-MAC=00:01:5c:71:b8:60;CM-QOS=1.1;CM-VER=3.0; 
 Mon Jun 29 17:54:16 2020    Critical (3)   No Ranging Response received - T3 time-out;CM-MAC=00:40:36:62:33:f2;CMTS-MAC=00:01:5c:71:b8:60;CM-QOS=1.0;CM-VER=3.0; 
 Mon Jun 29 17:54:25 2020    Notice (6)   Honoring MDD; IP provisioning mode = IPv6 
 Mon Jun 29 18:15:45 2020    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:62:33:f2;CMTS-MAC=00:01:5c:71:b8:60;CM-QOS=1.1;CM-VER=3.0; 
 Mon Jun 29 18:20:05 2020    Critical (3)   Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:40:36:62:33:f2;CMTS-MAC=00:01:5c:71:b8:60;CM-QOS=1.1;CM-VER=3.0; 
 Mon Jun 29 18:20:22 2020    Notice (6)   Honoring MDD; IP provisioning mode = IPv6 
 Mon Jun 29 18:33:07 2020    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:62:33:f2;CMTS-MAC=00:01:5c:71:b8:60;CM-QOS=1.1;CM-VER=3.0; 
 Mon Jun 29 18:37:27 2020    Critical (3)   Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:40:36:62:33:f2;CMTS-MAC=00:01:5c:71:b8:60;CM-QOS=1.1;CM-VER=3.0; 
 Mon Jun 29 18:37:39 2020    Critical (3)   No Ranging Response received - T3 time-out;CM-MAC=00:40:36:62:33:f2;CMTS-MAC=00:01:5c:71:b8:60;CM-QOS=1.0;CM-VER=3.0; 
 Mon Jun 29 18:37:47 2020    Notice (6)   Honoring MDD; IP provisioning mode = IPv6 
 Tue Jun 30 06:27:36 2020    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:62:33:f2;CMTS-MAC=00:01:5c:71:b8:60;CM-QOS=1.1;CM-VER=3.0; 
     
     
       
     
Highlighted
Diamond Problem Solver

Re: dropping connection

As part of troubleshooting I’d start with swapping the modem.

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: dropping connection

It's not the device.  Something is going on with the connection quality / line. Get a tech visit.



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!