Reply

Re: No Admin Access in Nighthawk R7000P after ExpressVPN firmware upload

JMGV
Aspirant

No Admin Access in Nighthawk R7000P after ExpressVPN firmware upload

1- Installed ExpressVPN router firmware for Nighthawk R7000P (https://www.expressvpn.com/support/vpn-setup/app-for-routers-netgear/)

 

2- Upload was succesful and router rebooted correctly, BUT I am not able to access the administrator settings neither with routerlogin.net, 192.168.1.1 nor expressvpnrouter.com. NOTHING works.

 

3- Wifi works fine and I am able to connect through ethernet to Windows 10, but no internet and NO access to admin settings.

 

4- Tried to look for a new router address by connecting through wifi and got 192.168.132.1, could not connect to router with that address neither.

 

5- Have seen several forums using TFTP to upload netgear firmware back but I have not been able to connect to router effectively with LAN. Process detailed in attachment.

 

All I want to to og back to my original Netgear firmwaree and never mess with 3rd party firmware again!

 

Model: R7000P|Nighthawk AC2300 Smart WiFi Dual Band Gigabit Router
Message 1 of 4
antinode
Guru

Re: No Admin Access in Nighthawk R7000P after ExpressVPN firmware upload

> BUT I am not able to access the administrator settings neither with
> routerlogin.net, 192.168.1.1 nor expressvpnrouter.com. NOTHING works.

 

   "not able" or "NOTHING works" is not a useful problem description.
("NOTHING works", in particular, implies that you tried EVERYTHING,
which seems unlikely.)  It does not say what you did.  It does not say
what happened when you did it.  As usual, showing actual actions
(commands) with their actual results (error messages, LED indicators,
...) can be more helpful than vague descriptions or interpretations.

 

      https://www.expressvpn.com/support/vpn-setup/app-for-routers-netgear/

 

   Did you try "192.168.0.1"? (from a computer which is using an
address on that subnet)

 

   LED indicators?

 

   Configuring different interfaces on the computer with different IP
subnets, when you're trying to talk to one device, seems more likely to
cause confusion than to work as desired.


> [...] got 192.168.132.1, [...]

 

   "got" how?  Where?  This sounds to me like VPN stuff, which is beyond
where you'e trying to get now.

 

> [...] Process detailed in attachment.

 

   Many things are "detailed in attachment", but it's not entirely clear
how you got to those conditions.

 

   If you manually configured the Ethernet interface to use those
"192.168.1.*" addresses, but the router's now using "192.168.0.*", as
the Wireless stuff suggests, then "Destination host unreachable" is not
an amazing result.

 

   Before attempting to use TFTP to force firmware into "192.168.0.1",
I'd try pointing a web browser at that address (from a computer which
is using an address on that subnet).  And I'd stick with Ethernet, and
disable the wireless interface.

Message 2 of 4
JMGV
Aspirant

Re: No Admin Access in Nighthawk R7000P after ExpressVPN firmware upload

Thanks for your reply antinode. In attachment I have included all you requested (commmand errors, pictures, etc.)

 

In addition I have tried to connect to the following gateways:

 

192.168.1.1 --> took too long to respond

routerlogin.net --> server ip addreess could not be found

expressvpnrouter.com --> server ip addreess could not be found

192.168.0.1 --> took too long to respond

192.168.132.1 ---> took too long to respond

192.168.132.140 ----> REFUSED TO CONNECT

Message 3 of 4
antinode
Guru

Re: No Admin Access in Nighthawk R7000P after ExpressVPN firmware upload

   "ping 192.168.1.10" verifies that your computer can talk to itself.
Not a significant achievement.

 

   "ping 192.168.0.1" fails when your computer's at "192.168.1.1"
("unreachable") because it's on a different subnet.  Not amazing.

 

   "ping 192.168.1.1" should fail if the router's really at
"192.168.0.1".

 

   I have no idea why you'd try "192.168.1.X".

 

   And if "ping" fails, I'd expect TFTP to fail.

 

>    If you manually configured the Ethernet interface to use those
> "192.168.1.*" addresses, but the router's now using "192.168.0.*", as
> the Wireless stuff suggests, then "Destination host unreachable" is not
> an amazing result.

 

   Still true.


   If you go back to using DHCP for the computer's Ethernet interface
("Obtain an IP address automatically"), does it get an address in the
"192.168.0.*" subnet (from the router which is running the ExpressVPN
firmware)?

 

>    Did you try "192.168.0.1"? (from a computer which is using an
> address on that subnet)

 

   Still wondering.

Message 4 of 4
Top Contributors
Discussion stats
  • 3 replies
  • 1683 views
  • 0 kudos
  • 2 in conversation
Announcements

Orbi WiFi 6E