New Poster
•
1 Message
I think the signal noise is coming from outside the house
My wife and I both teach at universities. We are "providing remote instruction" from home.
We have been having service interruptions consistent with some other reports on this board --- clusters of T3/T4 timeouts.
I have ruled out everything downstream from the modem. (The modem logs make it clear that there is a connection issue. My setup is modem -> router -> network, and during these interruptions my router's diagnostics indicate it has lost Internet but there are no issues with physical connections or wifi.)
I have been in touch with XFinity Support but got no help other than suggestion to speak to modem manufacturer (which I did, see below).
I think the signal noise is coming from outside the house. I'm writing to seek support in diagnosing and remedying this issue.
Here is today's example from my modem's logs:
Tue Sep 22 09:47:56 2020 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out; [macs redacted] |
Tue Sep 22 09:47:57 2020 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;[macs redacted] |
Tue Sep 22 09:48:00 2020 | Warning (5) | MDD message timeout;[macs redacted] |
Tue Sep 22 09:48:01 2020 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;[macs redacted] |
Tue Sep 22 09:48:02 2020 | Warning (5) | MDD message timeout;[macs redacted] |
Tue Sep 22 09:48:11 2020 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;[macs redacted] |
Tue Sep 22 09:48:16 2020 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;[macs redacted] |
Tue Sep 22 09:48:16 2020 | Warning (5) | MDD message timeout;[macs redacted] |
Tue Sep 22 09:48:22 2020 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;[macs redacted] |
Tue Sep 22 09:48:22 2020 | Warning (5) | MDD message timeout;[macs redacted] |
Tue Sep 22 09:48:26 2020 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;[macs redacted] |
Tue Sep 22 09:52:31 2020 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;[macs redacted] |
Tue Sep 22 09:52:44 2020 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;[macs redacted] |
Tue Sep 22 09:52:49 2020 | Notice (6) | Honoring MDD; IP provisioning mode = IPv6 |
Tue Sep 22 09:53:35 2020 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;[macs redacted] |
Tue Sep 22 09:54:08 2020 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out; [macs redacted] |
Tue Sep 22 09:54:20 2020 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;[macs redacted] |
Tue Sep 22 09:54:24 2020 | Notice (6) | Honoring MDD; IP provisioning mode = IPv6 |
Tue Sep 22 09:55:23 2020 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;[macs redacted] |
Tue Sep 22 09:55:56 2020 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;[macs redacted] |
Tue Sep 22 10:00:11 2020 | Critical (3) | No Ranging Response received - T3 time-out;[macs redacted] |
Tue Sep 22 10:01:22 2020 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;[macs redacted] |
Tue Sep 22 10:01:26 2020 | Critical (3) | No Ranging Response received - T3 time-out;[macs redacted] |
Tue Sep 22 10:01:34 2020 | Notice (6) | Honoring MDD; IP provisioning mode = IPv6 |
Tue Sep 22 10:19:25 2020 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;[macs redacted] |
Here are the connection stats (packet counts reflect 6 days of uptime):
| |||||||||||||||||||||||||||||||||||
|
Usually my modem gets 4 upstream channels, sometimes it gets 1 upstream, it works either way. Our plan is for relatively low speeds.
I called XFinity support about this last week (hence the 6 day uptime -- that's when we power-cycled during diagnostics). XFinity support agreed the open question is whether the issue is the modem, the cable from the modem to the wall jack, or outside my building. XFinity support was unable to offer any help other than suggest I contact the modem manufacturer.
Rep for the modem manufacturer (Motorola MB7420) says that if the modem itself was malfunctioning, the device would most likely be completely inoperable. Rep also says that the error log is consistent with connection trouble upstream (it could be the modem, it's just unlikely). Rep also says that having 1 rather than 4 upstream channels is not necessarily an issue at relatively lower speed plans (like the one we have).
Other people on this board have said that upstream power levels like the one reported here are high. Is it high?
The modem is connected to the wall jack through a daisy chain of 2 coaxial cables:
modem -> coax cable 1 -> coax cable 2 -> wall jack
All of the connections are snug. We've done nothing to disturb those cables so there's no reason to expect a change in the house wiring caused a change in service.
A previous disruption happened one day after an outage was reported in my area.
A disruption happened yesterday and a few minutes afterwards I saw a technician working on a box on a utility pole in the alley behind my building. And another disruption happened again today. All of them show up on the modem's logs.
So I think the signal noise is coming from outside the house.
I welcome suggestions on what to do next, additional information about log readouts, and more information from XFinity/Comcast regarding the state of service in my area.
CCAndrew
Gold Problem Solver
•
25.9K Messages
5 years ago
0
0