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

Forum Discussion

timandmarilyn's avatar
timandmarilyn
Guide
Nov 07, 2023
Solved

C7000v2 Speed Issues

Hello, Recently we were told by our ISP (Spectrum) that our Internet speed has increased from 100MB to 300MB. Not only did this not happen, but our upload speeds are now nonexistent when connected v...
  • timandmarilyn's avatar
    timandmarilyn
    Nov 19, 2023

    Thanks FurryE38.

    Well I have an update! Spectrum came out and replaced the line due to errors they saw, but it didn't resolve my issue. HOWEVER, they tested with the ethernet cables I was using and verified upload speeds worked fine ... so it isolated my upload issue to the PC. After researching extensively further, I discovered that people have been complaining for months about the "Killer" ethernet software that a firmware update caused it to kill upload speeds :). There's literally a single switch in their control panel you can punch to fix it, which I did. So Netgear is off the hook officially on this one :).

     

    On the WiFi side, uploads have always been fine. The download speeds bumped up tonight after the improvements, but still not to 500mb ... its stuck at around 300-350. Well I was told by Spectrum that despite my device being able to handle 1.9GB, Spectrum only supports up to 400mb on that device, so that is tracking with what I'm seeing. I was only aiming for 300 in the first place anyway. Strangely, the PC that's physically connected is still well over 500mb regardless of what they say.

     

    So bottom line the mystery is solved ... partly a line issue, partly a software issue. Thank you for the help in thinking this through FurryE38!

timandmarilyn's avatar
timandmarilyn
Guide
Nov 08, 2023

Thank you very much for replying! I have not tried it in quite that exact sequence before so I will give that a shot to see what happens. To clarify, this is a gateway device so there isn't a separate cable modem, this is an all-in-one device. I may have to wait a day to do it but I'll reply here when I do with the results.

FURRYe38's avatar
FURRYe38
Guru - Experienced User
Nov 08, 2023

