NO ACCESS TO NIGHTHAWK D7000 V1 MANAGEMENT PAGE
As the D7000 has no fiber optic connection, I had to set up my 2018 NETGEAR D7000 Nighthawk modem/router behind a Movistar ISP provided Askey RTF3505VW (HGU) Fiber Optic router via ethernet cable. PC with OS WIN10 1809 x64.
WIFI and USB work ok but it is impossible to get access to the D7000 configuration page to disable DHCP or change network channel, although my PC is connected directly to the D7000 via ethernet cable.
Using routerlogin.net, either exclusively via ethernet or the D7000 WIFI network, I always get a message saying 'no access because not connected to the D7000 WIFI network'?!
Using 192.168.1.1 or 192.168.0.1 either exclusively via ethernet or the D7000 WIFI network I get the message ‘this site can’t be reached; connection refused’.
When using Genie on either LAN or WIFI network I get a message saying 'Netgear Router not found'.
I already changed the primary Askey RTF3505VW (HGU) router IP to different from 192.168.1.1 but to no avail.
What`s going on and how do I get access to the D7000 configuration page?
Re: NO ACCESS TO NIGHTHAWK D7000 V1 MANAGEMENT PAGE
> [...] it is impossible to get access to the D7000 configuration page
"impossible" may be too strong. "I have not found a way" might be
> Using routerlogin.net, either exclusively via ethernet or the D7000
> WIFI network, I always get a message saying 'no access because not
> connected to the D7000 WIFI network'?!
I'd expect the "routerlogin" names to work on a device which is
connected directly to the D7000[v1]. But welcome to what may be the
worst error message in the world. For an explanation, try:
Briefly, the idea is that "[www.]routerlogin.net" (or ".com") should
point to your own router, but that's true only if you use your own
router for DNS name resolution. (Or, if the Netgear router can
intercept your DNS queries.) Regardless, you should be able to get to
the thing using its IP address, if you can determine (or guess) that.
Normally, that would be something like "192.168.0.1", but it could be
different. ("10.0.0.1" is a typical alternate, for example.)
If you connect the WAN/Internet port of the D7000 to another router
(like your Askey RTF3505VW), which is already using "192.168.1.*"
subnet, then I'd expect the D7000 to shift to "10.0.0.1" (using
"10.0.0.*" as its LAN subnet).
Generally, cascading multiple routers causes problems. If the
RTF3505VW can be configured in a modem-only ("bridge") mode, then you
could use the D7000 as your only router. Otherwise, you might want to
configure the D7000 as a wireless access point, leaving the RTF3505VW as
your only router.
If you configure the D7000 as a WAP, then it will get (yet another)
different LAN IP address, but if your main router (RTF3505VW) provides
something like what Netgear calls an Attached Devices report (or a DHCP
clients report), then the D7000-as-WAP should appear there.