Problem accessing Netgear router login page from Windows 10

My home router is an admittedly ancient (but still works) Netgear WGR614v9.

On rare occasions typically when someone in the family has a new device to which I need to give access, I'll go to routerlogin.com which is the web page Netgear has to administer the router. I don't believe I've used that page though under Windows 10, to which I just converted at home in January.

When I went to it with Firefox, my default browser, it dumped me to Router login - instead of the login page.

This had never happened before. I tried a few times to refresh the page, then cleared cookies and cache, and still no luck.

I finally used the Edge browser and had no problem.

So this could be a Firefox problem (I'm running FF 75.0, 64-bit), but I'll first try here to see if it's a Window problem.

It sounds like a Firefox name resolution problem.

Open a command prompt and type: ipconfig /all.

Scroll down until you find the IP address for your Default Gateway.

Type this IP address into the Firefox address bar and Firefox should take you to the router login page.

JackHughs

JackHughs said:

It sounds like a Firefox name resolution problem.

Open a command prompt and type: ipconfig /all.

Scroll down until you find the IP address for your Default Gateway.

Type this IP address into the Firefox address bar and Firefox should take you to the router login page.

JackHughs

Thanks. This did the trick. Although I am wondering why this sudden name resolution problem, and just for that web page, and just with my Firefox browser.

Windows contains a "Hosts" file which records the IP addresses of frequently visited sites. You type a site name into the address bar and the browser first goes to the Hosts file to find the IP address. Browsers screw-up, Host file entries get corrupted, and so on.

You can edit entries in the Host file so that a site name is once again associated with the proper IP address. Instructions on how to do this are readily available on the internet. Howeveer, since Edge works with the site name, the problem may be in FIrefox. Personally, I'm lazy so I would just be happy with being able to access the routers log-in page.

JackHughs