Time |
Priority |
Description |
Thu Sep 28 11:38:07 2023 |
Critical (3) |
No Ranging Response received - T3 time-out; |
Thu Sep 28 11:39:40 2023 |
Critical (3) |
Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out; |
Thu Sep 28 11:41:44 2023 |
Critical (3) |
No Ranging Response received - T3 time-out; |
Thu Sep 28 11:43:19 2023 |
Critical (3) |
Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out; |
Thu Sep 28 11:43:33 2023 |
Critical (3) |
No Ranging Response received - T3 time-out; |
Thu Sep 28 11:44:50 2023 |
Critical (3) |
Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out; |
Thu Sep 28 11:45:00 2023 |
Critical (3) |
No Ranging Response received - T3 time-out; |
Thu Sep 28 11:45:53 2023 |
Critical (3) |
Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out; |
Thu Sep 28 11:46:16 2023 |
Critical (3) |
No Ranging Response received - T3 time-out; |
Thu Sep 28 11:47:25 2023 |
Critical (3) |
Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out; |
Thu Sep 28 11:47:33 2023 |
Critical (3) |
No Ranging Response received - T3 time-out; |
Thu Sep 28 11:48:32 2023 |
Critical (3) |
Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out; |
Thu Sep 28 11:48:47 2023 |
Critical (3) |
No Ranging Response received - T3 time-out; |
Thu Sep 28 11:49:52 2023 |
Critical (3) |
Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out; |
Thu Sep 28 11:50:11 2023 |
Critical (3) |
No Ranging Response received - T3 time-out; |
Thu Sep 28 11:51:26 2023 |
Critical (3) |
Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out; |
Thu Sep 28 11:51:29 2023 |
Critical (3) |
SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;; |
Thu Sep 28 11:51:36 2023 |
Warning (5) |
Lost MDD Timeout; |
Thu Sep 28 11:51:46 2023 |
Critical (3) |
No UCDs Received - Timeout;; |
Thu Sep 28 11:52:08 2023 |
Critical (3) |
No Ranging Response received - T3 time-out; |
Thu Sep 28 11:53:05 2023 |
Critical (3) |
Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out; |
Thu Sep 28 11:53:17 2023 |
Critical (3) |
No Ranging Response received - T3 time-out; |
Thu Sep 28 11:53:30 2023 |
Critical (3) |
Started Unicast Maintenance Ranging - No Response received - T3 time-out; |
Thu Sep 28 11:54:12 2023 |
Critical (3) |
Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out; |
Thu Sep 28 11:54:29 2023 |
Critical (3) |
No Ranging Response received - T3 time-out; |
Thu Sep 28 11:55:42 2023 |
Critical (3) |
Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out; |
Thu Sep 28 11:55:55 2023 |
Critical (3) |
No Ranging Response received - T3 time-out; |
Thu Sep 28 11:56:30 2023 |
Critical (3) |
Started Unicast Maintenance Ranging - No Response received - T3 time-out; |
Thu Sep 28 11:57:02 2023 |
Critical (3) |
Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out; |
Thu Sep 28 11:57:09 2023 |
Critical (3) |
No Ranging Response received - T3 time-out |
Thu Sep 28 11:57:21 2023 |
Notice (6) |
Honoring MDD; IP provisioning mode = IPv6 |
Thu Sep 28 11:58:36 2023 |
Critical (3) |
Started Unicast Maintenance Ranging - No Response received - T3 time-out; |
BruceW
Gold Problem Solver
•
26.3K Messages
2 years ago
Downstream, power levels and SNR values look good. Error counts seem high, but can't really be evaluated without knowing how long it has been since the counters were reset. The upstream power levels look good. There are other signal quality measures that the modem does not report, and the intermittent nature of the problem makes it harder to troubleshoot, so all we can say is between your observations and the Event Log entries, something is wrong.
Network connection problems like this are often due to poor coax connections or damaged coax cable, usually in or near your home. Running the cable through a surge protector, a defective splitter, or too many splitters can cause signal problems as well. If there is an amplifier in the line make sure it's getting power.
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 and 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 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 (approx $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.
0
0
user_281b6d
4 Messages
2 years ago
Thanks for taking a look. Per the coax, we don’t have a splitter or amplifier. The line from outside comes in, hits a single adapter (female-to-female), and goes directly to the modem. Nothing on the interior has been modified or moved, and the connections are solid. The modem currently has my up time as 1d: 15min, but there have been lapses in connectivity all day. I’ll troubleshoot the best I can and then have a tech out to check the supply coax. Thanks again.
0
0