NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.

Forum Discussion

jredmann's avatar
jredmann
Aspirant
Jul 27, 2021

Unable to reach 500Mbs using Netgear CM600 cable modem and R6400v2 router with WoW! internet

I upgraded my internet service with WoW! three days ago from 100Mbs to 500Mbs. I have not been able to get over a download speed of 120Mbs and upload speed of 24Mbs. They are unsure why this is happe...
jredmann's avatar
jredmann
Aspirant
Jul 27, 2021
Frequency start Value
This field below allows you to modify the frequency the cable modem start with its scan during initialization and registration. Enter the new start frequency and restart the cable modem for it to take effect.
Starting Frequency
 
Startup Procedure
ProcedureStatusComment
Acquire Downstream Channel603000000 HzLocked
Connectivity StateOKOperational
Boot StateOKOperational
SecurityEnableBPI+
IP Provisioning ModeHonor MDDIPv4 only
 
<tabindex=-1>Downstream Bonded Channels</tabindex=-1>
ChannelLock StatusModulationChannel IDFrequencyPowerSNRCorrectablesUncorrectables
1LockedQAM25619603000000 Hz-6.5 dBmV34.5 dB5270
2LockedQAM2561489000000 Hz-0.6 dBmV36.6 dB20414580
3LockedQAM2562495000000 Hz-0.4 dBmV34.3 dB22713
4LockedQAM2563501000000 Hz-0.7 dBmV36.3 dB1880
5LockedQAM2564507000000 Hz-0.7 dBmV37.9 dB1730
6LockedQAM2565513000000 Hz-0.1 dBmV39.0 dB1550
7LockedQAM2566519000000 Hz0.1 dBmV39.0 dB2140
8LockedQAM2567525000000 Hz-0.2 dBmV38.5 dB2220
9LockedQAM2568531000000 Hz-0.1 dBmV35.4 dB2340
10LockedQAM2569537000000 Hz-0.6 dBmV38.7 dB2270
11LockedQAM25610543000000 Hz-0.4 dBmV38.2 dB3930
12LockedQAM25611555000000 Hz-0.8 dBmV37.9 dB109686
13LockedQAM25612561000000 Hz-0.6 dBmV37.4 dB13990
14LockedQAM25614567000000 Hz-1.2 dBmV37.9 dB12590
15LockedQAM25613573000000 Hz-1.3 dBmV37.1 dB9420
16LockedQAM25615579000000 Hz-1.2 dBmV37.1 dB8810
17LockedQAM25616585000000 Hz-2.3 dBmV37.9 dB3430
18LockedQAM25617591000000 Hz-3.5 dBmV36.8 dB3580
19LockedQAM25618597000000 Hz-6.3 dBmV34.6 dB2770
20LockedQAM25620615000000 Hz-1.8 dBmV39.4 dB1144
21LockedQAM25622627000000 Hz-1.5 dBmV37.9 dB1217
22LockedQAM25623633000000 Hz-1.6 dBmV39.4 dB570
23LockedQAM25629669000000 Hz-1.5 dBmV39.9 dB150
24LockedQAM25631675000000 Hz-1.5 dBmV39.4 dB547850877309
 
<tabindex=-1>Upstream Bonded Channels</tabindex=-1>
ChannelLock StatusUS Channel TypeChannel IDSymbol RateFrequencyPower
1LockedATDMA15120 Ksym/sec21900000 Hz49.8 dBmV
2LockedATDMA25120 Ksym/sec28300000 Hz47.5 dBmV
3LockedATDMA35120 Ksym/sec34700000 Hz47.0 dBmV
4LockedATDMA42560 Ksym/sec39500000 Hz47.3 dBmV
 
Current System Time: Tue Jul 27 16:03:50 2021

 

 
plemans's avatar
plemans
Guru - Experienced User
Jul 28, 2021

Do you also have your logs? 

You don't have a lot of errors but your power is a bit out of spec. The channels should be within 3.5dbmv of each other. You're a bit out of that. 

if you have any splitters, amplifiers, or signal attenuators in line, remove them. 

