NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
CM3000 Not achieving high download speeds
I purchased the CM3000 a few weeks ago when my Comcast speeds were increased to 2000 Mbps. After 2 tech visits from Comcast my speeds from the modem do not exceed 800 or so Mbps even though they tested the line directly and the speeds are double that (1662 Mbps when tested today directly from the coaxial cable by the technician). I am using a CAT 8 cable and have tried all the trouble shooting I can find. Any suggestions on how to achieve the better speeds? Thank you.
9 Replies
What ethernet brand and model adapter do you have installed on your PC or laptop?
There a wifi router in between the modem and PC? Brand and model.
Be sure you have both ethernet adapter and a router that supports 2.5Gb or higher connection rate speeds on the ethernet ports, WAN and LAN ports for the router.
Speed test with a ethernet connected PC connected to the multi gig port on the CM modem with out the router connected.
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-routerCAT#A STP cabling is recommended.
I know my computer is older and doesn't support the highest speeds.
This is the ethernet adapter model I think: Realtek PCIe GBE Family Controller.
I am using the Google Nest Wifi Pro for my routers.
Cable Diagnostic Status: Good Action:
Your setup looks fine. If you can't access the internet, make sure you properly activated the modem. If modem has been activated and you still can't access the internet, contact your service provider for troubleshooting help.
If you can access the internet but has other internet issue, the Netgear Cable Knowledge Base can provide additional troubleshooting info.CM Status: Green Downstream Status: Green Upstream Status: Green Time Priority Description Fri Sep 13 12:57:04 2024 (Notice (6)) US profile assignment change. US Chan ID: 43; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=e0:46:ee:91:bb:c3;CMTS-MAC=00:90:f0:2e:00:00;CM-QOS=1.1;CM-VER=3.1; Fri Sep 13 12:52:04 2024 (Notice (6)) US profile assignment change. US Chan ID: 43; Previous Profile: 12 13; New Profile: 11 13.;CM-MAC=e0:46:ee:91:bb:c3;CMTS-MAC=00:90:f0:2e:00:00;CM-QOS=1.1;CM-VER=3.1; Fri Sep 13 12:01:08 2024 (Critical (3)) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=e0:46:ee:91:bb:c3;CMTS-MAC=00:90:f0:2e:00:00;CM-QOS=1.1;CM-VER=3.1; Fri Sep 13 11:51:17 2024 (Notice (6)) DS profile assignment change. DS Chan ID: 33; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=e0:46:ee:91:bb:c3;CMTS-MAC=00:90:f0:2e:00:00;CM-QOS=1.1;CM-VER=3.1; Fri Sep 13 11:51:16 2024 (Notice (6)) DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=e0:46:ee:91:bb:c3;CMTS-MAC=00:90:f0:2e:00:00;CM-QOS=1.1;CM-VER=3.1; Fri Sep 13 11:51:11 2024 (Notice (6)) TLV-11 - unrecognized OID;CM-MAC=e0:46:ee:91:bb:c3;CMTS-MAC=00:90:f0:2e:00:00;CM-QOS=1.1;CM-VER=3.1; Time Not Established (Notice (6)) Honoring MDD; IP provisioning mode = IPv6 Time Not Established (Critical (3)) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=e0:46:ee:91:bb:c3;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; Fri Sep 13 11:43:00 2024 (Critical (3)) Resetting the cable modem due to docsDevResetNow Time Not Established (Critical (3)) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=e0:46:ee:91:bb:c3;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; Fri Sep 13 03:01:35 2024 (Critical (3)) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=e0:46:ee:91:bb:c3;CMTS-MAC=00:90:f0:2e:00:00;CM-QOS=1.1;CM-VER=3.1; Thu Sep 12 15:47:11 2024 (Critical (3)) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=e0:46:ee:91:bb:c3;CMTS-MAC=00:90:f0:2e:00:00;CM-QOS=1.1;CM-VER=3.1; Wed Sep 11 03:01:32 2024 (Critical (3)) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=e0:46:ee:91:bb:c3;CMTS-MAC=00:90:f0:2e:00:00;CM-QOS=1.1;CM-VER=3.1; Tue Sep 10 12:20:51 2024 (Critical (3)) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=e0:46:ee:91:bb:c3;CMTS-MAC=00:90:f0:2e:00:00;CM-QOS=1.1;CM-VER=3.1; Time Not Established (Critical (3)) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=e0:46:ee:91:bb:c3;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; Fri Sep 06 06:39:34 2024 (Critical (3)) No Ranging Response received - T3 time-out;CM-MAC=e0:46:ee:91:bb:c3;CMTS-MAC=00:90:f0:2e:00:00;CM-QOS=1.1;CM-VER=3.1; Fri Sep 06 06:39:05 2024 (Critical (3)) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=e0:46:ee:91:bb:c3;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; Fri Sep 06 06:09:41 2024 (Critical (3)) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=e0:46:ee:91:bb:c3;CMTS-MAC=00:90:f0:2e:00:00;CM-QOS=1.1;CM-VER=3.1; Fri Sep 06 06:09:11 2024 (Critical (3)) No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=e0:46:ee:91:bb:c3;CMTS-MAC=00:90:f0:2e:00:00;CM-QOS=1.1;CM-VER=3.1; Fri Sep 06 06:09:01 2024 (Critical (3)) No Ranging Response received - T3 time-out;CM-MAC=e0:46:ee:91:bb:c3;CMTS-MAC=00:90:f0:2e:00:00;CM-QOS=1.1;CM-VER=3.1; Fri Sep 06 05:58:40 2024 (Critical (3)) Ranging Request Retries exhausted;CM-MAC=e0:46:ee:91:bb:c3;CMTS-MAC=00:90:f0:2e:00:00;CM-QOS=1.1;CM-VER=3.1; Fri Sep 06 05:58:40 2024 (Critical (3)) No Ranging Response received - T3 time-out;CM-MAC=e0:46:ee:91:bb:c3;CMTS-MAC=00:90:f0:2e:00:00;CM-QOS=1.1;CM-VER=3.1; Fri Sep 06 05:57:56 2024 (Critical (3)) No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=e0:46:ee:91:bb:c3;CMTS-MAC=00:90:f0:2e:00:00;CM-QOS=1.1;CM-VER=3.1; Fri Sep 06 05:57:46 2024 (Critical (3)) No Ranging Response received - T3 time-out;CM-MAC=e0:46:ee:91:bb:c3;CMTS-MAC=00:90:f0:2e:00:00;CM-QOS=1.1;CM-VER=3.1; Fri Sep 06 05:46:56 2024 (Critical (3)) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=e0:46:ee:91:bb:c3;CMTS-MAC=00:90:f0:2e:00:00;CM-QOS=1.1;CM-VER=3.1; Fri Sep 06 05:46:26 2024 (Critical (3)) No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=e0:46:ee:91:bb:c3;CMTS-MAC=00:90:f0:2e:00:00;CM-QOS=1.1;CM-VER=3.1; Fri Sep 06 05:46:16 2024 (Critical (3)) No Ranging Response received - T3 time-out;CM-MAC=e0:46:ee:91:bb:c3;CMTS-MAC=00:90:f0:2e:00:00;CM-QOS=1.1;CM-VER=3.1; Fri Sep 06 05:35:33 2024 (Critical (3)) No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=e0:46:ee:91:bb:c3;CMTS-MAC=00:90:f0:2e:00:00;CM-QOS=1.1;CM-VER=3.1; Fri Sep 06 05:35:23 2024 (Critical (3)) No Ranging Response received - T3 time-out;CM-MAC=e0:46:ee:91:bb:c3;CMTS-MAC=00:90:f0:2e:00:00;CM-QOS=1.1;CM-VER=3.1; Fri Sep 06 05:24:33 2024 (Critical (3)) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=e0:46:ee:91:bb:c3;CMTS-MAC=00:90:f0:2e:00:00;CM-QOS=1.1;CM-VER=3.1; Fri Sep 06 05:24:03 2024 (Critical (3)) No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=e0:46:ee:91:bb:c3;CMTS-MAC=00:90:f0:2e:00:00;CM-QOS=1.1;CM-VER=3.1; Fri Sep 06 05:23:53 2024 (Critical (3)) No Ranging Response received - T3 time-out;CM-MAC=e0:46:ee:91:bb:c3;CMTS-MAC=00:90:f0:2e:00:00;CM-QOS=1.1;CM-VER=3.1; Fri Sep 06 05:13:30 2024 (Critical (3)) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=e0:46:ee:91:bb:c3;CMTS-MAC=00:90:f0:2e:00:00;CM-QOS=1.1;CM-VER=3.1; Fri Sep 06 05:13:00 2024 (Critical (3)) No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=e0:46:ee:91:bb:c3;CMTS-MAC=00:90:f0:2e:00:00;CM-QOS=1.1;CM-VER=3.1; Fri Sep 06 05:12:50 2024 (Critical (3)) No Ranging Response received - T3 time-out;CM-MAC=e0:46:ee:91:bb:c3;CMTS-MAC=00:90:f0:2e:00:00;CM-QOS=1.1;CM-VER=3.1; Fri Sep 06 05:02:23 2024 (Critical (3)) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=e0:46:ee:91:bb:c3;CMTS-MAC=00:90:f0:2e:00:00;CM-QOS=1.1;CM-VER=3.1; Fri Sep 06 05:01:55 2024 (Critical (3)) No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=e0:46:ee:91:bb:c3;CMTS-MAC=00:90:f0:2e:00:00;CM-QOS=1.1;CM-VER=3.1; Fri Sep 06 05:01:43 2024 (Critical (3)) No Ranging Response received - T3 time-out;CM-MAC=e0:46:ee:91:bb:c3;CMTS-MAC=00:90:f0:2e:00:00;CM-QOS=1.1;CM-VER=3.1; Fri Sep 06 05:01:24 2024 (Critical (3)) SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=e0:46:ee:91:bb:c3;CMTS-MAC=00:90:f0:2e:00:00;CM-QOS=1.1;CM-VER=3.1; Fri Sep 06 05:01:24 2024 (Critical (3)) No Ranging Response received - T3 time-out;CM-MAC=e0:46:ee:91:bb:c3;CMTS-MAC=00:90:f0:2e:00:00;CM-QOS=1.1;CM-VER=3.1; If the ethernet adapter doesn't have 2.5Gbe, then thats only a 1Gb adapter. It will never much see past 900Mpbs.
If the WAN and LAN ports on the Google router system are the same 1Gb, then it won't pass thru anything much past 900Mpbs from the CM modem.
Can you post the cable connections data page with all the data down the page please.
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.
