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

Forum Discussion

BigStyz's avatar
BigStyz
Aspirant
Feb 24, 2025
Solved

RBR750 dropping connection and poor network quality

I began experiencing network issues 2 weeks ago.  Day 1 and Day 2, no internet for 15-30 minute segments over the course of 4 hours each day.  On each of the subsequent days, the internet has staye...
  • BigStyz's avatar
    BigStyz
    Mar 10, 2025

    Problem solved. Thanks for the insight. The ISP made 3 trips to the house, and each tech "found" something new and wrong on their end. After tech #3, the errors went away and speeds are back up. It was not a hardware issue, but it took a lot to get to that answer. 

BigStyz's avatar
BigStyz
Aspirant
Feb 25, 2025
FURRYe38 wrote:

Does the front LED on the RBR and or the RBS turn PINK or blink WHITE when this happens? NO

 

What Firmware version is currently loaded? V7.2.6.31_5.0.24
What is the Mfr and model# of the Internet Service Providers modem/ONT the NG router is connected too? 

NETGEAR Nighthawk DOCSIS 3.1 32x8 Multi-Gigabit Cable Modem with Voice (CM2050V)


Be sure your using a good quality LAN cable between the modem and router. CAT6 is recommended. Confirmed CAT6.

 

What is the size of your home? Sq Ft?3 Levels, 5000SF
What is the distance between the router 📡 and satellite(s)🛰️? 30 feet or more is recommended in between RBR 📡 and RBS 🛰️ to begin with depending upon building materials when wired or wirelessly connected.
https://kb.netgear.com/31029/Where-should-I-place-my-Orbi-satellite ‌‌🛰

Router in B, Satellites 1 and 2 on 1st FL. Satellite 3 on 2nd FL This has been an effective placement for the last 4 years.

Are the RBS wireless or ethernet connected to the RBR? They are all wirelessly connected

 

Does this happen with the RBS turned OFF? Never tried
Does this happen with both wireless and wired devices? 

Yes. The same thing happens on devices connected both ways.


What channel configurations are currently set on the router?  2.4… Auto (6); 5… 36+40+44+48(P)

 

Be sure to disable any MAC Address randomizers on phones and pads while at home:
https://community.netgear.com/t5/Orbi-App/NETGEAR-Mobile-Applications-and-Apple-Devices-FAQ/td-p/2220016/jump-to/first-unread-message

 

Try disabling the following and see:
Armor, Smart Parental Controls or Circle, IPv6, Traffic Meter. All confirmed disabled

 

Has a power off for 1 minute then back ON with the ISP modem and router and satellite(s) been performed since last update?
Be sure to restart your network in this sequence:
Turn off and unplug modem.
Turn off router and computers.
Plug in and turn on modem. Wait 2 minutes for it to connect.
Turn on the router and wait 2 minutes for it to connect.
Turn on computers and rest of network.

Yes. Same sequence Comcast advised during troubleshooting

 

FURRYe38's avatar
FURRYe38
Guru - Experienced User
Feb 25, 2025

Had this been working ok before v.31 FW was applied or has this been happening for a while now? 

 

Please post a copy and paste of the modems connection status and event log page.
https://kb.netgear.com/30007/How-do-I-obtain-the-cable-connection-information-from-a-NETGEAR-cable-modem-modem-router
https://kb.netgear.com/30008/How-do-I-view-or-clear-the-event-logs-on-my-NETGEAR-cable-modem-or-modem-router

