Frequent Visitor
•
22 Messages
Frequent Internet Disconnects
We have been having frequent (1+ times a day) Internet disconnects for some time now. Thinking that it might be the modem, I installed a new modem the other day. But, the problem persists. From what I've seen in the logs, it is always a problem with the upstream (T3) connection dropping. At the end of this message I've attached a screenshot of the modem log.
For testing purposes, I moved the modem as close to the point where the cable comes into the house as possible. There is one splitter in between the cable coming in from the street and the modem with only 6ft of cable between the splitter and the modem. The splitter was provided by Comcast.
Hopefully, the log provides some hint as to why we're experiencing these frequent disconnects.
Any help would be greatly appreciated.
Thank you,
-Jeff
Time |
Priority |
Description |
1970-1-1, 00:01:11 |
Notice (6) |
Honoring MDD; IP provisioning mode = IPv6 |
1970-1-1, 00:00:59 |
Critical (3) |
SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**********;CMTS-MAC=**********;CM-QOS=1.0;CM-VER=3.0; |
1970-1-1, 00:00:59 |
Critical (3) |
SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=**********;CMTS-MAC=**********;CM-QOS=1.0;CM-VER=3.0; |
1970-1-1, 00:00:58 |
Critical (3) |
SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**********;CMTS-MAC=**********;CM-QOS=1.0;CM-VER=3.0; |
1970-1-1, 00:00:55 |
Critical (3) |
SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=**********;CMTS-MAC=**********;CM-QOS=1.0;CM-VER=3.0; |
1970-1-1, 00:00:40 |
Critical (3) |
SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**********;CMTS-MAC=**********;CM-QOS=1.0;CM-VER=3.0; |
1970-1-1, 00:00:40 |
Notice (6) |
WiFi Interface [wl1] set to Channel 153 (Side-Band Channel:N/A) - Reason:INIT |
1970-1-1, 00:00:40 |
Notice (6) |
WiFi Interface [wl0] set to Channel 11 (Side-Band Channel:N/A) - Reason:INIT |
1970-1-1, 00:00:37 |
Critical (3) |
SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**********;CMTS-MAC=**********;CM-QOS=1.0;CM-VER=3.0; |
2024-11-8, 20:21:05 |
Critical (3) |
No UCDs Received - Timeout;;CM-MAC=**********;CMTS-MAC=**********;CM-QOS=1.0;CM-VER=3.0; |
2024-11-8, 20:20:48 |
Critical (3) |
SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**********;CMTS-MAC=**********;CM-QOS=1.0;CM-VER=3.0; |
2024-11-8, 20:20:47 |
Critical (3) |
No UCDs Received - Timeout;;CM-MAC=**********;CMTS-MAC=**********;CM-QOS=1.0;CM-VER=3.0; |
2024-11-8, 20:20:30 |
Critical (3) |
SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**********;CMTS-MAC=**********;CM-QOS=1.0;CM-VER=3.0; |
2024-11-8, 20:20:29 |
Critical (3) |
No UCDs Received - Timeout;;CM-MAC=**********;CMTS-MAC=**********;CM-QOS=1.0;CM-VER=3.0; |
2024-11-8, 20:20:12 |
Critical (3) |
SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**********;CMTS-MAC=**********;CM-QOS=1.0;CM-VER=3.0; |
2024-11-8, 20:20:11 |
Critical (3) |
No UCDs Received - Timeout;;CM-MAC=**********;CMTS-MAC=**********;CM-QOS=1.0;CM-VER=3.0; |
2024-11-8, 20:19:54 |
Critical (3) |
SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**********;CMTS-MAC=**********;CM-QOS=1.0;CM-VER=3.0; |
2024-11-8, 20:19:53 |
Critical (3) |
No UCDs Received - Timeout;;CM-MAC=**********;CMTS-MAC=**********;CM-QOS=1.0;CM-VER=3.0; |
2024-11-8, 20:19:36 |
Critical (3) |
SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**********;CMTS-MAC=**********;CM-QOS=1.0;CM-VER=3.0; |
2024-11-8, 20:19:35 |
Critical (3) |
No UCDs Received - Timeout;;CM-MAC=**********;CMTS-MAC=**********;CM-QOS=1.0;CM-VER=3.0; |
2024-11-8, 20:19:16 |
Critical (3) |
SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**********;CMTS-MAC=00:90:f0:0c:04:00;CM-QOS=1.0;CM-VER=3.0; |
2024-11-8, 20:13:41 |
Critical (3) |
No Ranging Response received - T3 time-out;CM-MAC=**********;CMTS-MAC=00:90:f0:0c:04:00;CM-QOS=1.0;CM-VER=3.0; |
2024-11-8, 20:13:27 |
Critical (3) |
SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**********;CMTS-MAC=00:90:f0:0c:04:00;CM-QOS=1.0;CM-VER=3.0; |
2024-11-8, 20:09:34 |
Critical (3) |
No Ranging Response received - T3 time-out;CM-MAC=**********;CMTS-MAC=00:90:f0:0c:04:00;CM-QOS=1.0;CM-VER=3.0; |
2024-11-8, 20:05:29 |
Critical (3) |
No Ranging Response received - T3 time-out;CM-MAC=**********;CMTS-MAC=00:90:f0:0c:04:00;CM-QOS=1.0;CM-VER=3.0; |
2024-11-8, 20:05:22 |
Critical (3) |
SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**********;CMTS-MAC=**********;CM-QOS=1.0;CM-VER=3.0; |
2024-11-8, 20:05:20 |
Critical (3) |
SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=**********;CMTS-MAC=**********;CM-QOS=1.0;CM-VER=3.0; |
2024-11-8, 20:05:17 |
Critical (3) |
SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**********;CMTS-MAC=**********;CM-QOS=1.0;CM-VER=3.0; |
2024-11-8, 20:05:16 |
Critical (3) |
SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=**********;CMTS-MAC=**********;CM-QOS=1.0;CM-VER=3.0; |
2024-11-8, 20:05:08 |
Critical (3) |
SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**********;CMTS-MAC=**********;CM-QOS=1.0;CM-VER=3.0; |
2024-11-8, 20:05:07 |
Critical (3) |
SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=**********;CMTS-MAC=**********;CM-QOS=1.0;CM-VER=3.0; |
2024-11-8, 20:05:07 |
Critical (3) |
SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**********;CMTS-MAC=**********;CM-QOS=1.0;CM-VER=3.0; |
2024-11-8, 20:05:06 |
Critical (3) |
SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=**********;CMTS-MAC=**********;CM-QOS=1.0;CM-VER=3.0; |
2024-11-8, 20:05:04 |
Critical (3) |
SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**********;CMTS-MAC=**********;CM-QOS=1.0;CM-VER=3.0; |
2024-11-8, 20:05:02 |
Critical (3) |
SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=**********;CMTS-MAC=**********;CM-QOS=1.0;CM-VER=3.0; |
2024-11-8, 20:05:02 |
Critical (3) |
SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**********;CMTS-MAC=**********;CM-QOS=1.0;CM-VER=3.0; |
2024-11-8, 20:04:59 |
Critical (3) |
SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=**********;CMTS-MAC=**********;CM-QOS=1.0;CM-VER=3.0; |
2024-11-8, 20:04:58 |
Critical (3) |
SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**********;CMTS-MAC=**********;CM-QOS=1.0;CM-VER=3.0; |
2024-11-8, 20:04:49 |
Critical (3) |
SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=**********;CMTS-MAC=**********;CM-QOS=1.0;CM-VER=3.0; |
2024-11-8, 20:04:48 |
Critical (3) |
No UCDs Received - Timeout;;CM-MAC=**********;CMTS-MAC=**********;CM-QOS=1.0;CM-VER=3.0; |
EG
Expert
•
107.1K Messages
15 days ago
@JeffMcG
Your post with that pic of the error log entries was marked as being "Private" by the forum bot because it contains CM MAC and the CMTS MAC addresses. They are considered to be personal information. The posting of personally identifiable information is a violation of their forum guidelines. Please delete that pic only.
What you can do instead is to copy all of the text (instead of using an image) and paste it into your next post here, but you'll need to redact all of the CM MAC and CMTS MAC addresses. The bot will not allow your post to be seen publicly.
4
0
EG
Expert
•
107.1K Messages
7 days ago
@JeffMcG
The upstream power is too high / out of spec. That can cause random disconnects, spontaneous re-booting of the modem, speed, packet loss, latency problems, and the un-bonding of channels.
In an effort to try to obtain better connectivity / more wiggle room, check to see if there are any excess/unneeded coax cable splitters in the line leading to the modem that can be eliminated/re-configured. Any splitters that remain should be high quality and cable rated for 5-1002 MHz, bi-directional, and no gold colored garbage from Home Depot, Target, Wal-Mart, etc. Splitters should be swapped with known to be good / new ones to test.
Also check the coax cable for any damage such as cuts, nicks, abrasions, kinks, sharp bends, etc.
If there aren't any unneeded splitters that can be eliminated and if your coax wiring setup can't be reconfigured so that there is a single two-way splitter connected directly off of the drop from the street / pole with one port feeding the modem and the other port feeding the rest of the house/equipment with additional splits as needed and you've checked all the wiring and fittings for integrity and tightness and refresh them by taking them apart then check for and clean off any corrosion / oxidation on the center wire and put them back together again, then perhaps it's best to book a tech visit to investigate and correct.
Good luck with it !
2
0