NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Not able to login (locally) to R9000 X10
I cannot login to the Genie interface of my R9000. I get the login prompt (username:admin, password) after which the browser (tried firefox, chrome, IE) all show "transferring data from 192.168.1.1"...
It was Bitdefender's Privacy setting. I had to add the IP address to the whitelist in Bitdefender.
antinode wrote:
If your client device is configured to use some real-world DNS server
instead of a Netgear router, then you might find yourself talking to a
Netgear web server with a misleading/useless error page for your
enjoyment.
In Win10's network IPv4 settings, I have the Gateway set to the R9000 (192.168.1.1) and DNS to Cloudflare and Google (1.1.1.1 and 8.8.8.8).
Thats what ipconfig shows as well. In the router's Advanced Internet setup. I have these DNS entered as well.
Routerlogin.net is still getting resolved correctly to 192.168.1.1 (I am seeing the router's setup screens) in Win10.
How come?
> [...] DNS to Cloudflare and Google (1.1.1.1 and 8.8.8.8). [...]
> [...] Routerlogin.net is still getting resolved correctly to
> 192.168.1.1 [...]
The R9000 could be intercepting even more DNS stuff than I'd expect,
or your Windows system or web browser could be using a cached value.
What does "nslookup routerlogin.net" say?
antinode wrote:
> [...] DNS to Cloudflare and Google (1.1.1.1 and 8.8.8.8). [...]
> [...] Routerlogin.net is still getting resolved correctly to
> 192.168.1.1 [...]The R9000 could be intercepting even more DNS stuff than I'd expect,
or your Windows system or web browser could be using a cached value.What does "nslookup routerlogin.net" say?
Other browsers that I never use (IE 11) is taking me to the router when going to routerlogin.net
nslookup routerlogin.net in a command prompt (w admin priv) goes to 1.1.1.1 and then times out.
DNS request timed out.
timeout was 2 seconds.
Server: UnKnown
Address: 1.1.1.1DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
*** Request to UnKnown timed-outPS: I'm not complaining .. I would like to understand how things work.
> nslookup routerlogin.net in a command prompt (w admin priv) goes to
> 1.1.1.1 and then times out. [...]Not what I'd expect. How do you get anything to work if a basic DNS
look-up fails? What does "ipconfig /all" say about your DNS servers?Restart the Windows system? (I'm confused.)
Things are working as they are supposed to:
My nslookup is going to my chosen DNS (cloudflare's 1.1.1.1).
routerlogin.net is not in cloudflare's (or any public DNS's) lookup table. No public DNS can or should return local non-routable IP addresses in the 192.168.x.x range for any name lookup.
When I nslookup microsoft.com, I get legit response:
C:\WINDOWS\system32>nslookup microsoft.com
Address: 1.1.1.1Non-authoritative answer:
Name: microsoft.com
Addresses: 40.112.72.205
40.113.200.201
104.215.148.63
13.77.161.179
40.76.4.15The mystery is: how is routerlogin.net getting resolved to 192.168.1.1?
It has not been added to the hosts file.
The router is trapping this somehow and resolving it. It is not passing it to my selected DNS (as it indeed should not).