Re: C7000v2 Speed Issues

timandmarilyn · ‎2023-11-06

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 via a physical cable (upload speeds are fine via wifi, including on the same PC).

For context, we bought this in 2019 specifically to be future proofed for speed upgrades like this. The C7000v2 can handle well above even Spectrum's increase, yet it's not working. We are on firmware V1.02.09, the one supported by Spectrum (according to this: https://kb.netgear.com/000036375/What-is-the-latest-firmware-version-of-my-NETGEAR-cable-modem-or-mo...).

We've done the whole router / PC reboot thing a few times to no effect. I called Spectrum and after some testing they show the correct speed being pushed out. They say it's a Netgear issue. Any recommendations?

timandmarilyn · ‎2023-11-18

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!

View solution in original post

FURRYe38 · ‎2023-11-07

Has a power off for 1 minute then back ON with the ISP modem been performed?
Be sure to restart your network in this sequence:
Turn off and unplug modem.
Turn off router and computers.
Plug in and turn on modem. Wait 2 minutes for it to connect.
Turn on computers and rest of network.

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-m...
https://kb.netgear.com/30008/How-do-I-view-or-clear-the-event-logs-on-my-NETGEAR-cable-modem-or-mode...

timandmarilyn · ‎2023-11-07

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 · ‎2023-11-07

Yes. There is a built in modem though.

timandmarilyn · ‎2023-11-13

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.

FURRYe38 · ‎2023-11-14

What Firmware version is currently loaded?
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-m...
https://kb.netgear.com/30008/How-do-I-view-or-clear-the-event-logs-on-my-NETGEAR-cable-modem-or-mode...

timandmarilyn · ‎2023-11-14

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

FURRYe38 · ‎2023-11-14

Any Criticals, Errors or Warnings seen in the event logs needs to be reviewed and resolved by the ISP. Indicates a signal issue on the ISP line up to the modem.

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-Mod...
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
https://highspeed.tips/docsis-events/

timandmarilyn · ‎2023-11-15

Thank you FURRYe38! Super helpful. I'll contact Spectrum again tonight and see what they say.

FURRYe38 · ‎2023-11-16

Let us know how it goes.

timandmarilyn · ‎2023-11-16

Well...the plot thickens.

I talked to a Spectrum tech a few weeks ago who insisted they were pushing out the 300mb speed and that the issue had to be with NetGear. Tonight I talked to Spectrum and they ended up upgrading me to 500mb instead of 300mb (still no extra cost) and when they pushed out the change, it did increase my speed on the physically connected PC from 100mb to 500mb. So they had to have been doing something wrong previously.

However, all is still not well, of course :). They also bumped me from 10mb to 20mb uploads, but uploads on the physically connected PC still are at 0mb as of a few weeks ago, and this change didn't correct that issue.

Wifi increased from 100mb to 250-280mb but nowhere near 500mb, but the upload speed did indeed go from 10mb to 20mb. And of course the Spectrum tech says they are pushing out the correct speeds so it's an issue with Netgear :).

Any recommended next steps?

FURRYe38 · ‎2023-11-16

Id get a onsite tech visit and have them look at your modem and the line going up to the modem. Have them install one of there modems to test with to see if problem follows or not. Then you'll know. Maybe time to upgrade the C7000.

timandmarilyn · ‎2023-11-17

Thanks FURRYe38. I hope we don't have to replace it - that would be immensely frustrating as the whole point of buying it 4 years ago was future proofing. I would likely go with a different vendor based on this experience. Hopefully Spectrum can give us something here.

FURRYe38 · ‎2023-11-17

I highly recommend next time, of you do have to get something different, go with separate modem and external wifi router systems. So if something happens to the modem, you still have a router system you can connect up to a new modem should something happen. And you can have more control over the FW upates on the router system as well. C and CM series modems don't allow for user FW updates.

Good Luck.

timandmarilyn · ‎2023-11-18

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!

FURRYe38 · ‎2023-11-19

Glad ISP helped on there side.

Ya Killer adapters have been historically one cause of posters issues for those use them. Killer has there own QoS features that seems to either not work as intended or not work with other router systems that already have QoS features running. Usually disabling the Killer QoS features fixes it or getting into a non Killer adapter resolves.

Ya, depending on wifi device design and support and this model modem, you'll not see much over 300-500Mbps on 5Ghz AC. Just nature of the beast and limiation of working with 2x2 MIMO and 80Mhz channel width.

Glad you got it working. Please mark your thread as solved so others will know. Be sure to save off a back up configuration to file for safe keeping. Saves time if a reset is needed.
https://kb.netgear.com/24231/How-do-I-back-up-the-router-configuration-settings-on-my-Nighthawk-rout...
Enjoy. 📡

timandmarilyn · ‎2023-11-19

Thanks again Furrye38, and thanks again for this (and the earlier) helpful links!

FURRYe38 · ‎2023-11-19

👍🍻

swingtime · ‎2023-11-26

Tim and Marilyn: What is the "single switch in my control panel to fix slow speeds for a NetGear AC1900 C7000V2 Modem-Router? Thanks

"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 :)"

timandmarilyn · ‎2023-11-26

Hi swingtime! It is the "Prioritization Engine" - literally just turn it off and the issue is resolved. Well, sort of. Apparently the option turns itself back on after a reboot, so I've still got to figure that out. I've read that some people are just uninstalling the Killer dashboard and just using the base driver.

swingtime · ‎2023-11-28

What "single switch in the control panel did you punch? Thx.

"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 :)."

timandmarilyn · ‎2023-11-29

Hi swingtime! I actually answered your question- see the reply right above your most recent post.

swingtime · ‎2023-11-29

I do not see a "Prioritization Engine" switch of any sort on my netgear http://192.168.0.1/ dashboard page. Is the switch in my computer control panel? I have continued erratic and SLOW speeds via my C7000 modem-router the past few weeks.

I need level 101 help! Thanks

FURRYe38 · ‎2023-11-29

I believe this "Prioritization Engine" feature is located on the Killer adapter cards control settings. It won't be seen on the NG side of things. This is a feature of the Killer ethernet adapter card. Do you have this card?

swingtime · ‎2023-11-29

Thanks Furry 38. I do not have the Killer Ethernet Card. Only have the Netgear AC1900 C7000 Version 2 Cable Modem Router. ISP deliver speed showed down-speed of 250-300 mBS when the Spectrum Tech checked the line going to my C7000V2. Once he reconnected the line to my C7000V2 last night, I was getting 200+ mBS at my laptop and on a phone. 20 minutes later the down-speed signal strength down-speed dropped back to 1mBS. Figuring I need to replace my modem router. But may try a Toner Cable Co RPA42-Return Path Attenuator at the cable to modem-router connection if I can determine the correct dB level to order. There are 3, 6, 9, 12 & 15dB attenuators.