NETGEAR router is not found or is not supported.

Hello guys, I'm having a hard time right now. I bought the NightHawk AC1900 R7000 to install a VPN on it. I installed the VPN showed in this video '' https://www.youtube.com/watch?v=FVLQzsCxwgI '' an...

Firmware

Troubleshooting

raven_au
Dec 07, 2016
That 192.168.0.20 looks wrong.

There are often problems coming back from dd-wrt to stock firmware and it's often difficult to find what you need to do on the dd-wrt forums.
The problem might be dd-wrt leaving conflicting NVRAM settings, you should have set the router back to factory defaults in dd-wrt before loading the firmware.
Even so the NVRAM settings can still conflict requiring they be erased before things will work properly.

I don't know if the Netgear tftp firmware update procedure will also erase NVRAM when the firmware is uploaded, a Netgear person will need to answer that one.
But if it does that could be a way to resolve the problem too.

You could try making sure no other devices are using DHCP assigned addresses by, perhaps, turning them off (so that there won't be a possible duplicate address).
But then the router appears to have an incorrect DHCP address range set so this might not be a problem at all, better to be safe though.

Then set your computer's address manually to one that is in the range 192.168.1.2-254, probably over 200 is better in case there ends up being a duplicate address on the network, as the higher addresses are less likely to be assigned by the DHCP server in the router.
For the subnet mask use 255.255.255.0 , as usual, and the gateway 192.168.1.1, and DNS 192.168.1.1, as it is in the above post.
If the router has an address of 192.168.1.1 (and it appears it does from the above post) then your computer with address 192.168.0.(anything) will not be able to communicate with the router or anything else in the 192.168.1 network. That's the point of setting the address manually.

Then try to connect to 192.168.1.1 in a browser and see if it works.

HavingBigProbs
Aspirant
Dec 07, 2016
ElaineM : i still can communate with my router
It's in french, if you need other info just tell me

IrvSp :
Carte Ethernet Connexion au réseau local :
Suffixe DNS propre à la connexion. . . :
Description. . . . . . . . . . . . . . : Realtek PCIe FE Family Controller
Adresse physique . . . . . . . . . . . : 00-1E-33-C9-45-A6
DHCP activé. . . . . . . . . . . . . . : Oui
Configuration automatique activée. . . : Oui
Adresse IPv6 de liaison locale. . : fe80::ad7f:d59a:a48c:c5bc%10(préféré)
Adresse IPv4. . . . . . . . . . . : 192.168.0.20(préféré)
Masque de sous-réseau. . . . . . . . . : 255.255.255.0
Bail obtenu. . . . . . . . . . . . . . : 6 décembre 2016 19:55:14
Bail expirant. . . . . . . . . . . . . : 7 décembre 2016 19:55:13
Passerelle par défaut. . . . . . . . . : 192.168.1.1
Serveur DHCP . . . . . . . . . . . . . : 192.168.1.1
IAID DHCPv6 . . . . . . . . . . . : 167779891
DUID de client DHCPv6. . . . . . . . : 00-01-00-01-18-16-92-AC-00-1E-33-C9-45
-A6
Serveurs DNS. . . . . . . . . . . . . : 192.168.1.1
NetBIOS sur Tcpip. . . . . . . . . . . : Activé
Carte Tunnel Connexion au réseau local* 6 :
Statut du média. . . . . . . . . . . . : Média déconnecté
Suffixe DNS propre à la connexion. . . :
Description. . . . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Adresse physique . . . . . . . . . . . : 02-00-54-55-4E-01
DHCP activé. . . . . . . . . . . . . . : Non
Configuration automatique activée. . . : Oui

Is the first one a bit too different?
- HavingBigProbs
  Aspirant
  Dec 07, 2016
  I tried reaching the website with a different browser and cleared the cache it stills Times out
  - raven_au
    Virtuoso
    Dec 07, 2016
    That 192.168.0.20 looks wrong.
    
    There are often problems coming back from dd-wrt to stock firmware and it's often difficult to find what you need to do on the dd-wrt forums.
    The problem might be dd-wrt leaving conflicting NVRAM settings, you should have set the router back to factory defaults in dd-wrt before loading the firmware.
    Even so the NVRAM settings can still conflict requiring they be erased before things will work properly.
    
    I don't know if the Netgear tftp firmware update procedure will also erase NVRAM when the firmware is uploaded, a Netgear person will need to answer that one.
    But if it does that could be a way to resolve the problem too.
    
    You could try making sure no other devices are using DHCP assigned addresses by, perhaps, turning them off (so that there won't be a possible duplicate address).
    But then the router appears to have an incorrect DHCP address range set so this might not be a problem at all, better to be safe though.
    
    Then set your computer's address manually to one that is in the range 192.168.1.2-254, probably over 200 is better in case there ends up being a duplicate address on the network, as the higher addresses are less likely to be assigned by the DHCP server in the router.
    For the subnet mask use 255.255.255.0 , as usual, and the gateway 192.168.1.1, and DNS 192.168.1.1, as it is in the above post.
    If the router has an address of 192.168.1.1 (and it appears it does from the above post) then your computer with address 192.168.0.(anything) will not be able to communicate with the router or anything else in the 192.168.1 network. That's the point of setting the address manually.
    
    Then try to connect to 192.168.1.1 in a browser and see if it works.
- IrvSp
  Master
  Dec 07, 2016
  HavingBigProbs wrote:
  Adresse IPv4. . . . . . . . . . . : 192.168.0.20(préféré)
  
  Is the first one a bit too different?
  Sure is...
  
  It is possible that the PC is retaining the address it had when DD-WRT was installed. Did you re-boot the PC after going from DD-WRT to NG flash? If not, that could fix it. Otherwise try DISABLING the Network Adapter and ENABLING it. That might work.
  
  Possible the PROPERTIES of the Network Adapter was SET to 192.168.0.20 too, if so, you need to change that to 192.168.1.20 and that too will fix it.
  
  You could also go to DEVICE MANAGER and DELETE the NETWORK ADAPTER and then under ACTIONS SCAN FOR H/W changes, that should fix it as well.
  - HavingBigProbs
    Aspirant
    Dec 07, 2016
    raven_au : Ok there was a big change here but it still won't work. I tried what you said and it brought me to the Netgear installation site. It told me to change the Wifi network name and put a password. Then they got me to put a password to my username : admin to get access to the 192.168.1.1 . After that they told me that some firware wasn't up to date so I downloaded it. When I tried to access to the 192.168.1.1 site it would now say that thw website is not accessable, 192.168.1.1 won't autorise connexion. Wich is different from before where they told me the connection was timed out. My router now has a Wifi Network with internet ON .
    
    IrvSp : I will try what you are saying in a moment.

Forum Discussion

NETGEAR router is not found or is not supported.