What FW version is loaded on the CM modem? Been some recent posts about v10 being slowly pushed by the ISP. 

  • BigStyz's avatar
    BigStyz
    Aspirant
    Feb 25, 2025

    The issue began on Feb 8. I cannot see a date the latest firmware was applied. 

    The logs you requested exceed the character limit, but I will try to separate them into manageable chunks. 

    The Cable Firmware Version is V2.01.03

     

    • BigStyz's avatar
      BigStyz
      Aspirant
      Feb 25, 2025

      Event Log

      Time

      		PriorityDescription
      Tue Feb 25 12:24:53 2025(Critical (3))Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:3a:95:a0;CMTS-MAC=00:90:f0:22:04:00;CM-QOS=1.1;CM-VER=3.1;
      Mon Feb 24 12:44:24 2025(Notice (6))CM-STATUS message sent. Event Type Code: 24; Chan ID: 193 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=08:36:c9:3a:95:a0;CMTS-MAC=00:90:f0:22:04:00;CM-QOS=1.1;CM-VER=3.1;
      Mon Feb 24 12:29:36 2025(Notice (6))CM-STATUS message sent. Event Type Code: 16; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=08:36:c9:3a:95:a0;CMTS-MAC=00:90:f0:22:04:00;CM-QOS=1.1;CM-VER=3.1;
      Mon Feb 24 08:36:28 2025(Notice (6))CM-STATUS message sent. Event Type Code: 24; Chan ID: 193 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=08:36:c9:3a:95:a0;CMTS-MAC=00:90:f0:22:04:00;CM-QOS=1.1;CM-VER=3.1;
      Mon Feb 24 08:20:49 2025(Notice (6))CM-STATUS message sent. Event Type Code: 16; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=08:36:c9:3a:95:a0;CMTS-MAC=00:90:f0:22:04:00;CM-QOS=1.1;CM-VER=3.1;
      Mon Feb 24 08:16:28 2025(Notice (6))CM-STATUS message sent. Event Type Code: 24; Chan ID: 193 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=08:36:c9:3a:95:a0;CMTS-MAC=00:90:f0:22:04:00;CM-QOS=1.1;CM-VER=3.1;
      Mon Feb 24 08:12:15 2025(Notice (6))CM-STATUS message sent. Event Type Code: 16; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=08:36:c9:3a:95:a0;CMTS-MAC=00:90:f0:22:04:00;CM-QOS=1.1;CM-VER=3.1;
      Mon Feb 24 08:09:48 2025(Notice (6))CM-STATUS message sent. Event Type Code: 24; Chan ID: 193 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=08:36:c9:3a:95:a0;CMTS-MAC=00:90:f0:22:04:00;CM-QOS=1.1;CM-VER=3.1;
      Mon Feb 24 08:09:18 2025(Notice (6))CM-STATUS message sent. Event Type Code: 16; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=08:36:c9:3a:95:a0;CMTS-MAC=00:90:f0:22:04:00;CM-QOS=1.1;CM-VER=3.1;
      Mon Feb 24 08:05:32 2025(Notice (6))CM-STATUS message sent. Event Type Code: 24; Chan ID: 193 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=08:36:c9:3a:95:a0;CMTS-MAC=00:90:f0:22:04:00;CM-QOS=1.1;CM-VER=3.1;
      Mon Feb 24 08:02:10 2025(Notice (6))CM-STATUS message sent. Event Type Code: 16; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=08:36:c9:3a:95:a0;CMTS-MAC=00:90:f0:22:04:00;CM-QOS=1.1;CM-VER=3.1;
      Mon Feb 24 07:58:52 2025(Notice (6))CM-STATUS message sent. Event Type Code: 24; Chan ID: 193 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=08:36:c9:3a:95:a0;CMTS-MAC=00:90:f0:22:04:00;CM-QOS=1.1;CM-VER=3.1;
      Mon Feb 24 07:49:20 2025(Notice (6))CM-STATUS message sent. Event Type Code: 16; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=08:36:c9:3a:95:a0;CMTS-MAC=00:90:f0:22:04:00;CM-QOS=1.1;CM-VER=3.1;
      Mon Feb 24 07:48:00 2025(Notice (6))CM-STATUS message sent. Event Type Code: 16; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=08:36:c9:3a:95:a0;CMTS-MAC=00:90:f0:22:04:00;CM-QOS=1.1;CM-VER=3.1;
      Mon Feb 24 07:45:32 2025(Notice (6))CM-STATUS message sent. Event Type Code: 24; Chan ID: 193 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=08:36:c9:3a:95:a0;CMTS-MAC=00:90:f0:22:04:00;CM-QOS=1.1;CM-VER=3.1;
      Mon Feb 24 07:40:06 2025(Notice (6))CM-STATUS message sent. Event Type Code: 16; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=08:36:c9:3a:95:a0;CMTS-MAC=00:90:f0:22:04:00;CM-QOS=1.1;CM-VER=3.1;
      Mon Feb 24 07:38:52 2025(Notice (6))CM-STATUS message sent. Event Type Code: 24; Chan ID: 193 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=08:36:c9:3a:95:a0;CMTS-MAC=00:90:f0:22:04:00;CM-QOS=1.1;CM-VER=3.1;
      Mon Feb 24 07:36:04 2025(Notice (6))CM-STATUS message sent. Event Type Code: 16; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=08:36:c9:3a:95:a0;CMTS-MAC=00:90:f0:22:04:00;CM-QOS=1.1;CM-VER=3.1;
      Mon Feb 24 07:35:50 2025(Notice (6))CM-STATUS message sent. Event Type Code: 16; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=08:36:c9:3a:95:a0;CMTS-MAC=00:90:f0:22:04:00;CM-QOS=1.1;CM-VER=3.1;
      Mon Feb 24 02:04:49 2025(Notice (6))CM-STATUS message sent. Event Type Code: 4; Chan ID: 1 2 3 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 193 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=08:36:c9:3a:95:a0;CMTS-MAC=00:90:f0:22:04:00;CM-QOS=1.1;CM-VER=3.1;
      Mon Feb 24 02:03:28 2025(Warning (5))MDD message timeout;CM-MAC=08:36:c9:3a:95:a0;CMTS-MAC=00:90:f0:22:04:00;CM-QOS=1.1;CM-VER=3.1;
      Mon Feb 24 01:17:54 2025(Critical (3))Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:3a:95:a0;CMTS-MAC=00:90:f0:22:04:00;CM-QOS=1.1;CM-VER=3.1;
      Mon Feb 24 01:07:14 2025(Notice (6))CM-STATUS message sent. Event Type Code: 4; Chan ID: 1 2 3 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 193 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=08:36:c9:3a:95:a0;CMTS-MAC=00:90:f0:22:04:00;CM-QOS=1.1;CM-VER=3.1;
      Mon Feb 24 01:05:44 2025(Warning (5))MDD message timeout;CM-MAC=08:36:c9:3a:95:a0;CMTS-MAC=00:90:f0:22:04:00;CM-QOS=1.1;CM-VER=3.1;
      Sun Feb 23 17:02:15 2025(Notice (6))CM-STATUS message sent. Event Type Code: 4; Chan ID: 2; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=08:36:c9:3a:95:a0;CMTS-MAC=00:90:f0:22:04:00;CM-QOS=1.1;CM-VER=3.1;
      Sun Feb 23 17:02:04 2025(Warning (5))MDD message timeout;CM-MAC=08:36:c9:3a:95:a0;CMTS-MAC=00:90:f0:22:04:00;CM-QOS=1.1;CM-VER=3.1;
      Sun Feb 23 12:12:07 2025(Notice (6))CM-STATUS message sent. Event Type Code: 24; Chan ID: 193 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=08:36:c9:3a:95:a0;CMTS-MAC=00:90:f0:22:04:00;CM-QOS=1.1;CM-VER=3.1;
      Sun Feb 23 12:05:07 2025(Notice (6))CM-STATUS message sent. Event Type Code: 24; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=08:36:c9:3a:95:a0;CMTS-MAC=00:90:f0:22:04:00;CM-QOS=1.1;CM-VER=3.1;
      Sun Feb 23 12:04:12 2025(Notice (6))CM-STATUS message sent. Event Type Code: 16; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=08:36:c9:3a:95:a0;CMTS-MAC=00:90:f0:22:04:00;CM-QOS=1.1;CM-VER=3.1;
      Sun Feb 23 06:29:54 2025(Notice (6))CM-STATUS message sent. Event Type Code: 5; Chan ID: 2 193 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=08:36:c9:3a:95:a0;CMTS-MAC=00:90:f0:22:04:00;CM-QOS=1.1;CM-VER=3.1;
      Sun Feb 23 06:29:30 2025(Notice (6))CM-STATUS message sent. Event Type Code: 4; Chan ID: 2; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=08:36:c9:3a:95:a0;CMTS-MAC=00:90:f0:22:04:00;CM-QOS=1.1;CM-VER=3.1;
      Sun Feb 23 06:29:30 2025(Warning (5))MDD message timeout;CM-MAC=08:36:c9:3a:95:a0;CMTS-MAC=00:90:f0:22:04:00;CM-QOS=1.1;CM-VER=3.1;
      Sun Feb 23 04:38:43 2025(Notice (6))CM-STATUS message sent. Event Type Code: 5; Chan ID: 2 193 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=08:36:c9:3a:95:a0;CMTS-MAC=00:90:f0:22:04:00;CM-QOS=1.1;CM-VER=3.1;
      Sat Feb 22 22:24:37 2025(Notice (6))CM-STATUS message sent. Event Type Code: 4; Chan ID: 2; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=08:36:c9:3a:95:a0;CMTS-MAC=00:90:f0:22:04:00;CM-QOS=1.1;CM-VER=3.1;
      Sat Feb 22 22:24:09 2025(Warning (5))MDD message timeout;CM-MAC=08:36:c9:3a:95:a0;CMTS-MAC=00:90:f0:22:04:00;CM-QOS=1.1;CM-VER=3.1;
      Sat Feb 22 15:40:12 2025(Notice (6))CM-STATUS message sent. Event Type Code: 22; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=08:36:c9:3a:95:a0;CMTS-MAC=00:90:f0:22:04:00;CM-QOS=1.1;CM-VER=3.1;
      Sat Feb 22 15:38:17 2025(Notice (6))CM-STATUS message sent. Event Type Code: 20; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=08:36:c9:3a:95:a0;CMTS-MAC=00:90:f0:22:04:00;CM-QOS=1.1;CM-VER=3.1;
      Sat Feb 22 08:53:32 2025(Notice (6))CM-STATUS message sent. Event Type Code: 24; Chan ID: 193 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=08:36:c9:3a:95:a0;CMTS-MAC=00:90:f0:22:04:00;CM-QOS=1.1;CM-VER=3.1;
      Sat Feb 22 08:48:07 2025(Notice (6))CM-STATUS message sent. Event Type Code: 16; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=08:36:c9:3a:95:a0;CMTS-MAC=00:90:f0:22:04:00;CM-QOS=1.1;CM-VER=3.1;
      Fri Feb 21 11:17:51 2025(Notice (6))CM-STATUS message sent. Event Type Code: 24; Chan ID: 193 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=08:36:c9:3a:95:a0;CMTS-MAC=00:90:f0:22:04:00;CM-QOS=1.1;CM-VER=3.1;
      • FURRYe38's avatar
        FURRYe38
        Guru - Experienced User
        Feb 25, 2025

        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.