NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
justinl
Jul 08, 2017Guide
R7500 not assigning correct IP addresses to wireless clients after firmware upgrade
I just updated my Nighthawk X4 R7500 to the latest available firmware, V1.0.0.108, and wireless clients no longer receive the correct IP address assignments after they connect to the 5.0 GHz wireless...
- Sep 09, 2017
I just upgraded to the latest R7500 firmware, V1.0.0.110. This appears to have resolved the issue, although NETGEAR does not include this fix in the release notes for this firmware upgrade.
If you were affected by this issue, I recommend you install V1.0.0.110. You may need to download the firmware update directly from NETGEAR's website; when I attempted to update the firmware through the router's interface, the firmware update page refreshed constantly and indefinitely, never finding the available update.
Feyroce
Jul 19, 2017Aspirant
Same issue on my side :-(
After resetting the router, it is sometimes working but just a few hours...
On my smartphone, after a reset I'm able to connect to the wlan but when I'm coming back home after my working day ... no way, I have to reset the router once again :-((
justinl
Jul 20, 2017Guide
Hi Feyroce,
I am not sure we have the same issue. It sounds like your smartphone might not be receiving any IP address at all, leading to no WLAN connectivity. After upgrading to V1.0.0.108 of the firmware on my R7500, IP addresses are still assigned to my wireless clients, but the addresses that get assigned are in the DHCP range rather than the static addresses that I have configured for my wireless devices, based on their MAC addresses.
For example, I have assigned my iPhone the address 192.168.0.60, but the R7500 gives it the address 192.168.0.101, which is the first address in the DHCP range I configured.
JamesGL, this behavior happened only *after* a firmware upgrade (to V1.0.0.108) and the firmware upgrade reset the router configuration. I had to reconfigure it from scratch. It seems unlikely that a second reset would resolve the issue. But, I appreciate the initial assistance.