Re: Nighthawk AX4: DHCP Not Working - IP not assigned automatically
@Tommy1981 wrote: Netgear would not talk to me about how to fix it unless I gave them 139 but he did email me a link to how to manually update the firmware.
Netgear does not provide paid support. It farms that out through Gearhead.
@Tommy1981 wrote: I called back and explained to the tech guy exactly what I did. He admitted that updating with a computer is better than using a phone app. The app downloads and uploads at the same time, while the computer will download it first and then upload it all at once.
This is a long recognised bit of advice. To add to it, it isn't just using the app that many people avoid. They also refuse to let the browser interface do it. This reduces the risk of an interrupted update that can happen when the Internet does mid update.
The manual approach is always advisable if you have the resources to do it. First download your own copy of the firmware, then apply it.
Re: Nighthawk AX4: DHCP Not Working - IP not assigned automatically
I'm having the same issue. Judging from the comments and Netgear's crappy support best fix is to scrap it and never buy or recommend a Netgear product ever again.
Re: Nighthawk AX4: DHCP Not Working - IP not assigned automatically
Hello all,
I recently purchased a Netgear AC1750 router to replace my local ISP router that I had been renting. Setting it up was fairly easy enough, but I noticed that when re-booting the router or if the power goes out for some reason, many devices on my network have trouble re-connecting. They appear to sit spinning waiting for an IP address to be assigned.
I have many "smart" devices connected to my network such as light switchs, light bulbs, outlets, TVs, "smart" speakers, etc. I have ~30+ devices all connected to the network. While I'm in IT software development for a living, I do not do hardware or infrastructure... so I'm by no means an expert in this area. Yet, I know enough to get myself into trouble... 🙂
When the power goes out and all devices start scrambling to get re-connected, the router seems to have trouble dealing with the high-volume of traffic. Not sure if there is a setting somewhere that somehow throttles this or tells devices to refresh or something.. but, here's what seemed to solve my problem.
I simply went into the LAN setup page and assigned static IP addresses to all the devices in the home that are always here. Every light switch, outlet, lighbulb, smart TV, smart speaker, etc. is reserved its own IP address. Now when I re-boot the router, everyone goes to their spot and connections happen VERY fast. Seems to have resolved the issue for me.
Then when I connect something new like a laptop, smart phone, etc... not all of those are assigned and IP and the router seems to have an easier time of assigning just those few as needed. It's not doing it for every device every time I reboot or power or network hiccups for a brief moment.
I recently purchased a Netgear AC1750 router to replace my local ISP router
That could be one of several devices. AC1750 is not a reliable guide to model number. Many devices come with an AC tag, but it is essentially a label that Netgear, and other brands, attach to hardware to describe wifi speeds.
Look at the label on the device for the model number.
Re: Nighthawk AX4: DHCP Not Working - IP not assigned automatically
Just reboot it until it does. Look how long this thread has been going. Look at how many other threads on the exact same issue have popped up. Netgear doesn't give a **bleep**. Horrible product, 0 support. Okay going to unsubscribe from this now, better luck next time you buy a router everyone.
Re: Nighthawk AX4: DHCP Not Working - IP not assigned automatically
Same, I personally won't be buying a netgear or dlink router again, if I hadn't decided to replace my RAX40 with a dream machine pro, I would have just bought a raspberry pi and used pi hole as a router replacement.
Re: Nighthawk AX4: DHCP Not Working - IP not assigned automatically
Been having the same issues with my R8000. Worked for months without any problems. Started getting a single device failing to pick up a dhcp address until the router was rebooted. I also tried rebooting the affected device, but that doesn't help - only rebooting the router fixes it. As time passed, it's slowly turned into multiple devices being unable to get an address and a reboot of the router at least once a day or face the kids moaning because their xbox is getting that dhcp error again.
Fortunately I have a linux machine running in the house, so I've disabled the router's dhcp server and installed dnsmasq on the llinux machine. Everything is working again.
Pretty dissapointed with the Netgear router at the moment - it's not a cheap bit of kit and it's only saving grace is that it's still better than the VirginMedia superhub for WiFi.
Re: Nighthawk AX4: DHCP Not Working - IP not assigned automatically
I’ve gone into LAN and reserved loads of devices that never leave the house with fixed IPs, not had any issues for a few months (probably just jinxed myself posting this)
Re: Nighthawk AX4: DHCP Not Working - IP not assigned automatically
I have a 2.5yo R6350 (AC1750) running the latest firmware: V1.1.0.84_1.0.1 with the same issues. I've tried everything as noted in the first post (and downgrading to 64_1.0.1 or 78_1.0.1 didn't help). What I *did* notice, and this is a poor workaround, is that when I reduced the number of connected devices to < 32, then DHCP began working again.
In all cases, the logfile shows that the IP addresses *are* being allocated, but they never transmitted to the device. With Access Control turned on, successful connections are properly logged when things are working fine. When broken, there are no [Access Control] entries. Again, turning off Access Control does *not* resolve the issue. I believe Access Control is *not* the issue, and the root cause maybe due to an internal table overflow.
The reason that firmware changes or rebooting can temporarily fix is that you reduce the number of devices at bootup. If you have > 32 devices at bootup then it will still fail. A quick test is to change your SSID and try connecting to that one. Things will work until you, once again, connect to too many devices.
My resolution plan is to purchase a new router, but given this major core issue that is not being addressed by Netgear (a wireless router's core function is to connect to wireless devices), I plan to return to Linksys.
Re: Nighthawk AX4: DHCP Not Working - IP not assigned automatically
Netgear has set up a community forum specifically for Smart WiFi Router products. Most of the people who watch that forum are more likely to have experience with General and Smart Wifi (WN and R6000 thru R6400 Series) routers. Might be more likely to find someone who has a solution if the question is posted there since the R6000 series differs from the RAX router series: https://community.netgear.com/t5/General-WiFi-Routers-Non/bd-p/home-wifi-routers-general
I have a 2.5yo R6350 (AC1750) running the latest firmware: V1.1.0.84_1.0.1 with the same issues. I've tried everything as noted in the first post (and downgrading to 64_1.0.1 or 78_1.0.1 didn't help). What I *did* notice, and this is a poor workaround, is that when I reduced the number of connected devices to < 32, then DHCP began working again.
In all cases, the logfile shows that the IP addresses *are* being allocated, but they never transmitted to the device. With Access Control turned on, successful connections are properly logged when things are working fine. When broken, there are no [Access Control] entries. Again, turning off Access Control does *not* resolve the issue. I believe Access Control is *not* the issue, and the root cause maybe due to an internal table overflow.
The reason that firmware changes or rebooting can temporarily fix is that you reduce the number of devices at bootup. If you have > 32 devices at bootup then it will still fail. A quick test is to change your SSID and try connecting to that one. Things will work until you, once again, connect to too many devices.
My resolution plan is to purchase a new router, but given this major core issue that is not being addressed by Netgear (a wireless router's core function is to connect to wireless devices), I plan to return to Linksys.
