NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
mc2software
May 10, 2021Follower
RAX80 DHCP problems
I've recently been having problems with the DHCP server on my RAX80. The first problem is that the router changes the DCHP network mask. I have the router set to 192.168.2.1. I do this because I've run into issues with some VPN software if their's is 192.168.1.### (remote desktop gets confused). Anyway, I've had issues with some Windows 10 computers being assigned a 192.168.1.### ip address. Obviously, this prevents internet access. If I manually set the ip address to the 192.168.2 mask, it works. In addition, I'm also having problems with it just assigning a After various tests, I discovered that this happens ONLY on the main 5G SSID. If I connect the same computer to the guest 5G network, DHCP works fine. 2.4 also works on both main SSID and guest. Only problem is on the main 5G SSID and the only solution I've found is to add the Windows 10 computers to the Address Reservation list.
2 Replies
Sort By
what modem/gateway is the rax connected to?
> Model: RAX80|Nighthawk AX8 8-Stream WiFi Router
Firmware version? Connected to what?
> [...] The first problem is that the router changes the DCHP network
> mask. I have the router set to 192.168.2.1. [...]First, "192.168.2.0" is the subnet; "255.255.255.0" is the subnet
mask.Second, I see no evidence yet that the router is responsible for
what's happening.> [...] I do this because I've run into issues with some VPN software
> [...]Is there any VPN software involved currently?
> [...] Anyway, I've had issues with some Windows 10 computers being
> assigned a 192.168.1.### ip address. [...]One easy explanation for that would be the presence of another DHCP
server on your LAN.> [...] I discovered that this happens ONLY on the main 5G SSID. [...]
Perhaps a DHCP server on some gizmo with a 5GHz wireless interface.
I'd shut down the router, and see if a wireless device still sees the
trouble-maker SSID.If you can't find a culprit other than the router, then I'd probably
resort to the old stand-by: settings reset and manual reconfiguration.