NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.

Forum Discussion

dualsweat's avatar
dualsweat
Aspirant
Oct 05, 2015
Solved

Nighthawk R7500 Slow WebUI

Hi All,                 I recently purchased "2" Nighthawk x4 R7500 Routers to replace "2" WNDR3700's. I upgraded both of the R7500's with the latest firmware (1.0.0.94), and also performed the h...
Troubleshooting
  • Babylon5's avatar
    Babylon5
    Oct 07, 2015

    Can I ask what the DHCP range of router 1 is set to? This would normally start at 192.168.1.2?

     

    Personally, I set all my static IPs at the end of the DHCP range, e.g. I set DHCP to end at address 99, and then set static IPs at easy to remember numbers – say increments of 10.

     

    It might be worthwhile setting the static IP of Router 2 to a much higher number, using the method that TheEther has suggested (which may also need a factory reset or a static IP at the PC since Router 2 is not configured as a DHCP server).

Babylon5's avatar
Babylon5
NETGEAR Employee Retired
Oct 09, 2015

I don’t think Matt has access to the UI (Post 8), so can't get to the UI page where the save settings option lives.

 

Matt, if you set a static IP address at the PC on the same subnet as your LAN e.g. 192.168.1.111 Subnet mask 255.255.255.0, all other IPs don’t care – leave blank. Then connect by Ethernet to Router1 with nothing else connected i.e. off your LAN, can you access the router at http://192.168.1.1 ?

 

If that still fails try changing the PC IP to 10.0.0.111, I’m thinking that possibly the router has automatically changed its LAN subnet to avoid a conflict, depending on how you initially set it up.

dualsweat's avatar
dualsweat
Aspirant
Oct 09, 2015

Hi All,

 

          Thank you for all the tips. Before I did the reset I tried using the power button on the back of the router and powercycled router1. This had no impact and the WebUI still didnt work completely. I let the router sit for a couple hours (because I was working and couldnt do the reset right at that moment). A couple hours later I decided to completely unplug the router from the wall and try again. And, success! I dont know what the difference is between using the power button and completely unplugging the router, but it seems something got "unstuck" by doing it that way.

 

           Problem solved - case closed!

 

Thanks Again,

 

Matt M.--------