Visitor
•
5 Messages
Internet Dropping Periodically (once or twice a week) or every 30 minutes sometimes
Hello, I have a NETGEAR Nighthawk Cable Modem WiFi Router Combo C7000v2 and running firmware V1.03.08
I have two issues that are happening:
Scenario 1: The internet drops once or twice a week and I have to reboot the Netgear combo router/modem to get it back up. (been happening for more than 6 months)
Scenario 2: Started happening today, internet goes down for 30 minutes and then comes back up and do the same thing over and over.
I rebooted, replaced coaxial cables and splitter and made sure they are plugged in all the way.
I looked at my router logs and I saw the time is behind by 1 hour from what it should be (Central Time) I also noticed some critical alerts at the same time the internet was dropping and coming back up and I think it has something to do with the issue
Time Priority Description
2022-9-22, 08:17:23 Warning (5) MDD message timeout;CM-MAC=XX:XX:XX:XX:XX:XX;CM-MAC=XX:XX:XX:XX:XX:XX;CM-QOS=1.1;CM-VER=3.0;
1970-1-1, 00:01:09 Notice (6) Honoring MDD; IP provisioning mode = IPv6
1970-1-1, 00:00:45 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=XX:XX:XX:XX:XX:XX;CM-MAC=XX:XX:XX:XX:XX:XX;CM-QOS=1.0;CM-VER=3.0;
1970-1-1, 00:00:42 Notice (6) WiFi Interface [wl1] set to Channel 153 (Side-Band Channel:N/A) - Reason:INIT
1970-1-1, 00:00:42 Notice (6) WiFi Interface [wl0] set to Channel 6 (Side-Band Channel:10) - Reason:INIT
1970-1-1, 00:00:39 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2022-9-22, 08:14:48 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=XX:XX:XX:XX:XX:XX;CM-MAC=XX:XX:XX:XX:XX:XX;CM-QOS=1.0;CM-VER=3.0;
2022-9-22, 08:13:34 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2022-9-22, 08:13:33 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2022-9-22, 08:13:33 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2022-9-22, 08:13:26 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2022-9-22, 08:13:18 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=XX:XX:XX:XX:XX:XX;CM-MAC=XX:XX:XX:XX:XX:XX;CM-QOS=1.0;CM-VER=3.0;
2022-9-22, 08:13:11 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=XX:XX:XX:XX:XX:XX;CM-MAC=XX:XX:XX:XX:XX:XX;CM-QOS=1.0;CM-VER=3.0;
2022-9-22, 08:13:10 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=XX:XX:XX:XX:XX:XX;CM-MAC=XX:XX:XX:XX:XX:XX;CM-QOS=1.0;CM-VER=3.0;
2022-9-22, 08:13:09 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=XX:XX:XX:XX:XX:XX;CM-MAC=XX:XX:XX:XX:XX:XX;CM-QOS=1.0;CM-VER=3.0;
2022-9-22, 08:13:06 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=XX:XX:XX:XX:XX:XX;CM-MAC=XX:XX:XX:XX:XX:XX;CM-QOS=1.0;CM-VER=3.0;
2022-9-22, 08:11:18 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=XX:XX:XX:XX:XX:XX;CM-MAC=XX:XX:XX:XX:XX:XX;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=XX:XX:XX:XX:XX:XX;CM-MAC=XX:XX: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=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2022-9-22, 08:06:38 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=XX:XX:XX:XX:XX:XX;CM-MAC=XX:XX:XX:XX:XX:XX;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=XX:XX:XX:XX:XX:XX;CM-MAC=XX:XX: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=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2022-9-22, 08:01:04 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=XX:XX:XX:XX:XX:XX;CM-MAC=XX:XX:XX:XX:XX:XX;CM-QOS=1.1;CM-VER=3.0;
2022-9-22, 07:48:17 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2022-9-22, 07:48:15 Critical (3) No UCDs Received - Timeout;;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2022-9-22, 07:47:58 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2022-9-22, 07:47:57 Critical (3) No UCDs Received - Timeout;;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2022-9-22, 07:47:41 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2022-9-22, 07:47:39 Critical (3) No UCDs Received - Timeout;;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2022-9-22, 07:47:22 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2022-9-22, 07:47:21 Critical (3) No UCDs Received - Timeout;;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2022-9-22, 07:47:04 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2022-9-22, 07:47:03 Critical (3) No UCDs Received - Timeout;;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2022-9-22, 07:46:46 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2022-9-22, 07:46:45 Critical (3) No UCDs Received - Timeout;;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2022-9-22, 07:46:28 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2022-9-22, 07:46:26 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=XX:XX:XX:XX:XX:XX;CM-MAC=XX:XX:XX:XX:XX:XX;CM-QOS=1.0;CM-VER=3.0;
2022-9-22, 07:45:36 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.0;CM-VER=3.0;
2022-9-22, 07:45:08 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.0;CM-VER=3.0;
2022-9-22, 07:45:03 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Can someone please he
Accepted Solution
EG
Expert
•
111.4K Messages
3 years ago
Everything is 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. The connection quality is terrible ! I'm surprised that you are able to be online at all.....
In an effort to try to obtain better connectivity / more wiggle room, check to see if there are there 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-1000 MHz, bi-directional, and no gold colored garbage from Radio Shack, Home Depot, Target, 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 !
3
EG
Expert
•
111.4K Messages
3 years ago
The time is normal. Cable modems don't do DST. It doesn't affect their performance, only the time / date stamps.
That said. Please also copy all of the text in its entirety of the *Downstream Power Levels*, the *SNR's* (Signal to Noise Ratios), and the *Upstream Power Level* numbers and paste them into your next post.
1
0