Daily I am having connection drops. I have a Motoroloa MB 7420 Modem, connected to a Netgear Nighthawk R6700. The issues started in the spring, or that is when i noticed them. Many troubleshooting sessions and 2 visits by Comcast techs resulted in 1) a new cable installed between my house and the road, and 2) ditching the Comcast modem and installing my own. For several months, the problems seems to subside...then about a month ago, I started having them again. I have had 3 calls with support with no solution. I was told that they are not dispatching techs due to COVID UNLESS your connection is completely down. Below is an excerpt from the logs. Each time there is an issue, this sequence of log entries is repeated. Any assistance will be much appreciated.
Nathan
Sun Aug 23 14:26:11 2020 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:63:c7:30;CMTS-MAC=58:97:bd:98:71:5b;CM-QOS=1.1;CM-VER=3.0;
Sun Aug 23 14:28:21 2020 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:40:36:63:c7:30;CMTS-MAC=58:97:bd:98:71:5b;CM-QOS=1.1;CM-VER=3.0;
Sun Aug 23 14:28:45 2020 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=00:40:36:63:c7:30;CMTS-MAC=58:97:bd:98:71:5b;CM-QOS=1.0;CM-VER=3.0;
Sun Aug 23 14:29:05 2020 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:63:c7:30;CMTS-MAC=58:97:bd:98:71:5b;CM-QOS=1.0;CM-VER=3.0;
Sun Aug 23 14:29:38 2020 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:40:36:63:c7:30;CMTS-MAC=58:97:bd:98:71:5b;CM-QOS=1.0;CM-VER=3.0;
Sun Aug 23 14:29:46 2020 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=00:40:36:63:c7:30;CMTS-MAC=58:97:bd:98:71:5b;CM-QOS=1.0;CM-VER=3.0;
Sun Aug 23 14:29:53 2020 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:63:c7:30;CMTS-MAC=58:97:bd:98:71:5b;CM-QOS=1.0;CM-VER=3.0;
Sun Aug 23 14:29:57 2020 Notice (6) Honoring MDD; IP provisioning mode = IPv6
Sun Aug 23 14:31:00 2020 Warning (5) MDD message timeout;CM-MAC=00:40:36:63:c7:30;CMTS-MAC=58:97:bd:98:71:5b;CM-QOS=1.1;CM-VER=3.0;
Please also post the *Downstream Power Level*, the *Upstream Power Level*, and the *SNR* (Signal to Noise Ratio) numbers.
| |||||||||||||||||||||||||||||||||||
|
The signal stats are good. Is this with a WiFi connection ? If so, for a test, does a computer / device hardwired directly to the MB 7420 Modem with an ethernet cable have the same problem ?
With this test, we are trying to isolate this from being either a WiFi-/ router only problem or a problem with the general connection to the Comcast system which would of course affect both. It's a good step of troubleshooting before we proceed any further.
I have tested that scenario. I have connected a laptop computer and internet TV with direct wire during the connection drops and there is no connectivity with them.
Did you power cycle the modem after connecting each of them ?
No. Usually, connectivity returns within 1-4 minutes. Power cycle also re-engages connectivity. That is great, however, audio/video calls over internet get dropped which causes problems for myself and my child students.
Just so you know, you MUST power cycle/reboot the modem each and every time that you change the device that is being directly connected to it in order for that device to be able to get an internet connection.
That said. Even though the signal stats looked o/k at that snapshot in time, the error log entries confirm that something is going on. Perhaps there is noise ingress into the line(s) somewhere.
There are other signal stat figures that can't be read by the modem. 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.
I'm going to escalate your issue to the Comcast corporate employees that are available to these boards. They can check the CMTS (Cable Modem Termination System) for any real time degradation and / or error reports, see your node / cable plant and modem health, and see whether or not everything is in the green zone. They can also see a history plot for the modem and poll for those upstream receive signal stats.
You should get a reply here in your topic. Good luck !
Hello noxvillenate, thanks for creating a post. Let's look into your signal levels to see what could be causing your constant disconnects, I have a few tools here that will help me pinpoint the issue so that we can get this taken care of. To continue with troubleshooting could you please send me a private message with your full name by clicking on my name (ComcastAmir) and then click "Send a message"?
I have tried multiple times to reach out to ComcastAmir with no response. If there are others who may assist, I would be grateful.
I'm going to re-escalate this.
FYI...out of the blue yesterday, I received a text that Comcast is now scheduling in home tech support visits again. I have a tech scheduled to come out tomorrow to troubleshoot. I will update this ticket with the results. Thanks! Nathan
Good luck with it ! Please post back with how things turn out.
Hi Nathan. We apologize for our delay in getting back with you. I was able to located and review the diagnostics of your modem and I do see an issue with your T3 Timeouts being high, and your Upstream Receive signal intermittently fluctuating. At this time that pending technician visit is the best thing to get your service performance back to where it needs to be. If you would like to discuss the details of your account, or the pending tech visit, please send me a private message. You can click my name (ComcastJoeTru) to view my profile and send me a private message. Click "Send a private message" and private message me.
Thanks for hanging in there with us.
Please escalate as the attempts to repair last Wednesday have not resulted in a solution. We have had MANY drops with the same errors since the Comcast tech was here
Thank you,
Nathan
NOTE: I have reached out to you @ComcastJoeTru via private message.
@ComcastJoeTru @ComcastAmir @EG
It has almost been a week since I reported the tech visit DID NOT repair my issue. Also 9/4 was the last I have heard from anyone on this post. I was told that escalation to a higher department @ Comcast was the next step. Also the tech who worked at my home mentioned the best way to get the support I need is to go throught this support forum.
Will someone please assist with escalation?
Thanks in advance!
Nathan (@knoxvillenate)
I'll try to re-escalate this once again.... Good luck !
Hello @knoxvillenate, I can't apologize enough for the delays in us getting back to you and the continued connection issues you have been experiencing. We absolutely want to get to the bottom of this and I would love to assist you! I have responded to your private message and look forward to working on this with you!
Unfortunately I spoke too soon. Since Sunday things are bad again. Many drops per day. PLEASE ESCALATE AND SEND OUT TECH.
Time | Priority | Description |
Mon Sep 21 03:05:58 2020 | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=00:40:36:63:c7:30;CMTS-MAC=58:97:bd:98:71:5b;CM-QOS=1.0;CM-VER=3.0; |
Mon Sep 21 04:26:41 2020 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:63:c7:30;CMTS-MAC=58:97:bd:98:71:5b;CM-QOS=1.1;CM-VER=3.0; |
Mon Sep 21 04:28:51 2020 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:40:36:63:c7:30;CMTS-MAC=58:97:bd:98:71:5b;CM-QOS=1.1;CM-VER=3.0; |
Mon Sep 21 04:29:01 2020 | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=00:40:36:63:c7:30;CMTS-MAC=58:97:bd:98:71:5b;CM-QOS=1.0;CM-VER=3.0; |
Mon Sep 21 11:16:17 2020 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:63:c7:30;CMTS-MAC=58:97:bd:98:71:5b;CM-QOS=1.1;CM-VER=3.0; |
Mon Sep 21 11:18:27 2020 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:40:36:63:c7:30;CMTS-MAC=58:97:bd:98:71:5b;CM-QOS=1.1;CM-VER=3.0; |
Mon Sep 21 11:18:45 2020 | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=00:40:36:63:c7:30;CMTS-MAC=58:97:bd:98:71:5b;CM-QOS=1.0;CM-VER=3.0; |
Tue Sep 22 03:54:56 2020 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:63:c7:30;CMTS-MAC=58:97:bd:98:71:5b;CM-QOS=1.1;CM-VER=3.0; |
Tue Sep 22 03:57:06 2020 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:40:36:63:c7:30;CMTS-MAC=58:97:bd:98:71:5b;CM-QOS=1.1;CM-VER=3.0; |
Tue Sep 22 03:57:18 2020 | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=00:40:36:63:c7:30;CMTS-MAC=58:97:bd:98:71:5b;CM-QOS=1.0;CM-VER=3.0; |
Tue Sep 22 04:44:15 2020 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:63:c7:30;CMTS-MAC=58:97:bd:98:71:5b;CM-QOS=1.1;CM-VER=3.0; |
Tue Sep 22 04:46:26 2020 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:40:36:63:c7:30;CMTS-MAC=58:97:bd:98:71:5b;CM-QOS=1.1;CM-VER=3.0; |
Tue Sep 22 04:46:36 2020 | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=00:40:36:63:c7:30;CMTS-MAC=58:97:bd:98:71:5b;CM-QOS=1.0;CM-VER=3.0; |
Tue Sep 22 05:12:41 2020 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:63:c7:30;CMTS-MAC=58:97:bd:98:71:5b;CM-QOS=1.1;CM-VER=3.0; |
Tue Sep 22 05:14:51 2020 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:40:36:63:c7:30;CMTS-MAC=58:97:bd:98:71:5b;CM-QOS=1.1;CM-VER=3.0; |
Tue Sep 22 05:15:06 2020 | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=00:40:36:63:c7:30;CMTS-MAC=58:97:bd:98:71:5b;CM-QOS=1.0;CM-VER=3.0; |
Tue Sep 22 05:29:54 2020 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:63:c7:30;CMTS-MAC=58:97:bd:98:71:5b;CM-QOS=1.1;CM-VER=3.0; |
Tue Sep 22 05:32:04 2020 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:40:36:63:c7:30;CMTS-MAC=58:97:bd:98:71:5b;CM-QOS=1.1;CM-VER=3.0; |
Tue Sep 22 05:32:22 2020 | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=00:40:36:63:c7:30;CMTS-MAC=58:97:bd:98:71:5b;CM-QOS=1.0;CM-VER=3.0; |
Tue Sep 22 05:42:52 2020 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:63:c7:30;CMTS-MAC=58:97:bd:98:71:5b;CM-QOS=1.1;CM-VER=3.0; |
Tue Sep 22 05:45:02 2020 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:40:36:63:c7:30;CMTS-MAC=58:97:bd:98:71:5b;CM-QOS=1.1;CM-VER=3.0; |
Time Not Established | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=00:40:36:63:c7:30;CMTS-MAC=58:97:bd:98:71:5b;CM-QOS=1.0;CM-VER=3.0; |
Tue Sep 22 10:35:24 2020 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:63:c7:30;CMTS-MAC=58:97:bd:98:71:5b;CM-QOS=1.1;CM-VER=3.0; |
Tue Sep 22 10:35:24 2020 | Critical (3) | Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=00:40:36:63:c7:30;CMTS-MAC=58:97:bd:98:71:5b;CM-QOS=1.1;CM-VER=3.0; |
Tue Sep 22 10:35:25 2020 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:63:c7:30;CMTS-MAC=58:97:bd:98:71:5b;CM-QOS=1.1;CM-VER=3.0; |
Tue Sep 22 10:35:25 2020 | Critical (3) | Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=00:40:36:63:c7:30;CMTS-MAC=58:97:bd:98:71:5b;CM-QOS=1.1;CM-VER=3.0; |
Tue Sep 22 10:35:28 2020 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:63:c7:30;CMTS-MAC=58:97:bd:98:71:5b;CM-QOS=1.1;CM-VER=3.0; |
Tue Sep 22 10:35:28 2020 | Critical (3) | Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=00:40:36:63:c7:30;CMTS-MAC=58:97:bd:98:71:5b;CM-QOS=1.1;CM-VER=3.0; |
Tue Sep 22 10:35:33 2020 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:63:c7:30;CMTS-MAC=58:97:bd:98:71:5b;CM-QOS=1.1;CM-VER=3.0; |
Tue Sep 22 10:35:33 2020 | Critical (3) | Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=00:40:36:63:c7:30;CMTS-MAC=58:97:bd:98:71:5b;CM-QOS=1.1;CM-VER=3.0; |
Tue Sep 22 10:35:33 2020 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:63:c7:30;CMTS-MAC=58:97:bd:98:71:5b;CM-QOS=1.1;CM-VER=3.0; |
Time Not Established | Notice (6) | Honoring MDD; IP provisioning mode = IPv6 |
I am having similiar issues. My connection drops multiple times a day. Seems to be more of an issue while using a PC versus using Apple products. I would love some help to figure this out. It's been going on for over a year.
I suggest you start your own topic and work with the Comcast techs that monitor these message boards. Working with techs on the message boards is MUCH BETTER than working with the techs at the call center. I have been working with them over time and we are still troubleshooting. Early on, it was the cable between the road an my house that needed to be replaced. Things were better for months, now I believe the problem is a new one. It takes a tech to troubleshoot onsite, however, there are some things that they can analyze remotely. My problems are sporadic and this type of problem can have many culprits, so we continue to work on it.