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 ...
  • BrokenOrbi's avatar
    BrokenOrbi
    Jun 06, 2024

    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. 

  • BrokenOrbi's avatar
    BrokenOrbi
    Aspirant
    Jun 05, 2024

    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
      Jun 06, 2024

      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. 

    • FURRYe38's avatar
      FURRYe38
      Guru - Experienced User
      Jun 06, 2024

      Id put a -3dbm coax line attenuator behind the model, bring down the power just a bit as some channels are a bit too high on power:

      https://kb.netgear.com/24311/Power-level-guidelines-for-a-NETGEAR-cable-modem-router

       

      You have some Criticals in the event logs. 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.

       

      Correctables and Un-correctables are good. 

       

      Have the ISP check the signal and line quality UP to the modem. Be sure the ISP provisions the modem correctly.
      Be sure there are no coax cable line splitters in the between the modem and ISP service box. 
      Be sure your using good quality RG6 coax cable up to the modem. 
      Start with removing any amplifiers, signal attenuators, or splitters from the coax.
      From there check the line for kinks, damage, moisture in the line.
      Check the connectors for improperly made ends, foil touching the copper coax line, loose connections, bad/old/cheap connectors, or corroded connections. Replace them if you do.
      Be sure to power OFF the modem for 1 minute then back ON.
      https://community.netgear.com/t5/Cable-Modems-Routers/General-info-and-Troubleshooting-for-Cable-Modems/m-p/1530376#M12853