Yes. There is a built in modem though.

  • timandmarilyn's avatar
    timandmarilyn
    Guide
    Nov 14, 2023

    Hi FURRYe38, unfortunately that did not work. Specifically, I powered off the NetGear, shut down a PC and laptop, and turned off two phones. I actually disconnected all cables from the NetGear and waited five minutes. I reconnected all cables to the NetGear and let it fully boot, then turned on phones and laptops. Same results. To summarize again:

     

    • Download speeds top out at just over 100Mbps on all devices, wired and wireless, when it should now be increased to 300Mbps.
    • Upload speeds are 10Mbps on all devices (which is correct), except the PC that has a physical connection. For the PC, uploads don't work anymore - speed test shows as 0Mbps. If I disable the physical port and enable Wifi on the PC, uploads are 10Mbps.

    I have tried two different physical network cables, and I have tried two different ports on the NetGear with the same results.

     

    Any other recommendations? I'm planning to call Spectrum again as I'm on the latest approved firmware by them.

      • timandmarilyn's avatar
        timandmarilyn
        Guide
        Nov 15, 2023
        Thanks FURRYe38! We are on V1.02.09. ------------------------------------------------------- Cable Connection Log ------------------------------------------------------- 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 0 Startup Procedure Procedure Status Comment Acquire Downstream Channel 603000000 Hz Locked Connectivity State OK Operational Boot State OK Operational Security Enabled BPI+ IP Provisioning Mode Honor MDD honorMdd(4) Downstream Bonded Channels Channel Lock Status Modulation Channel ID Frequency Power SNR Correctables Uncorrectables 1 Locked QAM256 21 603000000 Hz -1.7 dBmV 37.9 dB 0 0 2 Locked QAM256 1 483000000 Hz -1.2 dBmV 38.7 dB 0 0 3 Locked QAM256 2 489000000 Hz -1.4 dBmV 38.5 dB 0 0 4 Locked QAM256 3 495000000 Hz -1 dBmV 38.8 dB 0 0 5 Locked QAM256 4 501000000 Hz -0.6 dBmV 39.1 dB 0 0 6 Locked QAM256 5 507000000 Hz -0.1 dBmV 38.5 dB 0 0 7 Locked QAM256 13 555000000 Hz -0.9 dBmV 38.7 dB 0 0 8 Locked QAM256 14 561000000 Hz -0.7 dBmV 38.3 dB 0 0 9 Locked QAM256 15 567000000 Hz -1.7 dBmV 38.3 dB 0 0 10 Locked QAM256 16 573000000 Hz -0.3 dBmV 39.1 dB 0 0 11 Locked QAM256 17 579000000 Hz -1.4 dBmV 38.3 dB 0 0 12 Locked QAM256 18 585000000 Hz -1.1 dBmV 38.4 dB 0 0 13 Locked QAM256 19 591000000 Hz -1.4 dBmV 38.3 dB 0 0 14 Locked QAM256 22 609000000 Hz -2.7 dBmV 37.3 dB 0 0 15 Locked QAM256 23 615000000 Hz -2.1 dBmV 37.6 dB 0 0 16 Locked QAM256 24 621000000 Hz -1.5 dBmV 38.1 dB 0 0 17 Locked QAM256 26 627000000 Hz -2.5 dBmV 37.5 dB 0 0 18 Locked QAM256 27 633000000 Hz -3.6 dBmV 36.7 dB 0 0 19 Locked QAM256 28 639000000 Hz -4 dBmV 36.5 dB 0 0 20 Locked QAM256 29 645000000 Hz -2 dBmV 38.2 dB 0 0 21 Locked QAM256 30 651000000 Hz -3.2 dBmV 37.1 dB 0 0 22 Locked QAM256 31 657000000 Hz -3.6 dBmV 36.8 dB 0 0 23 Locked QAM256 32 663000000 Hz -4.4 dBmV 36.2 dB 0 0 24 Locked QAM256 33 669000000 Hz -4.6 dBmV 35.9 dB 0 0 Upstream Bonded Channels Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power 1 Locked ATDMA 65 5120 Ksym/sec 17800000 Hz 40.8 dBmV 2 Locked ATDMA 68 5120 Ksym/sec 37000000 Hz 41.5 dBmV 3 Locked ATDMA 66 5120 Ksym/sec 24200000 Hz 41.5 dBmV 4 Locked ATDMA 67 5120 Ksym/sec 30600000 Hz 41.5 dBmV 5 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV 6 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV 7 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV 8 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV Current System Time:Tue Nov 14 21:26:33 2023 ------------------------------------------------------- Event Log ------------------------------------------------------- Time Priority Description 1970-1-1, 00:00:39 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=10:0c:6b:0b:f7:10;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=10:0c:6b:0b:f7:10;CMTS-MAC=00:01:5c:a1:6a:66;CM-QOS=1.0;CM-VER=3.0; 2023-10-6, 05:11:25 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=10:0c:6b:0b:f7:10;CMTS-MAC=00:01:5c:a1:6a:66;CM-QOS=1.1;CM-VER=3.0; 2023-10-6, 05:11:30 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=10:0c:6b:0b:f7:10;CMTS-MAC=00:01:5c:a1:6a:66;CM-QOS=1.1;CM-VER=3.0; 2023-10-6, 05:11:37 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=10:0c:6b:0b:f7:10;CMTS-MAC=00:01:5c:a1:6a:66;CM-QOS=1.1;CM-VER=3.0; 2023-10-6, 05:14:07 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=10:0c:6b:0b:f7:10;CMTS-MAC=00:01:5c:a1:6a:66;CM-QOS=1.1;CM-VER=3.0; 2023-10-6, 05:14:08 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=10:0c:6b:0b:f7:10;CMTS-MAC=00:01:5c:a1:6a:66;CM-QOS=1.1;CM-VER=3.0; 2023-10-6, 05:14:19 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=10:0c:6b:0b:f7:10;CMTS-MAC=00:01:5c:a1:6a:66;CM-QOS=1.1;CM-VER=3.0; 2023-10-6, 05:14:44 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=10:0c:6b:0b:f7:10;CMTS-MAC=00:01:5c:a1:6a:66;CM-QOS=1.1;CM-VER=3.0; 2023-10-6, 05:15:50 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=10:0c:6b:0b:f7:10;CMTS-MAC=00:01:5c:a1:6a:66;CM-QOS=1.0;CM-VER=3.0; 2023-10-6, 05:15:51 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:0c:6b:0b:f7:10;CMTS-MAC=00:01:5c:a1:6a:66;CM-QOS=1.0;CM-VER=3.0; 2023-10-6, 05:16:01 Critical (3) DHCP FAILED - Discover sent, no offer received;CM-MAC=10:0c:6b:0b:f7:10;CMTS-MAC=00:01:5c:a1:6a:66;CM-QOS=1.0;CM-VER=3.0; 2023-10-6, 05:19:10 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=10:0c:6b:0b:f7:10;CMTS-MAC=00:01:5c:a1:6a:66;CM-QOS=1.0;CM-VER=3.0; 2023-10-6, 05:19:17 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=10:0c:6b:0b:f7:10;CMTS-MAC=00:01:5c:a1:6a:66;CM-QOS=1.0;CM-VER=3.0; 2023-10-6, 05:19:27 Critical (3) DHCP FAILED - Discover sent, no offer received;CM-MAC=10:0c:6b:0b:f7:10;CMTS-MAC=00:01:5c:a1:6a:66;CM-QOS=1.0;CM-VER=3.0; 2023-10-6, 05:20:12 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:0c:6b:0b:f7:10;CMTS-MAC=00:01:5c:a1:6a:66;CM-QOS=1.0;CM-VER=3.0; 2023-10-6, 05:20:26 Critical (3) DHCP FAILED - Discover sent, no offer received;CM-MAC=10:0c:6b:0b:f7:10;CMTS-MAC=00:01:5c:a1:6a:66;CM-QOS=1.0;CM-VER=3.0; 2023-10-6, 05:22:38 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=10:0c:6b:0b:f7:10;CMTS-MAC=00:01:5c:a1:6a:66;CM-QOS=1.0;CM-VER=3.0; 2023-10-6, 05:22:45 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=10:0c:6b:0b:f7:10;CMTS-MAC=00:01:5c:a1:6a:66;CM-QOS=1.0;CM-VER=3.0; 2023-10-6, 05:22:55 Critical (3) DHCP FAILED - Discover sent, no offer received;CM-MAC=10:0c:6b:0b:f7:10;CMTS-MAC=00:01:5c:a1:6a:66;CM-QOS=1.0;CM-VER=3.0; 1970-1-1, 00:00:39 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=10:0c:6b:0b:f7:10;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; 2023-10-17, 15:10:28 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:0c:6b:0b:f7:10;CMTS-MAC=00:01:5c:a1:6a:66;CM-QOS=1.1;CM-VER=3.0; 2023-10-17, 15:18:42 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=10:0c:6b:0b:f7:10;CMTS-MAC=00:01:5c:a1:6a:66;CM-QOS=1.1;CM-VER=3.0; 2023-10-17, 15:19:12 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=10:0c:6b:0b:f7:10;CMTS-MAC=00:01:5c:a1:6a:66;CM-QOS=1.1;CM-VER=3.0; 2023-10-17, 15:19:37 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=10:0c:6b:0b:f7:10;CMTS-MAC=00:01:5c:a1:6a:66;CM-QOS=1.1;CM-VER=3.0; 2023-10-17, 16:41:05 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=10:0c:6b:0b:f7:10;CMTS-MAC=00:01:5c:a1:6a:66;CM-QOS=1.1;CM-VER=3.0; 2023-10-17, 16:41:24 Critical (3) SYNC Timing Synchronization failure - Failed to receive MAC SYNC frame within time-out period;CM-MAC=10:0c:6b:0b:f7:10;CMTS-MAC=00:01:5c:a1:6a:66;CM-QOS=1.1;CM-VER=3.0; 2023-10-17, 16:48:39 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=10:0c:6b:0b:f7:10;CMTS-MAC=00:01:5c:a1:6a:66;CM-QOS=1.1;CM-VER=3.0; 1970-1-1, 00:00:38 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=10:0c:6b:0b:f7:10;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; 2023-10-30, 22:13:03 Critical (3) Resetting the cable modem due to docsDevResetNow 1970-1-1, 00:00:39 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=10:0c:6b:0b:f7:10;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; 1970-1-1, 00:00:46 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=10:0c:6b:0b:f7:10;CMTS-MAC=00:01:5c:a1:6a:66;CM-QOS=1.0;CM-VER=3.0; 2023-10-30, 22:14:33 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=10:0c:6b:0b:f7:10;CMTS-MAC=00:01:5c:a1:6a:66;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=10:0c:6b:0b:f7:10;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; 1970-1-1, 00:00:40 Notice (6) WiFi Interface [wl0] set to Channel 11 (Side-Band Channel:N/A) - Reason:INIT 1970-1-1, 00:00:40 Notice (6) WiFi Interface [wl1] set to Channel 153 (Side-Band Channel:N/A) - Reason:INTERFERENCE 1970-1-1, 00:00:46 Notice (6) Honoring MDD; IP provisioning mode = APM 2023-11-13, 20:37:55 Error (4) Missing BP Configuration Setting TLV Type: 17.3;CM-MAC=10:0c:6b:0b:f7:10;CMTS-MAC=00:01:5c:a1:6a:66;CM-QOS=1.1;CM-VER=3.0; 2023-11-13, 20:37:55 Error (4) Missing BP Configuration Setting TLV Type: 17.8;CM-MAC=10:0c:6b:0b:f7:10;CMTS-MAC=00:01:5c:a1:6a:66;CM-QOS=1.1;CM-VER=3.0; 2023-11-13, 20:37:55 Error (4) Missing BP Configuration Setting TLV Type: 17.9;CM-MAC=10:0c:6b:0b:f7:10;CMTS-MAC=00:01:5c:a1:6a:66;CM-QOS=1.1;CM-VER=3.0; Help CenterSh