Cannot access router login

[skunkmunkey]

Before I have to go ahead and do a factory reset and lose all my settings and ports etc, does anyone have any suggestions how to access my router when the standard 192.168.0.1 etc won't work? My internet and wifi are working fine and I can ping the router and it's showing correctly on ipconfig. When I try accessing it I just get a message saying the page isn't working. Rebooting doesn't make any difference.

 

The router is a Netgear AC1600a and the firmware was up to date as of a couple of months ago

[Oshino Shinobu]

Try clearing your browser cache or using a different browser. Can you access it from other devices?

[kirashi]

8 minutes ago, skunkmunkey said:

Before I have to go ahead and do a factory reset and lose all my settings and ports etc, does anyone have any suggestions how to access my router when the standard 192.168.0.1 etc won't work? My internet and wifi are working fine and I can ping the router and it's showing correctly on ipconfig. When I try accessing it I just get a message saying the page isn't working. Rebooting doesn't make any difference.

 

The router is a Netgear AC1600a and the firmware was up to date as of a couple of months ago

Run ipconfig /all to verify your default gateway, then try to connect again using multiple browsers. I've had cases where Firefox stops loading the login page but Chrome works fine, and vice versa, usually due to session cookies used to store your login session. If that doesn't work, reboot your PC and the router, then try again. If that doesn't work, factory reset your router and try again.

 

If after all this you still cannot load the page from multiple devices trying multiple web browsers, and you're 100% sure you have the actual IP of the router (and your PC is getting assigned an IP properly too), contact the manufacturer for warranty replacement. If our of warranty, replace the router.

[skunkmunkey]

I'd tried clearing the cache and accessing it from other devices with no luck.

 

Just tried Edge **shudders** and got in fine.

 

Thank you

 

[Oshino Shinobu]

1 minute ago, skunkmunkey said:

I'd tried clearing the cache and accessing it from other devices with no luck.

 

Just tried Edge **shudders** and got in fine.

 

Thank you

 

Wondering when you say reboot, do you mean the router or PC? If you haven't already, clear all data for the router's address from the browser, completely close the browser down and then reboot. 

 

You could try ipconfig /flushdns as well, just in case. 

 

It's pretty much certainly cached or local data for the broswer(s) if it's working through Edge.

[skunkmunkey]

I've restarted multiple PC's and the router and flushing the DNS but it's still not working in Chrome but is in Edge. 

 

Cleared the cache and local data etc and it's still not working in Chrome. At least I'm in now and can do what I wanted

[skunkmunkey]

Have just found this;

https://community.netgear.com/t5/DSL-Modems-Routers/GOOGLE-CHROME-ERROR-PAGE-DUE-TO-NULLS-IN-HEADER-OF-ROUTER/td-p/1701839

 

Seems it's Netgears fault and their practices don't meet the standards for the latest version of Chrome. It works for now in other browsers but no way to tell how long for before they're updated too. Seems Netgear are chossing to ignore the problem.