NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
C7000 v2 inconsistent download speeds - 2.0-300.0 Mbps
Hello, I have been experiencing bad download speeds for several weeks and it is getting worse. I have spoken to several Comcast phone and chat associates trying to fix the issue with no luck. ...
You got the cable connections page but not the event logs.
Are you doing any torrenting? I noticed when I tested one that it struggles with multiple connections from a torrent client. I'd had my torrent client set to 800 connections possible and had the same symptoms. I had to set it down to 200
I posted the events log on Comcast forums and they got flagged due to the MAC address being displayed, was unsure if the same would happen on this forum as well.
I am not torrenting, only basic internet use. I do connect to employers VPN for remote work, which is laggy with regular disconnects.
| Time | Priority | Description |
| 1970-1-1, 00:00:49 | Notice (6) | Honoring MDD; IP provisioning mode = IPv6 |
| 1970-1-1, 00:00:42 | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=80:cc:xx:xx:xx:xx;CMTS-MAC=00:01:xx:xx:xx:xx;CM-QOS=1.0;CM-VER=3.0; |
| 1970-1-1, 00:00:40 | Notice (6) | WiFi Interface [wl1] set to Channel 161 (Side-Band Channel:N/A) - Reason:INIT |
| 1970-1-1, 00:00:40 | Notice (6) | WiFi Interface [wl0] set to Channel 8 (Side-Band Channel:N/A) - Reason:INIT |
| 1970-1-1, 00:00:37 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=80:cc:xx:xx:xx:xx;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; |
| 2022-5-6, 09:42:45 | Critical (3) | Resetting the cable modem due to docsDevResetNow |
| 1970-1-1, 00:00:37 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=80:cc:xx:xx:xx:xx;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; |
| 1970-1-1, 00:00:44 | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=80:cc:xx:xx:xx:xx;CMTS-MAC=00:01:xx:xx:xx:xx;CM-QOS=1.0;CM-VER=3.0; |
| 1970-1-1, 00:00:37 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=80:cc:xx:xx:xx:xx;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; |
| 1970-1-1, 00:00:45 | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=80:cc:xx:xx:xx:xx;CMTS-MAC=00:01:xx:xx:xx:xx;CM-QOS=1.0;CM-VER=3.0; |
| 1970-1-1, 00:00:38 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=80:cc:xx:xx:xx:xx;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; |
| 2022-5-5, 15:45:39 | Critical (3) | Resetting the cable modem due to docsDevResetNow |
| 1970-1-1, 00:00:37 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=80:cc:xx:xx:xx:xx;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; |
| 1970-1-1, 00:00:45 | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=80:cc:xx:xx:xx:xx;CMTS-MAC=00:01:xx:xx:xx:xx;CM-QOS=1.0;CM-VER=3.0; |
| 1970-1-1, 00:00:38 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=80:cc:xx:xx:xx:xx;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; |
| 1970-1-1, 00:00:44 | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=80:cc:xx:xx:xx:xx;CMTS-MAC=00:01:xx:xx:xx:xx;CM-QOS=1.0;CM-VER=3.0; |
| 1970-1-1, 00:00:37 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=80:cc:xx:xx:xx:xx;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; |
| 2022-5-2, 16:39:14 | Critical (3) | Resetting the cable modem due to docsDevResetNow |
| 1970-1-1, 00:00:44 | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=80:cc:xx:xx:xx:xx;CMTS-MAC=00:01:xx:xx:xx:xx;CM-QOS=1.0;CM-VER=3.0; |
| 1970-1-1, 00:00:37 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=80:cc:xx:xx:xx:xx;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; |
| 2022-5-2, 15:58:06 | Critical (3) | Resetting the cable modem due to docsDevResetNow |
| 1970-1-1, 00:00:45 | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=80:cc:xx:xx:xx:xx;CMTS-MAC=00:01:xx:xx:xx:xx;CM-QOS=1.0;CM-VER=3.0; |
| 1970-1-1, 00:00:38 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=80:cc:xx:xx:xx:xx;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; |
| 2022-4-28, 16:18:27 | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=80:cc:xx:xx:xx:xx;CMTS-MAC=00:01:xx:xx:xx:xx;CM-QOS=1.0;CM-VER=3.0; |
| 2022-4-28, 16:18:20 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=80:cc:xx:xx:xx:xx;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; |
| 2022-4-28, 16:18:18 | Critical (3) | No UCDs Received - Timeout;;CM-MAC=80:cc:xx:xx:xx:xx;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; |
| 2022-4-28, 16:18:02 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=80:cc:xx:xx:xx:xx;CMTS-MAC=00:01:xx:xx:xx:xx;CM-QOS=1.0;CM-VER=3.0; |
| 1970-1-1, 00:01:19 | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=80:cc:xx:xx:xx:xx;CMTS-MAC=00:01:xx:xx:xx:xx;CM-QOS=1.0;CM-VER=3.0; |
| 1970-1-1, 00:01:11 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=80:cc:xx:xx:xx:xx;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; |
| 1970-1-1, 00:01:10 | Critical (3) | No UCDs Received - Timeout;;CM-MAC=80:cc:xx:xx:xx:xx;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; |
| 1970-1-1, 00:00:53 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=80:cc:xx:xx:xx:xx;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; |
| 1970-1-1, 00:00:43 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=80:cc:xx:xx:xx:xx;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; |
| 1970-1-1, 00:00:42 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=80:cc:xx:xx:xx:xx;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; |
| 1970-1-1, 00:00:39 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=80:cc:xx:xx:xx:xx;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; |
Your logs are indicating a line issue thats trigger a reset from the cmts.
If you've already checked all your lines/connections, then the isp would need to check it.
Start with removing any amplifiers, signal attenuators, or splitters from the coax.
From there check the line for kinks, damage, moisture in the line.
Check the connectors for improperly made ends, foil touching the copper coax line, bad/old/cheap connectors, or corroded connections. Replace them if you do.
If you can, simply connect the modem right where the coax comes into the home. This prevents wiring in the home from being the issue. And some ISP’s charge if the wiring issue is in the home. So this helps prevent this.10-4. I live in an apartment building but I'll try connecting it to the other entry point.
The cable is currently directly connected to the coax, no splitters or amplifiers are connected.
I appreciate you helping out plemans. I wanted to ask someone more knowledgeable before committing to an ISP tech visit and fee vs returning/purchasing a new modem/router.