NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
MileHighBurt
Mar 26, 2023Aspirant
CAX30 has to restart multiple times a day
I have the latest firmware and have had no issue in the past with connectivity. For some reason, after losing power during a storm a few weeks ago, I now have to restart the router every few hours b...
FURRYe38
Mar 26, 2023Guru - Experienced User
What Firmware version is currently loaded?
What ISP are you with?
Please post a copy and paste of the modems connection status and event log page.
https://kb.netgear.com/30007/How-do-I-obtain-the-cable-connection-information-from-a-NETGEAR-cable-modem-modem-router
https://kb.netgear.com/30008/How-do-I-view-or-clear-the-event-logs-on-my-NETGEAR-cable-modem-or-modem-router
Have the ISP check the signal and line quality UP to the modem. Be sure the ISP provisions the modem correctly.
Be sure there are no coax cable line splitters in the between the modem and ISP service box.
Be sure your using good quality RG6 coax cable up to the modem.
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, loose connections, bad/old/cheap connectors, or corroded connections. Replace them if you do.
Be sure to power OFF the modem for 1 minute then back ON.
https://community.netgear.com/t5/Cable-Modems-Routers/General-info-and-Troubleshooting-for-Cable-Modems/m-p/1530376#M12853
https://kb.netgear.com/24311/Power-level-guidelines-for-a-NETGEAR-cable-modem-router
https://www.duckware.com/tech/solving-intermittent-cable-modem-issues.html
- MileHighBurtMar 26, 2023Aspirant
Cable Information Hardware Version V1.01 Firmware Version V2.1.3.10 Cable Firmware Version V1.04.05 Cable Modem Serial Number 6PK122WL0222A CM certificate Installed CM MAC 34:98:B5:8F:DE:38 LAN Port MAC Address 34:98:B5:8F:DE:3A IP Address/Mask 192.168.1.1/255.255.255.0 DHCP Enabled REBOOTInternet Port MAC Address 34:98:B5:8F:DE:39 IP Address 74.139.234.132
2607:fcc8:bfc0:64:541f:6d3c:d513:a1c2Connection DHCP Mask 255.255.224.0
128Default Gateway 74.139.224.1
fe80::201:5cff:fe64:5046Domain Name Server 209.18.47.63, 209.18.47.61
2001:1998:f00:1::1, 2001:1998:f00:2::1Show Statistics Connection StatusWireless Settings (2.4GHz) Name (SSID) Spaceballs_TheWIFI! Region United States Channel Auto (5) Mode Up to 860Mbps Wireless AP On Broadcast Name On Wi-Fi Protected Setup Configured Wireless Settings (5GHz) Smart Connect ENABLED Channel 149 + 153(P) + 157 + 161 Mode Up to 1801Mbps Using Spectrum
- MileHighBurtMar 26, 2023Aspirant
Time Priority Description 2023-03-26 17:58:50 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=34:98:b5:8f:de:38;CMTS-MAC=00:01:5c:64:50:55;CM-QOS=1.1;CM-VER=3.1; 2023-03-26 17:58:47 Notice (6) DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2.;CM-MAC=34:98:b5:8f:de:38;CMTS-MAC=00:01:5c:64:50:55;CM-QOS=1.1;CM-VER=3.1; 2023-03-26 17:58:46 Notice (6) TLV-11 - unrecognized OID;CM-MAC=34:98:b5:8f:de:38;CMTS-MAC=00:01:5c:64:50:55;CM-QOS=1.1;CM-VER=3.1; 2023-03-26 17:58:45 Error (4) Missing BP Configuration Setting TLV Type: 17.9;CM-MAC=34:98:b5:8f:de:38;CMTS-MAC=00:01:5c:64:50:55;CM-QOS=1.1;CM-VER=3.1; 2023-03-26 17:58:45 Error (4) Missing BP Configuration Setting TLV Type: 17.8;CM-MAC=34:98:b5:8f:de:38;CMTS-MAC=00:01:5c:64:50:55;CM-QOS=1.1;CM-VER=3.1; 1970-01-01 00:00:33 Notice (6) Overriding MDD IP initialization parameters; IP provisioning mode = IPv6 1970-01-01 00:00:28 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=34:98:b5:8f:de:38;CMTS-MAC=00:01:5c:64:50:55;CM-QOS=1.1;CM-VER=3.1; 1970-01-01 00:00:24 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=34:98:b5:8f:de:38;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; 1970-01-01 00:00:29 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=34:98:b5:8f:de:38;CMTS-MAC=00:01:5c:64:50:55;CM-QOS=1.1;CM-VER=3.1; 1970-01-01 00:00:24 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=34:98:b5:8f:de:38;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; 1970-01-01 00:00:30 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=34:98:b5:8f:de:38;CMTS-MAC=00:01:5c:64:50:55;CM-QOS=1.1;CM-VER=3.1; 1970-01-01 00:00:25 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=34:98:b5:8f:de:38;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; 1970-01-01 00:00:30 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=34:98:b5:8f:de:38;CMTS-MAC=00:01:5c:64:50:55;CM-QOS=1.1;CM-VER=3.1; 1970-01-01 00:00:24 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=34:98:b5:8f:de:38;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; 2023-03-24 18:51:15 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=34:98:b5:8f:de:38;CMTS-MAC=00:01:5c:64:50:55;CM-QOS=1.1;CM-VER=3.1; 1970-01-01 00:00:29 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=34:98:b5:8f:de:38;CMTS-MAC=00:01:5c:64:50:55;CM-QOS=1.1;CM-VER=3.1; 1970-01-01 00:00:24 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=34:98:b5:8f:de:38;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; 1970-01-01 00:00:29 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=34:98:b5:8f:de:38;CMTS-MAC=00:01:5c:64:50:55;CM-QOS=1.1;CM-VER=3.1; 1970-01-01 00:00:24 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=34:98:b5:8f:de:38;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; 1970-01-01 00:00:28 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=34:98:b5:8f:de:38;CMTS-MAC=00:01:5c:64:50:55;CM-QOS=1.1;CM-VER=3.1; 1970-01-01 00:00:24 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=34:98:b5:8f:de:38;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; 2023-03-22 15:17:48 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=34:98:b5:8f:de:38;CMTS-MAC=00:01:5c:64:50:55;CM-QOS=1.1;CM-VER=3.1; 1970-01-01 00:00:24 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=34:98:b5:8f:de:38;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; 1970-01-01 00:02:36 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=34:98:b5:8f:de:38;CMTS-MAC=00:01:5c:64:50:55;CM-QOS=1.1;CM-VER=3.1; 1970-01-01 00:02:17 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=34:98:b5:8f:de:38;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; 1970-01-01 00:00:27 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=34:98:b5:8f:de:38;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; - FURRYe38Mar 27, 2023Guru - Experienced User
What Firmware version is currently loaded?
What ISP are you with?
Please post a copy and paste of the modems connection status page.
https://kb.netgear.com/30007/How-do-I-obtain-the-cable-connection-information-from-a-NETGEAR-cable-modem-modem-routerThe ISP needs to review and resolve all Criticals, Errors and Warnings seen in the Events log page...
- MileHighBurtApr 02, 2023Aspirant
So I got Spectrum out and there was a 15db drop in signal from the source to my modem/router. They removed a three way splitter that had a 5db attenuation and the modem passed the signal test. I Then connected my main PC to the modem via ethernet to test (if it did need to be reset again) to see if the wifi was having issues separate from the hard connection. I still have to reset router for wifi, though the ethernet doesnt have the same loss of signal. I tried disabling the smartconnect to see if that does anything? Maybe the router choosing between 2.4 and 5ghz is an issue? I also cleared the event log yesterday and recorded the current event log below. All firmwares are up to date.
2023-04-01 18:54:47Notice (6)DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2.;CM-MAC=34:98:b5:8f:de:38;CMTS-MAC=00:01:5c:64:50:55;CM-QOS=1.1;CM-VER=3.1;
2023-04-01 18:54:46Notice (6)TLV-11 - unrecognized OID;CM-MAC=34:98:b5:8f:de:38;CMTS-MAC=00:01:5c:64:50:55;CM-QOS=1.1;CM-VER=3.1;
2023-04-01 18:54:46Error (4)Missing BP Configuration Setting TLV Type: 17.9;CM-MAC=34:98:b5:8f:de:38;CMTS-MAC=00:01:5c:64:50:55;CM-QOS=1.1;CM-VER=3.1;
2023-04-01 18:54:46Error (4)Missing BP Configuration Setting TLV Type: 17.8;CM-MAC=34:98:b5:8f:de:38;CMTS-MAC=00:01:5c:64:50:55;CM-QOS=1.1;CM-VER=3.1;
1970-01-01 00:00:31Notice (6)Overriding MDD IP initialization parameters; IP provisioning mode = IPv6
1970-01-01 00:00:28Critical (3)No Ranging Response received - T3 time-out;CM-MAC=34:98:b5:8f:de:38;CMTS-MAC=00:01:5c:64:50:55;CM-QOS=1.1;CM-VER=3.1;
1970-01-01 00:00:24Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=34:98:b5:8f:de:38;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
1970-01-01 00:00:29Critical (3)No Ranging Response received - T3 time-out;CM-MAC=34:98:b5:8f:de:38;CMTS-MAC=00:01:5c:64:50:55;CM-QOS=1.1;CM-VER=3.1;
1970-01-01 00:00:24Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=34:98:b5:8f:de:38;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;