U

Visitor

 • 

3 Messages

Fri, May 13, 2022 9:00 PM

MDD Message Timeout and Started Unicast Maintenance Ranging - No Response received - T3 time-out Errors

Hello, 

I am trying to figure out what is going on with my internet speed.  I talked with a customer service rep not even 24 hours ago and she was able to temporarily fix my issue by running system cleanup, reconnection, and system update; as of now though, my speed is back to barely 2mbps when it should be around 100.

I see no splitters or line damage and my modem is barely a year old.  This has been a long time issue for me.  I am using a Motorola mg7700 that should be able to easily handle anything I pay for.

   Log  
  
 Time   Priority   Description 
 Fri Apr 29 06:19:21 2022    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.0; 
 Fri Apr 29 09:12:05 2022    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.0; 
 Fri Apr 29 11:31:07 2022    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"]CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.0; 
 Fri Apr 29 11:48:06 2022    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.0; 
 Fri Apr 29 18:27:50 2022    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.0; 
 Sun May 01 21:47:46 2022    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.0; 
 Mon May 02 13:19:45 2022    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.0; 
 Sat May 07 10:22:22 2022    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.0; 
 Thu May 12 09:34:25 2022    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.0; 
 Thu May 12 21:33:53 2022    Critical (3)   Resetting the cable modem due to docsDevResetNow 
 Time Not Established   Notice (6)   Honoring MDD; IP provisioning mode = IPv6 
 Thu May 12 21:49:21 2022    Warning (5)   MDD message timeout;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.0; 
 Thu May 12 21:49:21 2022    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.0; 
 Fri May 13 00:30:09 2022    Warning (5)   MDD message timeout;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.0; 
 Fri May 13 00:30:09 2022    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.0; 
 Fri May 13 00:43:45 2022    Warning (5)   MDD message timeout;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.0; 
 Fri May 13 00:43:45 2022    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.0; 
 Fri May 13 01:23:41 2022    Warning (5)   MDD message timeout;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.0; 
 Fri May 13 01:23:41 2022    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.0; 
 Fri May 13 01:37:20 2022    Warning (5)   MDD message timeout;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.0; 
 Fri May 13 01:37:20 2022    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.0; 
 Fri May 13 01:39:00 2022    Warning (5)   MDD message timeout;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.0; 
 Fri May 13 01:39:00 2022    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.0; 
 Fri May 13 04:09:08 2022    Warning (5)   MDD message timeout;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.0; 
 Fri May 13 04:09:08 2022    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.0; 
 Fri May 13 04:24:26 2022    Warning (5)   MDD message timeout;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.0; 
 Fri May 13 04:24:26 2022    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.0; 
 Fri May 13 04:37:44 2022    Warning (5)   MDD message timeout;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.0; 
 Fri May 13 04:37:44 2022    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.0; 
 Fri May 13 04:58:42 2022    Warning (5)   MDD message timeout;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.0; 
 Fri May 13 04:58:42 2022    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.0; 
 Fri May 13 15:55:49 2022    Warning (5)   MDD message timeout;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.0; 

   Startup Sequence    
   Startup Step Status Comment

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

  
   Configuration File OK
  
   Security Enabled BPI+
  


   Connection Status    
   System Up Time 0 days 18h:25m:03s  
  
   Network Access Allowed  
  


   Downstream Bonded Channels  
  
   Channel Lock Status Modulation Channel ID Freq. (MHz) Pwr (dBmV) SNR (dB) Corrected Uncorrected
