A friend has a Netgear Nighthawk AX1800 RAX20-100NAS WiFi 6 router that I can’t get to the administrative web interface of. The router is connected (by Ethernet cable) to their cable modem. I’ve tried multiple browsers from Windows (WiFi and Ethernet), Linux (WiFi and Ethernet) and Android devices and it the page always times out, regardless whether I use just the bare IP address, routerlogin.net, www.routerlogin.net, with or without http or https. All the devices I’m using have Internet access and I can ‘ping’ the router by IP address. And I have tools on my Android tablet (which is logged in as a WiFi client to that router) that confirms the router’s IP address is 192.168.1.1, so I’m certain I have connectivity.
It was me set this router up initially and all I changed from stock was to match the SSID and the WiFi password to what they had been using previously so the change would be transparent to the users. That much worked to their satisfaction and they’ve had no complaints.
Now I need back in to update the firmware and make some changes to support a new access point on the other end of the house, but I can’t get the administrative web interface to load. If it were my call I’d do a factory reset and rebuild it but one member of the household who telecommutes has veto authority and won’t allow it.
I have Netgear’s Nighthawk app installed on my Android tablet but haven’t had opportunity to try it. That might give me the ability to control that router, but controlling the router isn’t the only problem. If only for academic reasons, I need to figure out why I can’t get that web interface to load. It’s too weird of a problem not to run down the cause.
Something else I should mention is I don’t recall that ever I accessed the web interface after the configuration changes I made before putting the router into service. I configured it, plugged it in, let it boot, asked the users to try to reconnect and test Internet throughput, then I called it a day. Not that I think the device is faulty but I can’t say to a certainty this isn’t a problem with the router itself, like some manner software glitch, dating back to my original set-up.
So what should I have done that I haven’t mentioned? The last time I ran a Netgear router of my own it was a G-band, so it was quite some time ago and the Netgear interface has changed dramatically since then. So I’m open to the possibility that this is all user-error (= my screw-up).
