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

Forum Discussion

bcassell's avatar
bcassell
Aspirant
Jan 26, 2017
Solved

CM1000 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 w...
CM1000
Troubleshooting
  • jimradzicki's avatar
    jimradzicki
    Oct 17, 2017

    Interesting, the overall problem was solved for me and several neighbors.  Cox replaced a mini-amplifier in the box at the street. However, I found the item that had the largest impact to overall network stability was unplugging our Ac1200's extenders. interestingly, we each had one on our individual networks and removing them resolved the overall issues.

vkdelta's avatar
vkdelta
NETGEAR Employee Retired
Feb 11, 2017

Comcast should happen early next week. 

COX will directly go to .15 as well. (no need to go .14). no ETA but should happen soon.

  • Shade00's avatar
    Shade00
    Guide
    Feb 13, 2017

    Two more dropouts today, one yesterday. I really hope early next week means tomorrow. This is beyond frustrating.

    • CowBoy_Tech's avatar
      CowBoy_Tech
      Tutor
      Feb 13, 2017

      Try having this many disconnects in the last 5 hors.....

       

       
       
       
      TimePriorityDescription
      2017-02-12, 15:02:52Critical (3)DHCP failed - DHCP Solicit sent, No DHCP Advertise received;CM-MAC=b0:7f:b9:66:d6:38;CMTS-MAC=00:01:5c:7f:a0:61;CM-QOS=1.1;CM-VER=3.1;
      2017-02-12, 15:02:58Critical (3)No Ranging Response received - T3 time-out;CM-MAC=b0:7f:b9:66:d6:38;CMTS-MAC=00:01:5c:7f:a0:61;CM-QOS=1.1;CM-VER=3.1;
      2017-02-12, 15:03:43Critical (3)DHCP failed - DHCP Solicit sent, No DHCP Advertise received;CM-MAC=b0:7f:b9:66:d6:38;CMTS-MAC=00:01:5c:7f:a0:61;CM-QOS=1.1;CM-VER=3.1;
      2017-02-12, 15:03:50Critical (3)No Ranging Response received - T3 time-out;CM-MAC=b0:7f:b9:66:d6:38;CMTS-MAC=00:01:5c:7f:a0:61;CM-QOS=1.1;CM-VER=3.1;
      2017-02-12, 15:04:32Critical (3)DHCP failed - DHCP Solicit sent, No DHCP Advertise received;CM-MAC=b0:7f:b9:66:d6:38;CMTS-MAC=00:01:5c:7f:a0:61;CM-QOS=1.1;CM-VER=3.1;
      2017-02-12, 15:04:38Critical (3)No Ranging Response received - T3 time-out;CM-MAC=b0:7f:b9:66:d6:38;CMTS-MAC=00:01:5c:7f:a0:61;CM-QOS=1.1;CM-VER=3.1;
      2017-02-12, 15:05:22Critical (3)DHCP failed - DHCP Solicit sent, No DHCP Advertise received;CM-MAC=b0:7f:b9:66:d6:38;CMTS-MAC=00:01:5c:7f:a0:61;CM-QOS=1.1;CM-VER=3.1;
      2017-02-12, 15:05:27Critical (3)No Ranging Response received - T3 time-out;CM-MAC=b0:7f:b9:66:d6:38;CMTS-MAC=00:01:5c:7f:a0:61;CM-QOS=1.1;CM-VER=3.1;
      2017-02-12, 15:06:11Critical (3)DHCP failed - DHCP Solicit sent, No DHCP Advertise received;CM-MAC=b0:7f:b9:66:d6:38;CMTS-MAC=00:01:5c:7f:a0:61;CM-QOS=1.1;CM-VER=3.1;
      2017-02-12, 15:06:15Critical (3)No Ranging Response received - T3 time-out;CM-MAC=b0:7f:b9:66:d6:38;CMTS-MAC=00:01:5c:7f:a0:61;CM-QOS=1.1;CM-VER=3.1;
      2017-02-12, 15:06:57Critical (3)DHCP failed - DHCP Solicit sent, No DHCP Advertise received;CM-MAC=b0:7f:b9:66:d6:38;CMTS-MAC=00:01:5c:7f:a0:61;CM-QOS=1.1;CM-VER=3.1;
      2017-02-12, 15:07:02Critical (3)No Ranging Response received - T3 time-out;CM-MAC=b0:7f:b9:66:d6:38;CMTS-MAC=00:01:5c:7f:a0:61;CM-QOS=1.1;CM-VER=3.1;
      2017-02-12, 15:07:45Critical (3)DHCP failed - DHCP Solicit sent, No DHCP Advertise received;CM-MAC=b0:7f:b9:66:d6:38;CMTS-MAC=00:01:5c:7f:a0:61;CM-QOS=1.1;CM-VER=3.1;
      2017-02-12, 15:07:50Critical (3)No Ranging Response received - T3 time-out;CM-MAC=b0:7f:b9:66:d6:38;CMTS-MAC=00:01:5c:7f:a0:61;CM-QOS=1.1;CM-VER=3.1;
      2017-02-12, 15:08:32Critical (3)DHCP failed - DHCP Solicit sent, No DHCP Advertise received;CM-MAC=b0:7f:b9:66:d6:38;CMTS-MAC=00:01:5c:7f:a0:61;CM-QOS=1.1;CM-VER=3.1;
      2017-02-12, 15:09:32Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=b0:7f:b9:66:d6:38;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
      2017-02-12, 15:11:11Critical (3)DHCP failed - DHCP Solicit sent, No DHCP Advertise received;CM-MAC=b0:7f:b9:66:d6:38;CMTS-MAC=00:01:5c:7f:a0:61;CM-QOS=1.1;CM-VER=3.1;
      2017-02-12, 15:11:18Critical (3)No Ranging Response received - T3 time-out;CM-MAC=b0:7f:b9:66:d6:38;CMTS-MAC=00:01:5c:7f:a0:61;CM-QOS=1.1;CM-VER=3.1;
      2017-02-12, 15:12:04Critical (3)DHCP failed - DHCP Solicit sent, No DHCP Advertise received;CM-MAC=b0:7f:b9:66:d6:38;CMTS-MAC=00:01:5c:7f:a0:61;CM-QOS=1.1;CM-VER=3.1;
      2017-02-12, 15:12:10Critical (3)No Ranging Response received - T3 time-out;CM-MAC=b0:7f:b9:66:d6:38;CMTS-MAC=00:01:5c:7f:a0:61;CM-QOS=1.1;CM-VER=3.1;
      2017-02-12, 15:12:55Critical (3)DHCP failed - DHCP Solicit sent, No DHCP Advertise received;CM-MAC=b0:7f:b9:66:d6:38;CMTS-MAC=00:01:5c:7f:a0:61;CM-QOS=1.1;CM-VER=3.1;
      2017-02-12, 15:13:00Critical (3)No Ranging Response received - T3 time-out;CM-MAC=b0:7f:b9:66:d6:38;CMTS-MAC=00:01:5c:7f:a0:61;CM-QOS=1.1;CM-VER=3.1;
      2017-02-12, 15:13:42Critical (3)DHCP failed - DHCP Solicit sent, No DHCP Advertise received;CM-MAC=b0:7f:b9:66:d6:38;CMTS-MAC=00:01:5c:7f:a0:61;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=b0:7f:b9:66:d6:38;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
      Time Not EstablishedCritical (3)No Ranging Response received - T3 time-out;CM-MAC=b0:7f:b9:66:d6:38;CMTS-MAC=00:01:5c:7f:a0:61;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=b0:7f:b9:66:d6:38;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
      Time Not EstablishedCritical (3)No Ranging Response received - T3 time-out;CM-MAC=b0:7f:b9:66:d6:38;CMTS-MAC=00:01:5c:7f:a0:61;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=b0:7f:b9:66:d6:38;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
      Time Not EstablishedCritical (3)No Ranging Response received - T3 time-out;CM-MAC=b0:7f:b9:66:d6:38;CMTS-MAC=00:01:5c:7f:a0:61;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=b0:7f:b9:66:d6:38;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
      Time Not EstablishedCritical (3)No Ranging Response received - T3 time-out;CM-MAC=b0:7f:b9:66:d6:38;CMTS-MAC=00:01:5c:7f:a0:61;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=b0:7f:b9:66:d6:38;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
      Time Not EstablishedCritical (3)No Ranging Response received - T3 time-out;CM-MAC=b0:7f:b9:66:d6:38;CMTS-MAC=00:01:5c:7f:a0:61;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=b0:7f:b9:66:d6:38;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
      Time Not EstablishedCritical (3)No Ranging Response received - T3 time-out;CM-MAC=b0:7f:b9:66:d6:38;CMTS-MAC=00:01:5c:7f:a0:61;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=b0:7f:b9:66:d6:38;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
      Time Not EstablishedCritical (3)No Ranging Response received - T3 time-out;CM-MAC=b0:7f:b9:66:d6:38;CMTS-MAC=00:01:5c:7f:a0:61;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=b0:7f:b9:66:d6:38;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
      Time Not EstablishedCritical (3)No Ranging Response received - T3 time-out;CM-MAC=b0:7f:b9:66:d6:38;CMTS-MAC=00:01:5c:7f:a0:61;CM-QOS=1.1;CM-VER=3.1;
      Time Not EstablishedNotice (6)Honoring MDD; IP provisioning mode = IPv6
       

      Help Center
       
      • CowBoy_Tech's avatar
        CowBoy_Tech
        Tutor
        Feb 13, 2017
        The people here have no idea about any firmware update!
  • Hydro130's avatar
    Hydro130
    Luminary
    Feb 13, 2017

    Dropouts from CM1000 are now increasing to several times a day for me - this is now well past being an annoyance...

     

    Oh mighty Netgear and Comcast gods - please release v .15 firmware asap!!!

    • vkdelta's avatar
      vkdelta
      NETGEAR Employee Retired
      Feb 13, 2017

      One last step to go...almost getting there. I can understand your situation..

      Just waiting for ISP to deploy new config files.

       

      • Hydro130's avatar
        Hydro130
        Luminary
        Feb 13, 2017

        Thank you for the updates - it's appreciated!!

        vkdelta wrote:

        One last step to go...almost getting there. I can understand your situation..

        Just waiting for ISP to deploy new config files.