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

Forum Discussion

BrokenOrbi's avatar
BrokenOrbi
Aspirant
Jun 05, 2024
Solved

Orbi RBR750 Lost Internet (Purple Light)

Hi,

 

I'll try to provide my details as schematically as possible to make this as easy as possible:

 

  • ISP: xfinity
  • Modem: Netgear CM1200 Nighthawk (no wifi capability on it; purely wired cable modem)
  • Router: Orbi RBR 750
  • Setup: Coax -> Modem -> Router (ethernet cable goes direct from Modem to my PC which is how I'm able to connect right now)
    • I also have a Satellite; currently turned off to avoid any further complicating factors
    • Router sits right behind me at my desk, right next to Modem, connected by a short cable, so there's no distance issues
  • Summary of issue: everything has been working fine, connected for 2 years or so. Had one time I lost internet a few months back, but simple power cycle on Modem and Router fixed it. Went to bed last night and wifi was fine. Woke up this morning and purple light on router, no internet available:
  • Things I've tried:
    • Power cycling modem and router (switching both off, unplugging cable from Modem to Router, turn modem back on, wait for internet to be restored to it, turn Router back on, wait till it's fully operational, connect cable between the two)
    • Factory reset on router
    • Update firmware to V7.2.6.31_5.0.24
    • Set router to AP mode (this broke router, couldn't connect at all, no Gateway available, had to do another factory reset)
    • Reached out to xfinity to see if there's any reset they could do their end -- nothing they could do
    • Tried three different ethernet cables between modem and router
    • Setting static IP (well, I haven't tried this, just listing it as a suggestion I've seen, but cannot do, since xfinity apparently don't offer this for residential customers, only for business) 
    • Resetting MAC address per this guy's post

It's currently sitting at a clean setup after a factory reset, so assume all settings are set to default at the moment. I've been working on this all day, reading various reddit threads, netgear.com threads and other community posts, trying to find something to fix this, but no luck so far. Gone through numerous power cycles and factory resets.

 

It's gone out so randomly, just by itself, overnight, I can only assume it went through some automatic firmware update that failed or something, but it was at like 4.x.x this morning before I did the manual update, so it doesn't look like it was even doing the automatic updates and, anyway, I would've assume between the factory reset and manual update that would've fixed it if that was the issue. But I dunno.

 

All I can think is something happened on the Xfinity side, some kind of update to my connection or something that somehow didn't percolate through from the Modem to the Router, but I really have no clue. 

 

Appreciate any insight anyone can offer here. Thanks.

  • I fixed it!

     

    Blimey, I spent all day on this, trying a bunch of different things. Turns out the solution was very simple. Very dumb, but hopefully it helps someone else googling this, and this thread comes up:

     

    Basically this was the issue:

    https://community.netgear.com/t5/Nighthawk-Wi-Fi-5-AC-Routers/Modem-wont-send-Internet-to-router/m-p/2091527/highlight/true#M190115

     

    I had my laptop connected directly to the modem via an ethernet cable (as described in my OP) alongside the router. Xfinity/Comcast doesn't like this. So I did as described above: disconnected all ethernet cables from the modem, turned the modem off, turned it back on, connected it to the Orbi, and hey presto, it was working (it asked me to reset the orbi admin page password for some reason, too).

     

    What a nightmare. I spent all day on this, inc. driving out to grab someone's old router off craigslist. It was in trying out the second router and encountering the same problem, that it forced me back to consider something was wrong in the setup of the modem, and to google: "Netgear CM1200 Nighthawk not forwarding to router" which led me to the above post. So if you're reading this and this doesn't fix it for you, try googling that and figuring out what the issue is with your modem not forwarding the internet connection, rather than the Orbi not receiving. 

4 Replies

    • BrokenOrbi's avatar
      BrokenOrbi
      Aspirant

      Connection Status:

       

      Event Log:

       
       
       
       
      TimePriorityDescription
      Wed Jun 05 15:10:26 2024Notice (6)CM-STATUS message sent. Event Type Code: 5; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=80:cc:9c:6d:71:a8;CMTS-MAC=00:90:f0:17:04:00;CM-QOS=1.1;CM-VER=3.1;
      Wed Jun 05 15:10:12 2024Critical (3)UCD invalid or channel unusable;CM-MAC=80:cc:9c:6d:71:a8;CMTS-MAC=00:90:f0:17:04:00;CM-QOS=1.1;CM-VER=3.1;
      Wed Jun 05 15:10:05 2024Notice (6)DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=80:cc:9c:6d:71:a8;CMTS-MAC=00:90:f0:17:04:00;CM-QOS=1.1;CM-VER=3.1;
      Wed Jun 05 15:10:00 2024Notice (6)TLV-11 - unrecognized OID;CM-MAC=80:cc:9c:6d:71:a8;CMTS-MAC=00:90:f0:17:04:00;CM-QOS=1.1;CM-VER=3.1;
      Time Not EstablishedNotice (6)Honoring MDD; IP provisioning mode = IPv6
      Time Not EstablishedCritical (3)UCD invalid or channel unusable;CM-MAC=80:cc:9c:6d:71:a8;CMTS-MAC=00:90:f0:17:04:00;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=80:cc:9c:6d:71:a8;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
      Wed Jun 05 10:59:38 2024Notice (6)CM-STATUS message sent. Event Type Code: 5; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=80:cc:9c:6d:71:a8;CMTS-MAC=00:90:f0:17:04:00;CM-QOS=1.1;CM-VER=3.1;
      Wed Jun 05 10:59:13 2024Critical (3)UCD invalid or channel unusable;CM-MAC=80:cc:9c:6d:71:a8;CMTS-MAC=00:90:f0:17:04:00;CM-QOS=1.1;CM-VER=3.1;
      Wed Jun 05 10:59:06 2024Notice (6)DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=80:cc:9c:6d:71:a8;CMTS-MAC=00:90:f0:17:04:00;CM-QOS=1.1;CM-VER=3.1;
      Wed Jun 05 10:59:01 2024Notice (6)TLV-11 - unrecognized OID;CM-MAC=80:cc:9c:6d:71:a8;CMTS-MAC=00:90:f0:17:04:00;CM-QOS=1.1;CM-VER=3.1;
      Time Not EstablishedNotice (6)Honoring MDD; IP provisioning mode = IPv6
      Time Not EstablishedCritical (3)UCD invalid or channel unusable;CM-MAC=80:cc:9c:6d:71:a8;CMTS-MAC=00:90:f0:17:04:00;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=80:cc:9c:6d:71:a8;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
      Wed Jun 05 10:20:11 2024Critical (3)UCD invalid or channel unusable;CM-MAC=80:cc:9c:6d:71:a8;CMTS-MAC=00:90:f0:17:04:00;CM-QOS=1.1;CM-VER=3.1;
      Wed Jun 05 10:20:04 2024Notice (6)DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=80:cc:9c:6d:71:a8;CMTS-MAC=00:90:f0:17:04:00;CM-QOS=1.1;CM-VER=3.1;
      Wed Jun 05 10:19:58 2024Notice (6)TLV-11 - unrecognized OID;CM-MAC=80:cc:9c:6d:71:a8;CMTS-MAC=00:90:f0:17:04:00;CM-QOS=1.1;CM-VER=3.1;
      Time Not EstablishedNotice (6)Honoring MDD; IP provisioning mode = IPv6
      Time Not EstablishedCritical (3)UCD invalid or channel unusable;CM-MAC=80:cc:9c:6d:71:a8;CMTS-MAC=00:90:f0:17:04:00;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=80:cc:9c:6d:71:a8;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
      Wed Jun 05 10:02:04 2024Critical (3)UCD invalid or channel unusable;CM-MAC=80:cc:9c:6d:71:a8;CMTS-MAC=00:90:f0:17:04:00;CM-QOS=1.1;CM-VER=3.1;
      Wed Jun 05 10:01:56 2024Notice (6)DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=80:cc:9c:6d:71:a8;CMTS-MAC=00:90:f0:17:04:00;CM-QOS=1.1;CM-VER=3.1;
      Wed Jun 05 10:01:51 2024Notice (6)TLV-11 - unrecognized OID;CM-MAC=80:cc:9c:6d:71:a8;CMTS-MAC=00:90:f0:17:04:00;CM-QOS=1.1;CM-VER=3.1;
      Time Not EstablishedNotice (6)Honoring MDD; IP provisioning mode = IPv6
      Time Not EstablishedCritical (3)UCD invalid or channel unusable;CM-MAC=80:cc:9c:6d:71:a8;CMTS-MAC=00:90:f0:17:04:00;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=80:cc:9c:6d:71:a8;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
      Wed Jun 05 09:38:55 2024Notice (6)CM-STATUS message sent. Event Type Code: 5; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=80:cc:9c:6d:71:a8;CMTS-MAC=00:90:f0:17:04:00;CM-QOS=1.1;CM-VER=3.1;
      Wed Jun 05 09:38:27 2024Critical (3)UCD invalid or channel unusable;CM-MAC=80:cc:9c:6d:71:a8;CMTS-MAC=00:90:f0:17:04:00;CM-QOS=1.1;CM-VER=3.1;
      Wed Jun 05 09:38:19 2024Notice (6)DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=80:cc:9c:6d:71:a8;CMTS-MAC=00:90:f0:17:04:00;CM-QOS=1.1;CM-VER=3.1;
      Wed Jun 05 09:38:14 2024Notice (6)TLV-11 - unrecognized OID;CM-MAC=80:cc:9c:6d:71:a8;CMTS-MAC=00:90:f0:17:04:00;CM-QOS=1.1;CM-VER=3.1;
      Time Not EstablishedNotice (6)Honoring MDD; IP provisioning mode = IPv6
      Time Not EstablishedCritical (3)UCD invalid or channel unusable;CM-MAC=80:cc:9c:6d:71:a8;CMTS-MAC=00:90:f0:17:04:00;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=80:cc:9c:6d:71:a8;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
      Wed Jun 05 09:23:31 2024Critical (3)UCD invalid or channel unusable;CM-MAC=80:cc:9c:6d:71:a8;CMTS-MAC=00:90:f0:17:04:00;CM-QOS=1.1;CM-VER=3.1;
      Wed Jun 05 09:23:24 2024Notice (6)DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=80:cc:9c:6d:71:a8;CMTS-MAC=00:90:f0:17:04:00;CM-QOS=1.1;CM-VER=3.1;
      Wed Jun 05 09:23:19 2024Notice (6)TLV-11 - unrecognized OID;CM-MAC=80:cc:9c:6d:71:a8;CMTS-MAC=00:90:f0:17:04:00;CM-QOS=1.1;CM-VER=3.1;
      Time Not EstablishedNotice (6)Honoring MDD; IP provisioning mode = IPv6
      Time Not EstablishedCritical (3)UCD invalid or channel unusable;CM-MAC=80:cc:9c:6d:71:a8;CMTS-MAC=00:90:f0:17:04:00;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=80:cc:9c:6d:71:a8;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
      Wed Jun 05 09:19:26 2024Critical (3)UCD invalid or channel unusable;CM-MAC=80:cc:9c:6d:71:a8;CMTS-MAC=00:90:f0:17:04:00;CM-QOS=1.1;CM-VER=3.1;
      • BrokenOrbi's avatar
        BrokenOrbi
        Aspirant

        I fixed it!

         

        Blimey, I spent all day on this, trying a bunch of different things. Turns out the solution was very simple. Very dumb, but hopefully it helps someone else googling this, and this thread comes up:

         

        Basically this was the issue:

        https://community.netgear.com/t5/Nighthawk-Wi-Fi-5-AC-Routers/Modem-wont-send-Internet-to-router/m-p/2091527/highlight/true#M190115

         

        I had my laptop connected directly to the modem via an ethernet cable (as described in my OP) alongside the router. Xfinity/Comcast doesn't like this. So I did as described above: disconnected all ethernet cables from the modem, turned the modem off, turned it back on, connected it to the Orbi, and hey presto, it was working (it asked me to reset the orbi admin page password for some reason, too).

         

        What a nightmare. I spent all day on this, inc. driving out to grab someone's old router off craigslist. It was in trying out the second router and encountering the same problem, that it forced me back to consider something was wrong in the setup of the modem, and to google: "Netgear CM1200 Nighthawk not forwarding to router" which led me to the above post. So if you're reading this and this doesn't fix it for you, try googling that and figuring out what the issue is with your modem not forwarding the internet connection, rather than the Orbi not receiving.