This topic has been marked solved and closed to new posts due to inactivity. We hope you'll join the conversation by posting to an open topic or starting a new one.
I’m encountering an unusual issue with (2) brand new AX5400 (RAX54S) routers being unable to pull an IP from the ISP’s DHCP server. Please note that I’ve done the traditional/basic troubleshooting already (power cycle, factory resets, etc). This is something more nuanced than the ol’ off and on again can solve.
The ISP is a community fiber provider in a rural area, the only in-house equipment is a Power over Ethernet injector that provides the internet cable for the router. I have confirmed with the ISP that the customer can use whatever router they prefer. I’m currently trying to replace a Motorola MR2600 router. The internet works fine with this router. I can also directly plug my laptop in to the injector and it pulls an IP address fine.
So why won’t the Nighthawk? I have experienced the same symptoms with both (brand new) routers. It does work if I leave the old router plugged in and connect a cable from the Nighthawk to one of the LAN slots, so it can pull from DHCP on these routers (just not from the ISP apparently).
I have tried all (3) available firmware, no difference. (RAX54S-V1.0.5.106_2.0.70, RAX54S-V1.0.10.110_2.0.75, RAX54S-V1.0.11.112)
I’ve also tried cloning the MAC of the old router, setting a static IP, no help. Disabling the WAN security features on the router did not do anything (Disable Port Scan and DoS protection).
Anyone with ideas of what to try next? It seems to be a firmware issue, possibly security-related? Thanks for reading.
my experience: support was useless. I returned these routers and went with TP-Link AX3200s. they work perfectly. I appreciate the condescension! my recommendation: don't buy Netgear products.
it seems unlikely to me that the ISP equipment is the issue here. other routers work, I can direct-connect my laptop and it works. double NAT would potentially cause connectivity issues with game consoles, etc -- but it wouldn't prevent a simple DHCP assignment from happening.
ISP acknowledged there should be no issue using this router and basically said "good luck, let us know if you figure it out."
I contacted Netgear support via phone and they escalated the issue, waiting to hear back from a senior tech. I really wish DD-WRT was supported on this model.
I appreciate your input. I have been troubleshooting this for 3 days and can definitively say it's not a line issue. if it were, other devices wouldn't work either. other routers work, other direct-connect devices work. I wish it were as simple as power cycling some piece of equipment.
my experience: support was useless. I returned these routers and went with TP-Link AX3200s. they work perfectly. I appreciate the condescension! my recommendation: don't buy Netgear products.
