NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
CM1000
16 TopicsCM1000 Xfinity issues
I am quite frustrated at this point. I had a CM600 modem to support Comcast's Extreme 150 service. I've had it for a few years and was consistently getting 160 to 170mbps speed from it. About three weeks ago, I noticed a drop off and did a speed test and could not get more than 50mbps. Comcast reset the modem (I did the same thing). No change. They sent a tech out to the house and he swapped out my modem for one of theirs and lo and behold, 170mbps. He said I needed a new modem. I was a little suspicious of this, but wanting to eventually get gigabit service when it becomes available, I bought a CM1000. It provisioned fine, but I am seeing the same behavior. At the start of the speed test it spikes to over 100 but eventually averages out to 70 or 80. They came out again and re-trenched a new thicker line between the street and the house. Still the same behavior. The tech came out again today and installed a dedicated line directly from the outside box to the modem. Still the same behavior. The logs from the Modem are consistently showing: Time Priority Description 2017-12-03, 10:41:31 Notice (6) CM-STATUS message sent. Event Type Code: 4; Chan ID: 21 22 ; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=b0:39:56:4b:b8:68;CMTS-MAC=00:01:5c:a7:12:4e;CM-QOS=1.1;CM-VER=3.1; 2017-12-03, 10:41:17 Warning (5) MDD message timeout;CM-MAC=b0:39:56:4b:b8:68;CMTS-MAC=00:01:5c:a7:12:4e;CM-QOS=1.1;CM-VER=3.1; The Cable Connection page displays the following. Any thoughts on this issue? 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 <tabindex=-1>Startup Procedure Procedure Status Comment Acquire Downstream Channel 555000000 Hz Locked Connectivity State OK Operational Boot State OK Operational Security Enable BPI+ IP Provisioning Mode Honor MDD IPv6 only <tabindex=-1>Downstream Bonded Channels Channel Lock Status Modulation Channel ID Frequency Power SNR / MER Unerrored Codewords Correctable Codewords Uncorrectable Codewords 1 Locked QAM256 20 555000000 Hz 2.8 dBmV 36.8 dB 158493311 546 0 2 Locked QAM256 1 423000000 Hz 5.4 dBmV 38.7 dB 157105990 36 0 3 Locked QAM256 2 429000000 Hz 5.6 dBmV 38.9 dB 157114932 13 0 4 Locked QAM256 3 435000000 Hz 5.6 dBmV 39.0 dB 157125743 17 0 5 Locked QAM256 4 441000000 Hz 5.1 dBmV 38.7 dB 157134245 29 0 6 Locked QAM256 5 453000000 Hz 4.2 dBmV 38.5 dB 157143868 60 0 7 Locked QAM256 6 459000000 Hz 3.8 dBmV 38.3 dB 157153008 71 0 8 Locked QAM256 7 465000000 Hz 3.5 dBmV 38.3 dB 157162210 62 0 9 Locked QAM256 8 471000000 Hz 3.2 dBmV 38.2 dB 157171891 72 0 10 Locked QAM256 9 477000000 Hz 2.7 dBmV 38.0 dB 157181040 59 0 11 Locked QAM256 10 483000000 Hz 2.2 dBmV 37.5 dB 157190267 74 0 12 Locked QAM256 11 489000000 Hz 2.0 dBmV 37.4 dB 157199468 75 0 13 Locked QAM256 12 495000000 Hz 1.9 dBmV 37.4 dB 157208618 80 0 14 Locked QAM256 13 507000000 Hz 1.7 dBmV 37.3 dB 157218872 61 0 15 Locked QAM256 14 513000000 Hz 1.6 dBmV 37.3 dB 157227558 70 0 16 Locked QAM256 15 519000000 Hz 1.4 dBmV 37.3 dB 157237136 95 0 17 Locked QAM256 16 525000000 Hz 1.1 dBmV 37.1 dB 157246947 121 0 18 Locked QAM256 17 531000000 Hz 1.3 dBmV 37.4 dB 157255633 105 0 19 Locked QAM256 18 537000000 Hz 1.3 dBmV 37.1 dB 157264694 132 0 20 Locked QAM256 19 543000000 Hz 1.6 dBmV 37.1 dB 157275272 112 0 21 Locked QAM256 21 561000000 Hz 2.9 dBmV 32.3 dB 147085863 2537135 7646772 22 Locked QAM256 22 567000000 Hz 3.6 dBmV 27.2 dB 135579752 4471561 17201032 23 Locked QAM256 23 573000000 Hz 3.7 dBmV 35.5 dB 152906954 3458380 927827 24 Locked QAM256 24 579000000 Hz 3.1 dBmV 34.7 dB 157299415 177 0 25 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0 0 26 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0 0 27 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0 0 28 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0 0 29 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0 0 30 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0 0 31 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0 0 32 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0 0 <tabindex=-1>Upstream Bonded Channels Channel Lock Status Modulation Channel ID Frequency Power 1 Locked ATDMA 1 35600000 Hz 35.8 dBmV 2 Locked ATDMA 2 29200000 Hz 35.8 dBmV 3 Locked ATDMA 3 22800000 Hz 34.0 dBmV 4 Not Locked Unknown 0 0 Hz 0.0 dBmV 5 Not Locked Unknown 0 0 Hz 0.0 dBmV 6 Not Locked Unknown 0 0 Hz 0.0 dBmV 7 Not Locked Unknown 0 0 Hz 0.0 dBmV 8 Not Locked Unknown 0 0 Hz 0.0 dBmV <tabindex=-1>Downstream OFDM Channels Channel Lock Status Modulation / Profile ID Channel ID Frequency Power SNR / MER Active Subcarrier Number Range Unerrored Codewords Correctable Codewords Uncorrectable Codewords 1 Locked 0, 1 25 372000000 Hz 7.6 dBmV 38.3 dB 1108 ~ 2987 4381967 35743 0 2 Not Locked 0 0 0 Hz 7.2 dBmV 0.0 dB 0 ~ 4095 0 0 0 <tabindex=-1>Upstream OFDMA Channels Channel Lock Status Modulation / Profile ID Channel ID Frequency Power 1 Not Locked Unknown 0 0 Hz 0 dBmV 2 Not Locked Unknown 0 0 Hz 0 dBmV Any help or guidance I can give Xfinity would be greatly appreciated. I really want to own my own equipment and not pay $10 a month for their stuff. Warm regards, JoeSolved78KViews0likes78CommentsCM1000 requiring rebooting several times a day (Comcast)
I recently purchased a Netgear CM1000 for use on Comcast and several times a day the internet just stops working despite all lights still showing green. When this happens I can't even log into the web management app. Turning the modem off and back on removes the problem, but this is really annoying to have to do multiple times a day! Any advice is welcomed. Here are some pertinent pieces of information: Hardware Version 2.02 Firmware Version V2.01.14 Acquire Downstream Channel 639000000 Hz Locked Connectivity State OK Operational Boot State OK Operational Security Enable BPI+ IP Provisioning Mode Honor MDD IPv6 only Downstream Bonded Channels Channel Lock Status Modulation Channel ID Frequency Power SNR Correctables Uncorrectables 1 Locked QAM256 17 639000000 Hz -1.7 dBmV 39.1 dB 1 0 2 Locked QAM256 1 543000000 Hz -1.3 dBmV 40.1 dB 0 0 3 Locked QAM256 2 549000000 Hz -1.2 dBmV 40.1 dB 2 0 4 Locked QAM256 3 555000000 Hz -1.3 dBmV 40.0 dB 1 0 5 Locked QAM256 4 561000000 Hz -1.4 dBmV 39.9 dB 2 0 6 Locked QAM256 5 567000000 Hz -1.3 dBmV 40.0 dB 0 0 7 Locked QAM256 6 573000000 Hz -1.5 dBmV 39.9 dB 3 0 8 Locked QAM256 7 579000000 Hz -1.4 dBmV 39.7 dB 2 0 9 Locked QAM256 8 585000000 Hz -1.5 dBmV 39.7 dB 2 0 10 Locked QAM256 9 591000000 Hz -1.5 dBmV 39.7 dB 4 0 11 Locked QAM256 10 597000000 Hz -1.7 dBmV 39.6 dB 7 0 12 Locked QAM256 11 603000000 Hz -2.0 dBmV 39.3 dB 3 0 13 Locked QAM256 12 609000000 Hz -2.5 dBmV 39.3 dB 5 0 14 Locked QAM256 13 615000000 Hz -2.0 dBmV 39.3 dB 6 0 15 Locked QAM256 14 621000000 Hz -1.7 dBmV 39.3 dB 4 0 16 Locked QAM256 15 627000000 Hz -1.7 dBmV 39.2 dB 2 0 17 Locked QAM256 16 633000000 Hz -1.7 dBmV 39.3 dB 1 0 18 Locked QAM256 18 645000000 Hz -1.8 dBmV 39.3 dB 2 0 19 Locked QAM256 19 651000000 Hz -1.7 dBmV 39.1 dB 3 0 20 Locked QAM256 20 657000000 Hz -1.7 dBmV 39.2 dB 3 0 21 Locked QAM256 21 663000000 Hz -1.6 dBmV 39.1 dB 3 0 22 Locked QAM256 22 669000000 Hz -1.6 dBmV 39.1 dB 1 0 23 Locked QAM256 23 675000000 Hz -1.5 dBmV 39.1 dB 0 0 24 Locked QAM256 24 681000000 Hz -1.5 dBmV 39.0 dB 0 0 ... Upstream Bonded Channels Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power 1 Locked ATDMA 1 5120 Ksym/sec 30100000 Hz 45.5 dBmV 2 Locked ATDMA 2 5120 Ksym/sec 36500000 Hz 45.5 dBmV 3 Locked ATDMA 3 5120 Ksym/sec 17300000 Hz 43.5 dBmV 4 Locked ATDMA 4 5120 Ksym/sec 23700000 Hz 45.5 dBmV ... Time Priority Description 2017-01-22, 21:03:53 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;CM-QOS=1.1;CM-VER=3.1; 2017-01-22, 21:03:58 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;CM-QOS=1.1;CM-VER=3.1; 2017-01-22, 21:04:05 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;CM-QOS=1.1;CM-VER=3.1; 2017-01-22, 21:04:49 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;CM-QOS=1.1;CM-VER=3.1; 2017-01-22, 21:04:49 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;CM-QOS=1.1;CM-VER=3.1; 2017-01-22, 21:05:09 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;CM-QOS=1.1;CM-VER=3.1; 2017-01-22, 21:05:10 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;CM-QOS=1.1;CM-VER=3.1; 2017-01-22, 21:05:28 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;CM-QOS=1.1;CM-VER=3.1; 2017-01-22, 21:05:29 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;CM-QOS=1.1;CM-VER=3.1; 2017-01-22, 21:05:48 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;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=a0:04:60:fc:8d:a0;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; Time Not Established Critical (3) No Ranging Response received - T3 time-out;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;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=a0:04:60:fc:8d:a0;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; 2017-01-24, 19:26:40 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;CM-QOS=1.1;CM-VER=3.1; 2017-01-24, 21:01:18 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;CM-QOS=1.1;CM-VER=3.1; 2017-01-24, 21:01:21 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;CM-QOS=1.1;CM-VER=3.1; 2017-01-24, 21:01:27 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;CM-QOS=1.1;CM-VER=3.1; 2017-01-24, 21:02:09 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;CM-QOS=1.1;CM-VER=3.1; 2017-01-24, 21:02:09 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;CM-QOS=1.1;CM-VER=3.1; 2017-01-24, 21:02:29 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;CM-QOS=1.1;CM-VER=3.1; 2017-01-24, 21:02:30 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;CM-QOS=1.1;CM-VER=3.1; 2017-01-24, 21:02:49 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;CM-QOS=1.1;CM-VER=3.1; 2017-01-24, 21:02:50 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;CM-QOS=1.1;CM-VER=3.1; 2017-01-24, 21:03:09 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;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=a0:04:60:fc:8d:a0;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; 2017-01-24, 22:53:14 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;CM-QOS=1.1;CM-VER=3.1; 2017-01-24, 23:00:30 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;CM-QOS=1.1;CM-VER=3.1; 2017-01-24, 23:00:35 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;CM-QOS=1.1;CM-VER=3.1; 2017-01-24, 23:00:41 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;CM-QOS=1.1;CM-VER=3.1; 2017-01-24, 23:01:11 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;CM-QOS=1.1;CM-VER=3.1; 2017-01-24, 23:01:12 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;CM-QOS=1.1;CM-VER=3.1; 2017-01-24, 23:01:32 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;CM-QOS=1.1;CM-VER=3.1; 2017-01-24, 23:01:32 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;CM-QOS=1.1;CM-VER=3.1; 2017-01-24, 23:01:53 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;CM-QOS=1.1;CM-VER=3.1; 2017-01-24, 23:01:54 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;CM-QOS=1.1;CM-VER=3.1; 2017-01-24, 23:02:12 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;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=a0:04:60:fc:8d:a0;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; Time Not Established Critical (3) No Ranging Response received - T3 time-out;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;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=a0:04:60:fc:8d:a0;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; Time Not Established Notice (6) Honoring MDD; IP provisioning mode = IPv6 This event log comes shortly after I had to restart my modem for the second time in the last 2 hours!Solved35KViews0likes66CommentsCM1000 needs regular rebooting; upgrade RCN to v2.01.15?
My CM1000 with firmware v2.01.14 randomly stops working about every other day. Symptoms: Unable to ping my ISP Upstream LED: blinking Downstream LED: off Internet LED: off If I turn it off and back on then it will start working again. From this thread it seems like a known issue that is solved by upgrading the firmware to v2.01.15. However, I can't upgrade the firmware myself—my ISP (RCN) has to do it for me. I called their technical support and they seem clueless. In the other thread Netgear representatives worked directly with Comcast and Cox to get the firmware updated. Can someone from Netgear please contact RCN and get them to upgrade the CM1000 firmware to v2.01.15 (or newer)? Details from the Cable Connection page: Startup Procedure Procedure Status Comment Acquire Downstream Channel 621000000 Hz Locked Connectivity State OK Operational Boot State OK Operational Security Enable BPI+ IP Provisioning Mode Honor MDD IPv4 only Downstream Bonded Channels Channel Lock Status Modulation Channel ID Frequency Power SNR Correctables Uncorrectables 1 Locked QAM256 15 621000000 Hz -5.5 dBmV 40.7 dB 78 0 2 Locked QAM256 1 537000000 Hz -7.9 dBmV 39.8 dB 84 30 3 Locked QAM256 2 543000000 Hz -7.1 dBmV 40.2 dB 73 24 4 Locked QAM256 3 549000000 Hz -6.5 dBmV 40.5 dB 94 7 5 Locked QAM256 4 555000000 Hz -6.0 dBmV 40.7 dB 86 0 6 Locked QAM256 5 561000000 Hz -5.6 dBmV 41.0 dB 99 0 7 Locked QAM256 6 567000000 Hz -5.2 dBmV 40.9 dB 1693 488 8 Locked QAM256 7 573000000 Hz -5.1 dBmV 40.8 dB 108 0 9 Locked QAM256 8 579000000 Hz -5.3 dBmV 40.9 dB 89 0 10 Locked QAM256 9 585000000 Hz -5.1 dBmV 41.2 dB 80 0 11 Locked QAM256 10 591000000 Hz -5.4 dBmV 40.9 dB 80 25 12 Locked QAM256 11 597000000 Hz -5.3 dBmV 40.6 dB 88 0 13 Locked QAM256 12 603000000 Hz -5.2 dBmV 40.6 dB 57 0 14 Locked QAM256 13 609000000 Hz -5.5 dBmV 40.6 dB 79 0 15 Locked QAM256 14 615000000 Hz -5.2 dBmV 40.9 dB 73 0 16 Locked QAM256 16 627000000 Hz -5.8 dBmV 40.5 dB 66 0 17 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0 18 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0 19 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0 20 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0 21 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0 22 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0 23 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0 24 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0 25 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0 26 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0 27 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0 28 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0 29 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0 30 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0 31 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0 32 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0 Upstream Bonded Channels Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power 1 Locked ATDMA 1 5120 Ksym/sec 32996000 Hz 40.5 dBmV 2 Locked ATDMA 2 5120 Ksym/sec 25396000 Hz 40.5 dBmV 3 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV 4 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 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 Downstream OFDM Channels Channel Channel ID Indicator Subcarrier Zero Frequency Active Subcarrier Number Range Total Codewords Uncorrectable Codewords 1 159 Non-Primary 599600000 Hz 646 ~ 3449 0 0 2 0 Non-Primary 0 Hz 0 ~ 4095 0 0 Upstream OFDMA Channels Channel UpstreamIsMuted Ranging Status Subcarrier Zero Frequency Active Subcarrier Number Range Symbols Per Frame Tx Power 1 Other 0 Hz 0 ~ 0 0 0 dBmV 2 Other 0 Hz 0 ~ 0 0 0 dBmV From the Event Log: 2017-06-25, 17:09:13 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=b0:b9:8a:xx:xx:xx;CMTS-MAC=00:ca:e5:yy:yy:yy;CM-QOS=1.1;CM-VER=3.1; 2017-06-25, 17:09:18 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=b0:b9:8a:xx:xx:xx;CMTS-MAC=00:ca:e5:yy:yy:yy;CM-QOS=1.1;CM-VER=3.1; 2017-06-25, 17:09:42 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:b9:8a:xx:xx:xx;CMTS-MAC=00:ca:e5:yy:yy:yy;CM-QOS=1.1;CM-VER=3.1; 2017-06-25, 17:09:42 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=b0:b9:8a:xx:xx:xx;CMTS-MAC=00:ca:e5:yy:yy:yy;CM-QOS=1.1;CM-VER=3.1; 2017-06-25, 17:10:02 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:b9:8a:xx:xx:xx;CMTS-MAC=00:ca:e5:yy:yy:yy;CM-QOS=1.1;CM-VER=3.1;Solved17KViews0likes11CommentsNetgear R7000 isn't up to speed on a gigabit connection through CM1000 modem
Hi, I recently got a Netgear CM1000 modem on my gigabit Xfinity connection. When I hook my laptop up to the modem directly I am getting close to a gigabit connection, at least above 900 Mbps consistently. But when I hook up (ethernet) through my R7000 with fully upgraded stock firmware I'm still just getting around 200 Mbps which is the speed I used to have before my connection was upgraded. What could the reason be for me not getting any speed increase when connecting through the router? As far as I can see the the router should be able to handle the speed.Solved16KViews0likes5CommentsNot getting correct speed with Comcast
Hello all In November I saw that Comcast offered a higher tier internet service in my neighborhood. Speeds are advertised up to 986 Mbps. Since I signed up I’ve only seen 350-400 Mbps. I had a couple of online chats and phone calls with Comcast. I also had two techs come to the house to check the signal to the house. The second tech said that Comcast had to approve new firmware for my CM1000 modem (this was in December). He said that once Comcast approved the firmware then Netgear would push the upgrade to my modem directly. I called to try to get credit for billing since I wasn’t getting the correct speeds and I was forced to chat with Comcast tech support again. The tech sent me a link to the Nighthawk X6 router firmware page to update my CM1000 cable modem :| When I told them it was the wrong equipment they told me to contact Netgear directly to receive my firmware update. I sent this link to him. https://www.netgear.com/support/product/CM1000#download It says “Current Versions Firmware upgrades are pushed down by your ISP. For more information, please see our Knowledge Base .” He just told me to talk to Netgear :| Has anyone had any success getting advertised speeds with Comcast Gigabit Internet? Thanks for your time13KViews0likes6CommentsXR500 and cm1000
Hey all I just bought the xr500 its pretty cool so far ,But i am having a slight hicup . If i restart my cm1000 the light on the xr500 goes amber even when the modem gets full back up it stays amber . I am wondering if maybe I got a bad xr500 or if its a glitch When i got the webpage for the modem It will not detect my modem till I unplug the router and power it back up.Solved8.4KViews0likes19Commentsconnecting NETGEAR CM1000 to Cisco DPC3825 modem/router but use DPC3825 as router
OK where to begin? My ISP is cox cable my new cable modem: Netgear CM1000 old cable modem/router: Cisco DPC3825 i recently set up my new NETGEAR CM1000 with them. it works fine and all but i dont have a router yet since im saving up for the X10. I bought the Cisco DPC3825 modem/router from Cox 3 years ago. The router would lose signal constantly, but regardless, i at least had a wireless network. So seeing as the DPC3825 is my only router at the moment, i would like to ask for anyones help on setting up the CM1000 to work with the DPC3825 and hopefully i can broadcast a wireless network without connecting the coaxial to the router. I know that the 3825 does not compare to any newer router but its all i have for the time being. i just want to connect the one ethernet cable from the CM1000 to the 3825 and run a wireless and also be able have a wan network. The only devices i ever have a wired connection into the router are ps3, ps4, and my laptop. i have 4 phones and 2 tablets. I read all about bridged mode but that option has been removed by a firmware update. at first i thought it was but i dont need the 3825 to run only as a modem. i just need it to run like a router would. I have tried to connect the modem to the router already but i get no internet connection. maybe its just not compatible. PLEASE END MY MISERY and please help so that someone who might have the same problem can read this and help them in the future. i have read countless pages but i cant find a way to have a successful wired connection from modem to router to laptop. and essentialy to ps4.3.8KViews0likes1CommentSuggestions for future CM1000 mods & upgrades
Love my new CM1000, here are some follow on product suggestions • Xfinity will be rolling out their 2G service in our area in 18 months or so, Netgear should consider a CM1100 version with two 1G WAN outputs, with optional 802.3ad (LACP) bonding, would require matching new routers with similar WAN ports (Nighthawk X11?). • Similarly, an SFP+ WAN port could be added in addition, again, would require updated routers with similar support. As far as the CM1000 firmware is concerned, would like Netgear to consider the following enhancements: • Log forwarding via syslog and/or email and/or secure XMPP (formerly Jabber for those unfamiliar) IM, with optional triggers. • A throughput/traffic panel, perhaps with a realtime graphical display of activity over the past minute • Port scan of the lower 10000 ports on the modem shows only port 80 open, which means admin passwords are sprayed over the subnet and can be seen by anyone with a packet sniffer (Android device, jailbroken iPhone, bot on on a hacked smart device). This is a security exposure and should be fixed immediately. A similar issue exists with the R9000.3.5KViews0likes1CommentCannot activate on RCN
I saw that there was another thread about the CM1000 dropping the connection on RCN, but mine does not even connect. When I called RCN to activate it with them, the packet loss ticks down from 100% to about 70 and then shoots right back up. Also relevant is that the modem's event logs had a bunch of errors regarding ToD Request Sent - No Response and Missing BP Configureation Setting. Firmware: V2.01.14 Anyone have any idea what's going on?3KViews1like2CommentsOrbi WiFi System (RBK53) AC3000
I am considering purchasing the Orbi WiFi System (RBK53) AC3000 system along with the Netgear CM1000 docsis 3.1 cable modem. Is anyone running this setup? If so, have you experienced the random network drops that some have mentioned? Also, is there a limit to how many satellites can be added before a reduction in speed occurs? I want the router and 3 satellites provided that the addition of the 3rd satellite won't cause a performance drop. Thanks in advance for your help!Solved