NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Wifi losing internet access
I just purchased the RAX80 (AX8) router from Best Buy last Friday. I had problems right out of the box with the router failing to provide DHCP addresses to my work laptop. Because of COVID19, I h...
Before you return it, have you performed a factory reset by using the pin hole on the back of the router? You should give it a try.
Honestly, I would returned RAX 80. This is what I did. I had the Costco version RAX75, it was a piece of garbage with the same symptoms you are having, so I returned it and purchase the more robust RAX200.
Yes, I did a factory reset last week. The problem just came back today. The one thing I noticed was my laptop said that the ip it wanted to use 192.168.1.9 (preferred)
My cell phone was already using this IP.
I've seen this behavior before where a device will assume it's last IP if it can't renew its lease. I have a feeling the DHCP service is failing on the router, or is behaving in a way not compatible with my laptop or Win10, and when my machine tries to use the old IP it causes every other device in the house to lose connectivity too.
If I reboot the router (remove power cable entirely) and power it back up, the other devices return to normal except for my laptop.
It's very frustrating that this feels like a firmware bug. And I have no real ability to diagnose any further because this is a "home" router.
nggw123 This is a known incompatibility issue with Intel Wireless 9560 adapters and the RAX80. Apparently the new drivers released two days ago should fix it: https://downloadmirror.intel.com/29520/eng/ReleaseNotes_WiFi_21.90.3.pdf as a "key issue fixed": "Intel® Wireless-AC 9560 connection p to NETGEAR* Access Point Nighthawk RAX80"
I have also been experiencing this problem and have reset the router many times, downgraded the firmware, etc to no avail, only with this one laptop in my household - 10+ other devices are working perfectly fine. The new driver update appears to resolve the problem, though it typically only starts occurring for me a couple days after the latest reset.