Check the link for kinks, loose/old/bad/cheap/corroded connections and remove them if you do. 

  • jredmann's avatar
    jredmann
    Aspirant
    Jul 28, 2021

    plemans 

    TimePriorityDescription
    2021-07-27, 21:22:41Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:7f:b9:6a:ae:d8;CMTS-MAC=00:01:5c:b7:7e:49;CM-QOS=1.1;CM-VER=3.0;
    2021-07-27, 09:22:56Critical (3)Resetting the cable modem due to docsDevResetNow
    2021-07-25, 14:08:04Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:7f:b9:6a:ae:d8;CMTS-MAC=00:01:5c:b7:7e:49;CM-QOS=1.1;CM-VER=3.0;
    2021-07-25, 03:06:58Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:7f:b9:6a:ae:d8;CMTS-MAC=00:01:5c:b7:7e:49;CM-QOS=1.1;CM-VER=3.0;
    2021-07-24, 10:47:01Critical (3)Resetting the cable modem due to docsDevResetNow
    2021-07-24, 10:42:15Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:7f:b9:6a:ae:d8;CMTS-MAC=00:01:5c:b7:7e:49;CM-QOS=1.1;CM-VER=3.0;
    2021-07-22, 03:35:11Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:7f:b9:6a:ae:d8;CMTS-MAC=00:01:5c:b7:7e:49;CM-QOS=1.1;CM-VER=3.0;
    2021-07-21, 06:16:47Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:7f:b9:6a:ae:d8;CMTS-MAC=00:01:5c:b7:7e:49;CM-QOS=1.1;CM-VER=3.0;
    2021-07-16, 19:22:40Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:7f:b9:6a:ae:d8;CMTS-MAC=00:01:5c:b7:7e:49;CM-QOS=1.1;CM-VER=3.0;
    2021-06-09, 00:08:40Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:7f:b9:6a:ae:d8;CMTS-MAC=00:01:5c:b7:7e:49;CM-QOS=1.1;CM-VER=3.0;
    2021-06-09, 00:07:23Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=b0:7f:b9:6a:ae:d8;CMTS-MAC=00:01:5c:b7:7e:49;CM-QOS=1.1;CM-VER=3.0;
    2021-06-09, 00:04:30Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=b0:7f:b9:6a:ae:d8;CMTS-MAC=00:01:5c:b7:7e:49;CM-QOS=1.1;CM-VER=3.0;
    2021-06-08, 11:29:12Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:7f:b9:6a:ae:d8;CMTS-MAC=00:01:5c:b7:7e:49;CM-QOS=1.1;CM-VER=3.0;
    2021-06-05, 01:47:06Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:7f:b9:6a:ae:d8;CMTS-MAC=00:01:5c:b7:7e:49;CM-QOS=1.1;CM-VER=3.0;
    2021-06-03, 01:17:30Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:7f:b9:6a:ae:d8;CMTS-MAC=00:01:5c:b7:7e:49;CM-QOS=1.1;CM-VER=3.0;
    2021-05-30, 03:24:25Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:7f:b9:6a:ae:d8;CMTS-MAC=00:01:5c:b7:7e:49;CM-QOS=1.1;CM-VER=3.0;
    2021-05-28, 11:40:18Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:7f:b9:6a:ae:d8;CMTS-MAC=00:01:5c:b7:7e:49;CM-QOS=1.1;CM-VER=3.0;
    2021-05-25, 11:17:47Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:7f:b9:6a:ae:d8;CMTS-MAC=00:01:5c:b7:7e:49;CM-QOS=1.1;CM-VER=3.0;
    2021-05-25, 11:06:33Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:7f:b9:6a:ae:d8;CMTS-MAC=00:01:5c:b7:7e:49;CM-QOS=1.1;CM-VER=3.0;
    2021-05-19, 00:12:43Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:7f:b9:6a:ae:d8;CMTS-MAC=00:01:5c:b7:7e:49;CM-QOS=1.1;CM-VER=3.0;
    2021-05-19, 00:08:48Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=b0:7f:b9:6a:ae:d8;CMTS-MAC=00:01:5c:b7:7e:49;CM-QOS=1.1;CM-VER=3.0;
    2021-05-19, 00:08:44Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=b0:7f:b9:6a:ae:d8;CMTS-MAC=00:01:5c:b7:7e:49;CM-QOS=1.1;CM-VER=3.0;
    2021-04-28, 04:34:28Critical (3)Resetting the cable modem due to docsDevResetNow
    2021-04-26, 14:08:54Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:7f:b9:6a:ae:d8;CMTS-MAC=00:01:5c:b7:7e:49;CM-QOS=1.1;CM-VER=3.0;
    2021-04-21, 14:13:37Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:7f:b9:6a:ae:d8;CMTS-MAC=00:01:5c:b7:7e:49;CM-QOS=1.1;CM-VER=3.0;
    2021-03-15, 17:41:31Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:7f:b9:6a:ae:d8;CMTS-MAC=00:01:5c:b7:7e:49;CM-QOS=1.1;CM-VER=3.0;
    2021-03-11, 14:14:47Critical (3)No Ranging Response received - T3 time-out;CM-MAC=b0:7f:b9:6a:ae:d8;CMTS-MAC=00:01:5c:b7:7e:49;CM-QOS=1.0;CM-VER=3.0;
    2021-03-11, 14:14:25Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=b0:7f:b9:6a:ae:d8;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
    2021-03-11, 14:14:21Critical (3)No Ranging Response received - T3 time-out;CM-MAC=b0:7f:b9:6a:ae:d8;CMTS-MAC=00:01:5c:b7:7e:49;CM-QOS=1.0;CM-VER=3.0;
    2021-03-11, 14:13:54Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=b0:7f:b9:6a:ae:d8;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
    2021-03-11, 14:13:52Critical (3)SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=b0:7f:b9:6a:ae:d8;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
    2021-03-11, 14:13:50Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=b0:7f:b9:6a:ae:d8;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
    2021-03-11, 14:13:49Critical (3)SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=b0:7f:b9:6a:ae:d8;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
    Time Not EstablishedCritical (3)No Ranging Response received - T3 time-out;CM-MAC=b0:7f:b9:6a:ae:d8;CMTS-MAC=00:01:5c:b7:7e:49;CM-QOS=1.0;CM-VER=3.0;
    Time Not EstablishedWarning (5)DHCP WARNING - Non-critical field invalid in response ;CM-MAC=b0:7f:b9:6a:ae:d8;CMTS-MAC=00:01:5c:b7:7e:49;CM-QOS=1.0;CM-VER=3.0;
    Time Not EstablishedNotice (6)Honoring MDD; IP provisioning mode = IPv4
    Time Not EstablishedCritical (3)No Ranging Response received - T3 time-out;CM-MAC=b0:7f:b9:6a:ae:d8;CMTS-MAC=00:01:5c:b7:7e:49;CM-QOS=1.0;CM-VER=3.0;
    Time Not EstablishedCritical (3)No Ranging Response received - T3 time-out;CM-MAC=b0:7f:b9:6a:ae:d8;CMTS-MAC=00:01:5c:b7:7e:49;CM-QOS=1.0;CM-VER=3.0;
    Time Not EstablishedCritical (3)No Ranging Response received - T3 time-out;CM-MAC=b0:7f:b9:6a:ae:d8;CMTS-MAC=00:01:5c:b7:7e:49;CM-QOS=1.0;CM-VER=3.0;
    Time Not EstablishedCritical (3)No Ranging Response received - T3 time-out;CM-MAC=b0:7f:b9:6a:ae:d8;CMTS-MAC=00:01:5c:b7:7e:49;CM-QOS=1.0;CM-VER=3.0;
  • FURRYe38's avatar
    FURRYe38
    Guru - Experienced User
    Jul 28, 2021

    You can try a new modem for sure and see if these are seen on the new modem. If they are then the ISP needs to review there service line and signals UP to the modem. If the problem is not seen on the new modem then the CM600 could be faulty. 

  • jredmann's avatar
    jredmann
    Aspirant
    Jul 28, 2021

    Okay, I've had this modem for a few years, probably close to 4 or 5 years. So it would not suprise me if it was going out.

  • FURRYe38's avatar
    FURRYe38
    Guru - Experienced User
    Jul 28, 2021

    Try another CM modem. CM1000, 1100, 1200 or 2000. See what one of these reports.

  • plemans's avatar
    plemans
    Guru - Experienced User
    Jul 28, 2021

    I'd also check the line carefully. Move the modem to right where the coax enters the home to prevent wiring in the home being the issue. 

    The docsresets are issued from the cmts usually. And t3 tends to indicate line issues. 

    not saying somethings not wrong with the modem but those errors tend to be line issues