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

Forum Discussion

645Linden's avatar
645Linden
Aspirant
Dec 30, 2023
Solved

NETGEAR Nighthawk AX3600 (MK83) Tri-Band Mesh WiFi 6 system

I have an existing Cable/Modem/Wifi Router Arris SBG8300 and wanted to extend my existing WiFi coverage around my house.  I installed a NETGEAR Nighthawk AX3600 (MK83) Tri-Band Mesh WiFi 6 system, on...
  • 645Linden's avatar
    645Linden
    Jan 02, 2024

    So, I performed a hard-reset of my NETGEAR Nighthawk (MR80) and did minimal configuration before setting into Access Point mode.  The network came back up all devices connected and worked fine.  I then did a usual reboot of the Cable/Modem/Router and the NETGEAR MR80 & MS80, that I typically do every few months, just to keep them running clean.  When I say "reboot", I mean I power down (unplug) the devices for a couple minutes.  I then power the Cable/Modem/Router on for about 5 minutes to get it booted up and functioning, then I power on the NETGEAR MR80 for a couple minutes so its fully booted up and functioning, then power on the NETGEAR MS80.  Again, all network devices connected and are A-O-K and no red LED status light on the MR80.

     

    My guess as to why the NETGEAR MR80 acted unusual after I rebooted it the other day may have been due to me doing extra configuring of the WiFi & LAN settings before setting into Access Point mode, since a majority of the settings get greyed out once its in Access Point mode. This time I did minimal WiFi & LAN configuration in the MR80 before setting it into Access Point mode and didn't set a fixed IP address.  It may also have been due to having, as you said, both the MR80 set with a fixed IP address and the Cablem/Modem/Router being set to assign a fixed IP address for the MR80 as well.

     

    I'll consider the case closed.

    Thanks for the assistance!

michaelkenward's avatar
michaelkenward
Guru - Experienced User
Dec 31, 2023
645Linden wrote:

 

As for reserving an IP address in my existing Cable/Modem/Router, I did have the MR80 configured under "Connected Devices"/"Static Addresses" set with Host Name=MR80, IPv4 Address=192.168.0.2 & MAC Address=C8:9E:xx:xx:xx:xx.  This configuration disappeared when I rebooted Cable/Modem/Router the other day.

 

Maybe setting it on both that was the problem. One or the other.

 

In the past, though, I have done both router and AP. But that was on a Netgear network, no other brands to get in the way and possible confuse things.

 

 

645Linden's avatar
645Linden
Aspirant
Jan 02, 2024

So, I performed a hard-reset of my NETGEAR Nighthawk (MR80) and did minimal configuration before setting into Access Point mode.  The network came back up all devices connected and worked fine.  I then did a usual reboot of the Cable/Modem/Router and the NETGEAR MR80 & MS80, that I typically do every few months, just to keep them running clean.  When I say "reboot", I mean I power down (unplug) the devices for a couple minutes.  I then power the Cable/Modem/Router on for about 5 minutes to get it booted up and functioning, then I power on the NETGEAR MR80 for a couple minutes so its fully booted up and functioning, then power on the NETGEAR MS80.  Again, all network devices connected and are A-O-K and no red LED status light on the MR80.

 

My guess as to why the NETGEAR MR80 acted unusual after I rebooted it the other day may have been due to me doing extra configuring of the WiFi & LAN settings before setting into Access Point mode, since a majority of the settings get greyed out once its in Access Point mode. This time I did minimal WiFi & LAN configuration in the MR80 before setting it into Access Point mode and didn't set a fixed IP address.  It may also have been due to having, as you said, both the MR80 set with a fixed IP address and the Cablem/Modem/Router being set to assign a fixed IP address for the MR80 as well.

 

I'll consider the case closed.

Thanks for the assistance!