1 Locked QAM256 17 531.0 -23.4 29.6 224601 0
2 Locked QAM256 1 435.0 -19.2 33.9 109 54
3 Locked QAM256 2 441.0 -18.8 34.5 25 0
4 Locked QAM256 3 447.0 -26.5 27.4 9149529 1290221
5 Not Locked Unknown 0 453.0 0.0 0.0 0 0
6 Not Locked Unknown 0 459.0 0.0 0.0 5729418 2285879
7 Locked QAM256 6 465.0 -23.4 29.6 1121561 2
8 Locked QAM256 7 471.0 -23.2 29.0 1932796 7013
9 Locked QAM256 8 477.0 -23.3 29.5 616460 0
10 Locked QAM256 9 483.0 -19.1 33.7 0 0
11 Locked QAM256 10 489.0 -19.1 33.3 395 779
12 Locked QAM256 11 495.0 -18.6 33.8 0 0
13 Locked QAM256 12 501.0 -17.9 34.1 0 0
14 Locked QAM256 13 507.0 -21.3 30.4 69568530 179150
15 Locked QAM256 14 513.0 -25.1 27.5 167295102 17763043
16 Locked QAM256 15 519.0 -24.0 28.8 4894343 3
17 Locked QAM256 16 525.0 -21.6 31.8 218 0
18 Locked QAM256 18 537.0 -21.5 32.1 164 0
19 Locked QAM256 19 543.0 -22.7 31.0 709011 0
20 Locked QAM256 20 549.0 -23.8 29.7 206481 0
21 Not Locked Unknown 0 555.0 0.0 0.0 64749311 64749311
22 Locked QAM256 22 561.0 -26.5 26.3 772192612 435698247
23 Not Locked Unknown 0 567.0 0.0 0.0 0 0
24 Not Locked Unknown 0 573.0 0.0 0.0 0 0
Total             1098390666 521973702


   Upstream Bonded Channels  
  
   Channel Lock Status Channel Type Channel ID Symb. Rate (Ksym/sec) Freq. (MHz) Pwr (dBmV)
1 Locked ATDMA 2 5120 16.4 48.5
2 Locked ATDMA 3 5120 22.8 47.0
3 Locked ATDMA 4 5120 29.2 50.0
4 Locked ATDMA 5 5120 35.6 51.0
5 Locked ATDMA 6 2560 40.4 50.0
6 Not Locked Unknown 0 0 0 0.0
7 Not Locked Unknown 0 0 0 0.0
8 Not Locked Unknown 0 0 0 0.0
BruceW

Gold Problem Solver

 • 

23.7K Messages

Hace 13 d

... my speed is back to barely 2mbps when it should be around 100. ...

Your signals are terrible. Downstream power and SNR are too low, and upstream power is borderline/too high. Network connection problems like this are often due to poor coax connections or damaged coax cable, usually in or near your home.

If you want to troubleshoot this yourself, please see Internet Troubleshooting Tips. If you can't find the problem or you'd rather have Comcast take care of it, call them at the phone number on your bill or 1-800-Comcast, or use one of the options on https://www.xfinity.com/support/contact-us/ and insist they send a tech out to identify the cause and correct it.

If the tech finds bad coax, splitters, amplifiers, or connections in your home (even if Comcast originally supplied them) you'll probably have to pay for the visit ($70-$100) unless you have their Service Protection Plan ( https://www.xfinity.com/support/articles/service-protection-plan, closed to customers that don't already have it). If the trouble is due to a faulty Comcast rental device or anything outside your home you shouldn't be charged.

Please be aware that there are 2 kinds of responses in this Forum: Replies and Comments. When you Comment on a post by scrolling down to "Comment on this post here...", I am notified of your response. But if you select Reply, I am NOT notified and may not be aware of your response.

Visitor

 • 

3 Messages

@BruceW​ The comcast customer service rep did diagnostics and restarted my router last night and my speeds went from 2mbps to 100mbps without me reconnecting any of the lines, it lasted for a few hours then went back to 1-5mbps.  I have tried 3 different coaxial cables with a router restart and it hasn't made much of a difference.  I can get a tech here but is there anything else it could be?  

Visitor

 • 

3 Messages

Update: Power cycling can give me 30mbps, but I have yet to come close to the 100 it was giving me last night

(edited)

Official Employee

 • 

114 Messages

Hi! It looks like you've done excellent troubleshooting, and are doing everything you should be in this situation. If you'd like, I can help you schedule a technician to look into this...

I am an Official Xfinity Employee.
Official Employees are from multiple teams within Xfinity: CARE, Product, Leadership.
We ask that you post publicly so people with similar questions may benefit from the conversation.
Was your question answered? Please, mark a reply as the Accepted Answer.tick
BruceW

Gold Problem Solver

 • 

23.7K Messages

Hace 12 d

... The comcast customer service rep did diagnostics and restarted my router ...

Rebooting the MG7700 might result in temporary improvement, but if you want a more permanent fix then, as stated, you need to have a tech onsite to troubleshoot and correct the cause of the signal problems.

(edited)

forum icon

New to the Community?

Start Here