Visitor
•
3 Messages
Network connection randomly disconnected; critical messages shown up in the Event Log
I have just recently experienced this problem after more than 5 years of service.
My neighborhood has recently experienced an unexpected outage on 3/8/2023, lasted about 8 hours; since then my network keeps randomly disconnected and I have to remove the cable from the modem, and recycle the power to have the network connection back.
At first I thought I could have a modem that gone bad; so I bought a new Motorola MB8600 modem from Best Buy store and activated it; it makes the issue a little bit better because the modem now can recover by itself the network connection after the interruption in a few minutes, without removing the cable from the modem and recycling power intervention; but this problem is still very annoying for me because working from home and if in middle of Teams/Zoom calls.
Following is the few log messages shown up in the Event Log; in addition, there are a lot of Corrected/Uncorrected counts in the Downstream bonded channels. Only one upstream bonded channel; MAC addresses are masked.
18:08:48
Thu Apr 6 2023 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;
18:20:20
Thu Apr 6 2023 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;
18:20:21
Thu Apr 6 2023 Warning (5) TCS Partial Service;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;
18:31:51
Thu Apr 6 2023 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;
18:31:53
Thu Apr 6 2023 Warning (5) TCS Partial Service;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;
18:43:24
Thu Apr 6 2023 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;
18:43:24
Thu Apr 6 2023 Warning (5) TCS Partial Service;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;
18:54:53
Thu Apr 6 2023 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;
18:54:55
Thu Apr 6 2023 Warning (5) TCS Partial Service;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;
19:06:13
Thu Apr 6 2023 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;
19:06:27
Thu Apr 6 2023 Warning (5) TCS Partial Service;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;
19:17:57
Thu Apr 6 2023 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;
19:17:58
Thu Apr 6 2023 Warning (5) TCS Partial Service;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;
19:29:21
Thu Apr 6 2023 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;
19:29:30
Thu Apr 6 2023 Warning (5) TCS Partial Service;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;
19:40:59
Thu Apr 6 2023 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;
19:41:01
Thu Apr 6 2023 Warning (5) TCS Partial Service;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;
19:52:25
Thu Apr 6 2023 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;
19:52:33
Thu Apr 6 2023 Warning (5) TCS Partial Service;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;
20:03:41
Thu Apr 6 2023 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;
20:04:04
Thu Apr 6 2023 Warning (5) TCS Partial Service;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;
20:15:27
Thu Apr 6 2023 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;
20:15:35
Thu Apr 6 2023 Warning (5) TCS Partial Service;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;
20:27:06
Thu Apr 6 2023 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;
20:27:07
Thu Apr 6 2023 Warning (5) TCS Partial Service;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;
20:38:37
Thu Apr 6 2023 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;
20:38:38
Thu Apr 6 2023 Warning (5) TCS Partial Service;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;
20:50:07
Thu Apr 6 2023 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;
20:50:10
Thu Apr 6 2023 Warning (5) TCS Partial Service;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;
20:50:36
Thu Apr 6 2023 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;
Downstream bonded channels
=========================
|
|
|||||||||||||||||
|
Accepted Solution
BruceW
Gold Problem Solver
•
26.3K Messages
2 years ago
Downstream and upstream power levels are both out of spec (too high) and you should have at least 3 upstream channels locked.
Suggest you have a Comcast premise tech identify the cause of these problems and correct them. If an employee does not respond to your message here, 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/. It's not likely they can fix the problem remotely. If not, insist they send a tech out.
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.
(edited)
1
0
Accepted Solution
BruceW
Gold Problem Solver
•
26.3K Messages
2 years ago
Please see Internet Troubleshooting Tips. The power levels in both directions are still too high. Chances are you'll lose connection again.
And again please note:
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.
0
user_3f21c2
Visitor
•
3 Messages
2 years ago
Just additional follow-up info and I've considered this issue closed for now. I have not scheduled an appt for a technician to come up yet; will do that when this issue popped up again. So far, i have not got any network disconnected in the last two days. The power stats are still high though.
0
0