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

Forum Discussion

keeve's avatar
keeve
Aspirant
Jun 25, 2023

CM1200 + R7000 speed issues

Hello all,

I am an Xfinity customer paying for a 1200 mbps plan.

Currently, i am getting somewhere between 20 and 50 mbps!

Here is the history:

A few weeks ago, an AT&T tech working on the neighbors yard cut my cable.

Technician came by and reconnected the cable. He tole me that CM700  Docsis 3.0 could not handle the speed i was paying for.

Suggested I get a 3.1. Hence I got the CM1200.

Was still not getting any speed improvement.

Today, a tech came by and checked the speed outside the house: 1900+ speed.

When directly connected to CM via ethernet, we go max 200 mbps.

He suggested I get a combo cm+router.

After that, I spent 2+ hours with a tech chat.....Issue still not identified.

I did learn how to login to the cm admin page and look at the cable connection page. Before I could send it to the chat, I lost connection.

Here are some screen shots from the page

Hardware Version1.01
 
Firmware VersionV3.12.03
 
Cable Modem Serial Number6YC2267CD0670
 
CM Certificate

Installed

 

Here is the downstreaminfo

Downstream Bonded Channels
Channel Lock Status Modulation Channel ID Frequency Power SNR Correctables Uncorrectables
1LockedQAM2565501000000 Hz-4.9 dBmV40.3 dB00
2LockedQAM2562483000000 Hz-4.5 dBmV41 dB00
3LockedQAM2563489000000 Hz-5.1 dBmV40.4 dB00
4LockedQAM2564495000000 Hz-5.2 dBmV40.4 dB00
5LockedQAM2566507000000 Hz-5.7 dBmV39.9 dB00
6LockedQAM2567513000000 Hz-5.9 dBmV39.9 dB00
7LockedQAM2568519000000 Hz-5.6 dBmV40.1 dB00
8LockedQAM2569525000000 Hz-6 dBmV39.8 dB00
9LockedQAM25610531000000 Hz-5.3 dBmV40.1 dB00
10LockedQAM25611537000000 Hz-4.7 dBmV40.5 dB00
11LockedQAM25612543000000 Hz-4.7 dBmV40.2 dB00
12LockedQAM25613555000000 Hz-4.6 dBmV40.3 dB00
13LockedQAM25614561000000 Hz-5.3 dBmV39.9 dB00
14LockedQAM25615567000000 Hz-5.7 dBmV39.6 dB00
15LockedQAM25616573000000 Hz-5.4 dBmV39.8 dB00
16LockedQAM25617579000000 Hz-5 dBmV39.9 dB00
17LockedQAM25618585000000 Hz-4.8 dBmV40 dB00
18LockedQAM25619591000000 Hz-4.6 dBmV40.1 dB00
19LockedQAM25620597000000 Hz-4.5 dBmV40 dB00
20LockedQAM25621603000000 Hz-4.5 dBmV39.8 dB00
21LockedQAM25622609000000 Hz-5 dBmV39.8 dB00
22LockedQAM25623615000000 Hz-5.4 dBmV39.6 dB00
23LockedQAM25624621000000 Hz-5.1 dBmV39.7 dB00
24LockedQAM25625627000000 Hz-5.3 dBmV39.6 dB00
25LockedQAM25626633000000 Hz-5.8 dBmV39.4 dB00
26LockedQAM25627639000000 Hz-5.7 dBmV39.4 dB00
27LockedQAM25628645000000 Hz-5.1 dBmV39.7 dB00
28LockedQAM25629651000000 Hz-5.4 dBmV39.6 dB00
29LockedQAM25630657000000 Hz-5.9 dBmV39.4 dB00
30LockedQAM25632663000000 Hz-6.1 dBmV39.3 dB00
31LockedQAM25633669000000 Hz-6.3 dBmV39 dB 

 

I am at a loss as to what to try next. Any help/suggestion  is appreciated.

The modem is less than 2 weeks old.

Thanks in advance.

 

 

