NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Homeuser66
Jun 22, 2022Guide
Have to reset Modem more often now, due to WiFi not working.
I've had my Netgear CAX80 for almost a year now. I have never had any issues until recently. I have to reset my Modem almost every other day. My CAX80 will keep an Ethernet connection, but the Wi-Fi ...
Homeuser66
Jun 22, 2022Guide
That's just the thing. I worked at Comcast as a installation tech, so I ran the line myself. I put my own fittings on and ran the line inside my house. I've double checked every fitting and they are spot on, even changed 1 just because. Things have changed since I worked there, but the line I ran (shielded) is only 2 years old, if that. I've even tested the line out the window directly to ground block to modem.. I have a call into Comcast. I'll see what they have to say..
Thanks!
Thanks!
FURRYe38
Jun 22, 2022Guru - Experienced User
Ok kewl. ya I found sometimes if the correct or un-correctables were seen with mine, I found one jack was not fitted correctly. All zero'd after re-fitting.
My ISP put an attenuator on mine as my power was too high. 😏
- Homeuser66Jun 22, 2022GuideThanks!
- Homeuser66Jun 21, 2022Guide
I would also like to know this answer.
I have to reset my Modem almost every other day. My CAX80 will keep a land line connection, but the Wi-Fi (both, 2G & 5G I'm not using the Wi-Fi 6) will drop out and ALL my Wi-Fi devices can't connect to it. When I try, it says, "Can't connect, no internet". Yet I can connect with a direct line with an ethernet cable. So, just the Wi-Fi is down, not my whole internet. My 2Gchannel is set for AUTO, while my 5G is set for 36, at the moment.
I have Xfinity and a direct line from the ground block (the barrel connection outside) directly to my modem. Which the total length is no more than 20 feet.
I have this from the Diagnostic Logs:
Cable Diagnostic
Status: Good
Action: Your setup looks fine. If you are still experience an internet issue, the Netgear Cable Knowledge Base can provide additional troubleshooting info.
Internet Access: Good
Downstream Status: Good
Downstream Power Level: Good
Downstream SNR: Good
Upstream Status: Good
Upstream Power Level: Good
Current time: Tue Jun 21 06:00:43 2022Startup Procedure
Acquire Downstream Channel: 675 MHz Locked
Connectivity State: OK Operational
Boot State: OK Operational
Security: Enabled BPI+Downstream Bonded Channels
Channel LockedStatus Modulation ChannelID Frequency Power SNR Correctables Uncorrectables
1 Locked 256 QAM 41 675000000 Hz -5.4 dBmV 38.1 dB 1 0
2 Locked 256 QAM 13 507000000 Hz -3.7 dBmV 41.4 dB 0 0
3 Locked 256 QAM 14 513000000 Hz -4.1 dBmV 41.2 dB 0 0
4 Locked 256 QAM 15 519000000 Hz -4 dBmV 41.2 dB 0 0
5 Locked 256 QAM 16 525000000 Hz -3.1 dBmV 41.5 dB 0 0
6 Locked 256 QAM 17 531000000 Hz -3.4 dBmV 41.4 dB 0 0
7 Locked 256 QAM 18 537000000 Hz -3.7 dBmV 41.2 dB 0 0
8 Locked 256 QAM 19 543000000 Hz -3.9 dBmV 41.1 dB 0 0
9 Locked 256 QAM 20 549000000 Hz -4.1 dBmV 41 dB 0 0
10 Locked 256 QAM 21 555000000 Hz -4.2 dBmV 40.8 dB 0 0
11 Locked 256 QAM 22 561000000 Hz -4.2 dBmV 40.8 dB 0 0
12 Locked 256 QAM 23 567000000 Hz -4.1 dBmV 40.9 dB 0 0
13 Locked 256 QAM 24 573000000 Hz -4.1 dBmV 40.8 dB 0 0
14 Locked 256 QAM 25 579000000 Hz -3.9 dBmV 40.9 dB 0 0
15 Locked 256 QAM 26 585000000 Hz -4 dBmV 40.8 dB 0 0
16 Locked 256 QAM 27 591000000 Hz -3.8 dBmV 40.9 dB 0 0
17 Locked 256 QAM 28 597000000 Hz -3.9 dBmV 40.8 dB 0 0
18 Locked 256 QAM 29 603000000 Hz -4.3 dBmV 40.5 dB 0 0
19 Locked 256 QAM 30 609000000 Hz -4.9 dBmV 40.1 dB 0 0
20 Locked 256 QAM 31 615000000 Hz -4.9 dBmV 39.7 dB 0 0
21 Locked 256 QAM 32 621000000 Hz -4.9 dBmV 39.9 dB 0 0
22 Locked 256 QAM 33 627000000 Hz -4.9 dBmV 39.9 dB 0 0
23 Locked 256 QAM 34 633000000 Hz -5.1 dBmV 39.5 dB 0 0
24 Locked 256 QAM 35 639000000 Hz -5.2 dBmV 39.3 dB 1 0
25 Locked 256 QAM 36 645000000 Hz -5.6 dBmV 39 dB 1 0
26 Locked 256 QAM 37 651000000 Hz -6 dBmV 38.8 dB 1 0
27 Locked 256 QAM 38 657000000 Hz -6.8 dBmV 38.6 dB 1 0
28 Locked 256 QAM 39 663000000 Hz -7 dBmV 38.6 dB 0 0
29 Locked 256 QAM 40 669000000 Hz -6 dBmV 39 dB 1 0
30 Locked 256 QAM 42 681000000 Hz -5.8 dBmV 39.2 dB 0 0
31 Locked 256 QAM 43 687000000 Hz -5.7 dBmV 39.2 dB 0 0
32 Locked 256 QAM 44 693000000 Hz -5.5 dBmV 39.4 dB 2 0
Upstream Bonded Channels
Channel LockedStatus ChannelType ChannelID SymbolRate Frequency Power
1 Locked ATDMA 6 2560 Ksym/sec 40400000 Hz 44.5 dBmV
2 Locked ATDMA 2 5120 Ksym/sec 16400000 Hz 39.0 dBmV
3 Locked ATDMA 3 5120 Ksym/sec 22800000 Hz 39.5 dBmV
4 Locked ATDMA 4 5120 Ksym/sec 29200000 Hz 40.5 dBmV
5 Locked ATDMA 5 5120 Ksym/sec 35600000 Hz 41.0 dBmV
6 Not Locked Unknown 0 0 0 0.0
7 Not Locked Unknown 0 0 0 0.0
8 Not Locked Unknown 0 0 0 0.0
Downstream OFDM Channels
Channel LockedStatus ProfileID ChannelID Frequency Power SNR/MER ActiveSubcarrier Unerror Correctable Uncorrectable
1 Locked 0 ,1 ,2 ,3 159 702000000 Hz -4.32 dBmV 40.1 dB 1126 ~ 2969 21006897 1268354 0
2 Not Locked 0 0 0 Hz 0 dBmV 0 dB 0 ~ 4095 0 0 0
Upstream OFDMA Channels
Channel LockedStatus ProfileID ChannelID Frequency Power
1 Not Locked 0 0 0 Hz 0 dBmV
2 Not Locked 0 0 0 Hz 0 dBmV
Event Log
Time Priority Description
Tue Jun 21 05:49:31 2022 Notice DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=6c:cd:d6:69:6d:4c;CMTS-MAC=18:8b:9d:4a:3d:61;CM-QOS=1.1;CM-VER=3.1;
Tue Jun 21 05:49:24 2022 Notice TLV-11 - unrecognized OID;CM-MAC=6c:cd:d6:69:6d:4c;CMTS-MAC=18:8b:9d:4a:3d:61;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 1 00:01:15 1970 Notice Honoring MDD; IP provisioning mode = IPv6
Thu Jan 1 00:00:44 1970 Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=6c:cd:d6:69:6d:4c;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
Sat Jun 4 13:10:38 2022 Critical Resetting the cable modem due to docsDevResetNow
Thu May 26 06:46:52 2022 Critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=6c:cd:d6:69:6d:4c;CMTS-MAC=18:8b:9d:4a:3d:61;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 1 00:01:04 1970 Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=6c:cd:d6:69:6d:4c;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
Sat May 21 14:37:59 2022 Critical Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=6c:cd:d6:69:6d:4c;CMTS-MAC=18:8b:9d:4a:3d:61;CM-QOS=1.1;CM-VER=3.1;
Sat May 21 14:36:00 2022 Critical No Ranging Response received - T3 time-out;CM-MAC=6c:cd:d6:69:6d:4c;CMTS-MAC=18:8b:9d:4a:3d:61;CM-QOS=1.1;CM-VER=3.1;
Sat May 21 14:34:29 2022 Critical No Ranging Response received - T3 time-out;CM-MAC=6c:cd:d6:69:6d:4c;CMTS-MAC=18:8b:9d:4a:3d:61;CM-QOS=1.1;CM-VER=3.1;
Sat May 21 14:33:14 2022 Critical No Ranging Response received - T3 time-out;CM-MAC=6c:cd:d6:69:6d:4c;CMTS-MAC=18:8b:9d:4a:3d:61;CM-QOS=1.1;CM-VER=3.1;
Sat May 21 14:32:17 2022 Critical No Ranging Response received - T3 time-out;CM-MAC=6c:cd:d6:69:6d:4c;CMTS-MAC=18:8b:9d:4a:3d:61;CM-QOS=1.1;CM-VER=3.1;
Sat May 21 14:30:36 2022 Critical No Ranging Response received - T3 time-out;CM-MAC=6c:cd:d6:69:6d:4c;CMTS-MAC=18:8b:9d:4a:3d:61;CM-QOS=1.1;CM-VER=3.1;
Sat May 21 14:29:29 2022 Critical No Ranging Response received - T3 time-out;CM-MAC=6c:cd:d6:69:6d:4c;CMTS-MAC=18:8b:9d:4a:3d:61;CM-QOS=1.1;CM-VER=3.1;
Sat May 21 14:29:19 2022 Critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=6c:cd:d6:69:6d:4c;CMTS-MAC=18:8b:9d:4a:3d:61;CM-QOS=1.1;CM-VER=3.1;
Sat May 21 14:29:19 2022 Critical No Ranging Response received - T3 time-out;CM-MAC=6c:cd:d6:69:6d:4c;CMTS-MAC=18:8b:9d:4a:3d:61;CM-QOS=1.1;CM-VER=3.1;
Sat May 21 14:29:18 2022 Critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=6c:cd:d6:69:6d:4c;CMTS-MAC=18:8b:9d:4a:3d:61;CM-QOS=1.1;CM-VER=3.1;
Sat May 21 14:29:06 2022 Critical No Ranging Response received - T3 time-out;CM-MAC=6c:cd:d6:69:6d:4c;CMTS-MAC=18:8b:9d:4a:3d:61;CM-QOS=1.1;CM-VER=3.1;
Sat May 21 14:29:06 2022 Critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=6c:cd:d6:69:6d:4c;CMTS-MAC=18:8b:9d:4a:3d:61;CM-QOS=1.1;CM-VER=3.1;
Sat May 21 14:26:18 2022 Critical Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=6c:cd:d6:69:6d:4c;CMTS-MAC=18:8b:9d:4a:3d:61;CM-QOS=1.1;CM-VER=3.1;
Wed Apr 27 06:08:16 2022 Critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=6c:cd:d6:69:6d:4c;CMTS-MAC=18:8b:9d:4a:3d:61;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 1 00:00:44 1970 Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=6c:cd:d6:69:6d:4c;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
Tue Apr 5 18:58:24 2022 Critical Resetting the cable modem due to docsDevResetNow
Wed Mar 23 13:32:40 2022 Critical Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=6c:cd:d6:69:6d:4c;CMTS-MAC=18:8b:9d:4a:3d:61;CM-QOS=1.1;CM-VER=3.1;
Wed Mar 23 00:56:29 2022 Critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=6c:cd:d6:69:6d:4c;CMTS-MAC=18:8b:9d:4a:3d:61;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 1 00:00:44 1970 Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=6c:cd:d6:69:6d:4c;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
Wed Mar 23 00:41:27 2022 Critical Resetting the cable modem due to docsDevResetNow
Thu Mar 10 15:27:54 2022 Critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=6c:cd:d6:69:6d:4c;CMTS-MAC=18:8b:9d:4a:3d:61;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 1 00:00:44 1970 Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=6c:cd:d6:69:6d:4c;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
Wed Jan 19 18:04:41 2022 Critical Resetting the cable modem due to docsDevResetNow
Fri Jan 7 11:21:31 2022 Critical Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=6c:cd:d6:69:6d:4c;CMTS-MAC=18:8b:9d:4a:3d:61;CM-QOS=1.1;CM-VER=3.1;
Tue Dec 28 16:59:06 2021 Critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=6c:cd:d6:69:6d:4c;CMTS-MAC=18:8b:9d:4a:3d:61;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 1 00:00:44 1970 Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=6c:cd:d6:69:6d:4c;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
Tue Dec 28 14:25:52 2021 Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=6c:cd:d6:69:6d:4c;CMTS-MAC=18:8b:9d:4a:3d:61;CM-QOS=1.1;CM-VER=3.1;
Sun Dec 19 08:16:31 2021 Critical No Ranging Response received - T3 time-out;CM-MAC=6c:cd:d6:69:6d:4c;CMTS-MAC=18:8b:9d:4a:3d:61;CM-QOS=1.1;CM-VER=3.1;
Sun Dec 19 08:16:27 2021 Critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=6c:cd:d6:69:6d:4c;CMTS-MAC=18:8b:9d:4a:3d:61;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 1 00:00:44 1970 Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=6c:cd:d6:69:6d:4c;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
Sat Dec 18 11:43:13 2021 Critical Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=6c:cd:d6:69:6d:4c;CMTS-MAC=18:8b:9d:4a:3d:61;CM-QOS=1.1;CM-VER=3.1;
Sat Dec 18 11:43:11 2021 Critical Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=6c:cd:d6:69:6d:4c;CMTS-MAC=18:8b:9d:4a:3d:61;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 1 00:01:04 1970 Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=6c:cd:d6:69:6d:4c;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;- plemansJun 21, 2022Guru - Experienced User
Homeuser66 please start your own thread instead of jumping on someone elses. we try to separate them out so the OP's info doesn't get confused with other posters info.
- FURRYe38Jun 22, 2022Guru - Experienced User
I'd give the beta FW a try as well. I'm also planning on getting it installed though not sure when I'll be able to try it out.