NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
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...
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!
My NETGEAR Nighthawk access point is configured with a "fixed IP". I set this via "Advanced Setup"/"Wireless AP" where I selected "Enable fixed IP settings on this device (not recommended)". Just below this selection is where I entered the fixed IP address of 192.168.0.2.
I've tried to find the NETGEAR Nighthawk access point IP address, after I rebooted it, by way of looking inside my Arris Cable/Modem under connected devices, which shows all devices except my NETGEAR Nighthawk access point. I also tried to ping, arp -a and use an IP scanner to figure out what my access points IP address is, which no results.
645Linden wrote:
My NETGEAR Nighthawk access point is configured with a "fixed IP".
Thanks for clearing that up. Fixed is not static, which is what you originally wrote.
Have you tried leaving it "unfixed" and using a reserved address in your modem.router? Maybe it doesn't have that option.
Trying to troubleshoot the interaction between two devices isn't always easy. Might be worth looking at both sides. After all, in the MR80 is in AP mode, the main router is in charge.
Yes, "unfixing" the IP address is doable and most likely my next step. Although all of my 20 WiFi devices are connecting and functioning fine, it's just weird that I can't see, ping or browse into the MR80 Acccess Point after it rebooted and that it now has a red LED status light. My MS80 (Satellite) still has a blue LED status light and is connecting fine to the MR80 via WiFi. Anyway, I'll need to do a hard reset on the MR80, which will revert all settings back to factory configuration, which isn't a big deal, and I'll go ahead and configure the MR80 Access Point IP address to "Get dynamically from existing router" after I reset it tomorrow. With the "Get dynamically from existing router" configured, it's likely that my MR80 will keep its existing IP address if/when it reboots, but, if it did change, I should easily be able to find its IP address by viewing connected devices through the existing Cable/Modem/Router. After I reset the MR80, I'll let you know if my two anomalies go away, which are 1) not being able see or browse into the MR80 and 2) the single LED status light goes from red back to blue.
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.
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.
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!