8 Replies

  • Kitsap's avatar
    Kitsap
    Master
    Jun 25, 2023

    Help is available, however more information is needed.

     

    With a direct Ethernet connection between your CM1200 and a computer of some type you report 200 Mbps throughput.  You should see something around 940 Mbps due to the limit of a single 1 Gbps output port.

     

    What operating system is running on that computer?  Mac? Windows?  If Windows, what version?

     

    Are you sure the Ethernet cable is in good condition and at least a Cat 5e or better?  Look on the cable insulation.

     

    How are you measuring your throughput?  Web browser?  ISP test site?  Recommend you download and install the Ookla stand alone test application.  It eliminates web browsers and web sites from the test process.

     

    The power levels you show are low, near the low end of the specification.  Netgear modems specify power levels between +7 dBmV and -7 dBmV with ideal right at 0 or a little higher.  For reference:  https://kb.netgear.com/24311/Power-level-guidelines-for-a-NETGEAR-cable-modem-router

     

     

     

    • keeve's avatar
      keeve
      Aspirant
      Jun 25, 2023

      Thanks for your response

      With a direct Ethernet connection between your CM1200 and a computer of some type you report 200 Mbps throughput.  You should see something around 940 Mbps due to the limit of a single 1 Gbps output port. I agree

       

      What operating system is running on that computer?  Mac? Windows?  If Windows, what version?

      Windows 10

       

      Are you sure the Ethernet cable is in good condition and at least a Cat 5e or better?  Look on the cable insulation.

      The cable is one that came with the modem when I purchased it

       

      How are you measuring your throughput?  Web browser?  ISP test site?  Recommend you download and install the Ookla stand alone test application.  It eliminates web browsers and web sites from the test process.

      xfinity suggests speedtest.xfinity.com

      I also tried ookla (I will download it and try as you suggested)

       

      The power levels you show are low, near the low end of the specification.  Netgear modems specify power levels between +7 dBmV and -7 dBmV with ideal right at 0 or a little higher.  For reference:  https://kb.netgear.com/24311/Power-level-guidelines-for-a-NETGEAR-cable-modem-router

      Ok. I must say the coax cable in the house is as old as the house (40 years)

      I will look at your link. Who can adjust power levels?

      • Kitsap's avatar
        Kitsap
        Master
        Jun 25, 2023

        Recent Windows updates have incorporated some new default features relative to network profiles.  On your computer, go to Settings -> Network & Internet -> Status -> Ethernet Properties and make sure your network profile is set to private.  If it is public, Windows throws a bunch of firewall features in your way that can limit throughput.  A new modem is considered a new network by Windows and you might run in to the same thing again when you put your R7000 in play.  If it is set to public, change the profile, restart your computer, and repeat the throughput test direct connected to your modem.  Be sure your computer has a 1 Gbps Ethernet port and the Ethernet port drivers are up to date from your computer manufacturer.

         

        For your own satisfaction, look at the outside insulation on your Ethernet cable to ensure it is Cat 5e or Cat 6.  What did you find?

         

        Be sure you install the Ookla stand alone test application and do not use a web browser and a web address for throughput testing.

         

        Power levels are the responsibility of your ISP.  Depending on what plan you purchase, the ISP may consider their responsibility to end at the connection box at your house and not at the connection to your modem.  I recall Xfinity has an optional inside wiring add-on to your bill where they take responsibility for the wiring right up to the connection on your modem.  You should check before you find yourself being billed for inside wiring work.

         

        Do you have any coax splitters inside your house?  Each one in series can reduce your power levels by 3.5 dB or 7 dB.

         

        Regardless of when you bought it, the design of your R7000 is getting a little long in the tooth.  Even so, it should handle nominal 1 Gbps throughput at the Ethernet ports.  It will not be the same over Wi-Fi.  The R7000 is not on the official End of Service list from Netgear.

         

         

         

         

         

         

         

  • plemans's avatar
    plemans
    Guru - Experienced User
    Jun 26, 2023

    I'd focus first on getting the cm1200 to full gigabit speeds before moving on to troubleshooting the r7000. 

    Its a solid router but its a decade old and certain settings can cause slowdowns with it. 

    do you have a copy of the cm1200's logs? those help test longer term connection stats

    • keeve's avatar
      keeve
      Aspirant
      Jun 26, 2023

      I am primarily focused on the cm1200. 

      Here is what I found in the log.

       
       
       
       
      TimePriorityDescription
      Mon Jun 26 13:36:43 2023Notice (6)CM-STATUS message sent. Event Type Code: 24; Chan ID: 31; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=34:98:b5:ce:cf:99;CMTS-MAC=00:01:5c:a8:bc:49;CM-QOS=1.1;CM-VER=3.1;
      Mon Jun 26 13:34:15 2023Notice (6)CM-STATUS message sent. Event Type Code: 16; Chan ID: 31; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=34:98:b5:ce:cf:99;CMTS-MAC=00:01:5c:a8:bc:49;CM-QOS=1.1;CM-VER=3.1;
      Sun Jun 25 18:16:54 2023Notice (6)CM-STATUS message sent. Event Type Code: 5; Chan ID: 31; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=34:98:b5:ce:cf:99;CMTS-MAC=00:01:5c:a8:bc:49;CM-QOS=1.1;CM-VER=3.1;
      Sun Jun 25 18:16:40 2023Notice (6)DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=34:98:b5:ce:cf:99;CMTS-MAC=00:01:5c:a8:bc:49;CM-QOS=1.1;CM-VER=3.1;
      Sun Jun 25 18:16:35 2023Notice (6)TLV-11 - unrecognized OID;CM-MAC=34:98:b5:ce:cf:99;CMTS-MAC=00:01:5c:a8:bc:49;CM-QOS=1.1;CM-VER=3.1;
      Time Not EstablishedNotice (6)Honoring MDD; IP provisioning mode = IPv6
      Time Not EstablishedCritical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=34:98:b5:ce:cf:99;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
      Sun Jun 25 17:47:23 2023Notice (6)DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=34:98:b5:ce:cf:99;CMTS-MAC=00:01:5c:a8:bc:49;CM-QOS=1.1;CM-VER=3.1;
      Sun Jun 25 17:47:18 2023Notice (6)TLV-11 - unrecognized OID;CM-MAC=34:98:b5:ce:cf:99;CMTS-MAC=00:01:5c:a8:bc:49;CM-QOS=1.1;CM-VER=3.1;
      Time Not EstablishedNotice (6)Honoring MDD; IP provisioning mode = IPv6
      Time Not EstablishedCritical (3)No Ranging Response received - T3 time-out;CM-MAC=34:98:b5:ce:cf:99;CMTS-MAC=00:01:5c:a8:bc:49;CM-QOS=1.1;CM-VER=3.1;
      Time Not EstablishedCritical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=34:98:b5:ce:cf:99;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
      Sun Jun 25 16:37:15 2023Notice (6)CM-STATUS message sent. Event Type Code: 24; Chan ID: 31; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=34:98:b5:ce:cf:99;CMTS-MAC=00:01:5c:a8:bc:49;CM-QOS=1.1;CM-VER=3.1;
      Sun Jun 25 16:36:59 2023Notice (6)CM-STATUS message sent. Event Type Code: 22; Chan ID: 31; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=34:98:b5:ce:cf:99;CMTS-MAC=00:01:5c:a8:bc:49;CM-QOS=1.1;CM-VER=3.1;
      Sun Jun 25 16:34:36 2023Notice (6)CM-STATUS message sent. Event Type Code: 24; Chan ID: 31; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=34:98:b5:ce:cf:99;CMTS-MAC=00:01:5c:a8:bc:49;CM-QOS=1.1;CM-VER=3.1;
      Sun Jun 25 16:34:27 2023Notice (6)CM-STATUS message sent. Event Type Code: 20; Chan ID: 31; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=34:98:b5:ce:cf:99;CMTS-MAC=00:01:5c:a8:bc:49;CM-QOS=1.1;CM-VER=3.1;
      Sun Jun 25 16:34:02 2023Notice (6)CM-STATUS message sent. Event Type Code: 16; Chan ID: 31; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=34:98:b5:ce:cf:99;CMTS-MAC=00:01:5c:a8:bc:49;CM-QOS=1.1;CM-VER=3.1;
      Sun Jun 25 16:32:14 2023Notice (6)CM-STATUS message sent. Event Type Code: 22; Chan ID: 31; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=34:98:b5:ce:cf:99;CMTS-MAC=00:01:5c:a8:bc:49;CM-QOS=1.1;CM-VER=3.1;
      Sun Jun 25 16:29:15 2023Notice (6)CM-STATUS message sent. Event Type Code: 20; Chan ID: 31; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=34:98:b5:ce:cf:99;CMTS-MAC=00:01:5c:a8:bc:49;CM-QOS=1.1;CM-VER=3.1;
      Sun Jun 25 16:29:02 2023Notice (6)CM-STATUS message sent. Event Type Code: 16; Chan ID: 31; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=34:98:b5:ce:cf:99;CMTS-MAC=00:01:5c:a8:bc:49;CM-QOS=1.1;CM-VER=3.1;
      Sun Jun 25 16:28:54 2023Notice (6)CM-STATUS message sent. Event Type Code: 16; Chan ID: 31; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=34:98:b5:ce:cf:99;CMTS-MAC=00:01:5c:a8:bc:49;CM-QOS=1.1;CM-VER=3.1;
      Sun Jun 25 16:11:58 2023Notice (6)CM-STATUS message sent. Event Type Code: 5; Chan ID: 31; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=34:98:b5:ce:cf:99;CMTS-MAC=00:01:5c:a8:bc:49;CM-QOS=1.1;CM-VER=3.1;
      Sun Jun 25 16:11:46 2023Notice (6)DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=34:98:b5:ce:cf:99;CMTS-MAC=00:01:5c:a8:bc:49;CM-QOS=1.1;CM-VER=3.1;
      Sun Jun 25 16:11:41 2023Notice (6)TLV-11 - unrecognized OID;CM-MAC=34:98:b5:ce:cf:99;CMTS-MAC=00:01:5c:a8:bc:49;CM-QOS=1.1;CM-VER=3.1;
      Time Not EstablishedNotice (6)Honoring MDD; IP provisioning mode = IPv6
      Time Not EstablishedCritical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=34:98:b5:ce:cf:99;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
      Sun Jun 25 16:04:34 2023Notice (6)CM-STATUS message sent. Event Type Code: 24; Chan ID: 31; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=34:98:b5:ce:cf:99;CMTS-MAC=00:01:5c:a8:bc:49;CM-QOS=1.1;CM-VER=3.1;
      Sun Jun 25 16:04:30 2023Notice (6)CM-STATUS message sent. Event Type Code: 22; Chan ID: 31; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=34:98:b5:ce:cf:99;CMTS-MAC=00:01:5c:a8:bc:49;CM-QOS=1.1;CM-VER=3.1;
      Sun Jun 25 16:04:27 2023Notice (6)CM-STATUS message sent. Event Type Code: 24; Chan ID: 31; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=34:98:b5:ce:cf:99;CMTS-MAC=00:01:5c:a8:bc:49;CM-QOS=1.1;CM-VER=3.1;
      Sun Jun 25 16:04:03 2023Notice (6)CM-STATUS message sent. Event Type Code: 16; Chan ID: 31; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=34:98:b5:ce:cf:99;CMTS-MAC=00:01:5c:a8:bc:49;CM-QOS=1.1;CM-VER=3.1;
      Sun Jun 25 16:04:01 2023Notice (6)CM-STATUS message sent. Event Type Code: 20; Chan ID: 31; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=34:98:b5:ce:cf:99;CMTS-MAC=00:01:5c:a8:bc:49;CM-QOS=1.1;CM-VER=3.1;
      Sun Jun 25 16:04:00 2023Notice (6)CM-STATUS message sent. Event Type Code: 16; Chan ID: 31; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=34:98:b5:ce:cf:99;CMTS-MAC=00:01:5c:a8:bc:49;CM-QOS=1.1;CM-VER=3.1;
      Sun Jun 25 15:51:39 2023Notice (6)CM-STATUS message sent. Event Type Code: 5; Chan ID: 31; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=34:98:b5:ce:cf:99;CMTS-MAC=00:01:5c:a8:bc:49;CM-QOS=1.1;CM-VER=3.1;
      Sun Jun 25 15:51:27 2023Notice (6)DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=34:98:b5:ce:cf:99;CMTS-MAC=00:01:5c:a8:bc:49;CM-QOS=1.1;CM-VER=3.1;
      Sun Jun 25 15:51:22 2023Notice (6)TLV-11 - unrecognized OID;CM-MAC=34:98:b5:ce:cf:99;CMTS-MAC=00:01:5c:a8:bc:49;CM-QOS=1.1;CM-VER=3.1;
      Time Not EstablishedNotice (6)Honoring MDD; IP provisioning mode = IPv6
      Time Not EstablishedCritical (3)No Ranging Response received - T3 time-out;CM-MAC=34:98:b5:ce:cf:99;CMTS-MAC=00:01:5c:a8:bc:49;CM-QOS=1.1;CM-VER=3.1;
      Time Not EstablishedCritical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=34:98:b5:ce:cf:99;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
      Sun Jun 25 15:48:05 2023Notice (6)DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=34:98:b5:ce:cf:99;CMTS-MAC=00:01:5c:a8:bc:49;CM-QOS=1.1;CM-VER=3.1;
      Sun Jun 25 15:48:00 2023Notice (6)TLV-11 - unrecognized OID;CM-MAC=34:98:b5:ce:cf:99;CMTS-MAC=00:01:5c:a8:bc:49;CM-QOS=1.1;CM-VER=3.1;