NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
StElmoQn
Feb 03, 2017Aspirant
Need Help after Factory Reset on NIghthawk Router
Had to physically relocate my desk and computer components yesterday and now for some reason my wired ethernet connection is shot. I can still log on wirelessly and my ISP walked me through many ste...
- Feb 09, 2017
StElmoQn wrote:
I prefer to run the modem as a bridge and use my Nighthawk as the true router. That being said, what exactly will be the setup?
... and then the NIghthawk and the CenturyLink modem are connected from LAN port to LAN port.
Connecting the modem to a Nighthawk LAN port only works if the modem is routing. A LAN port from the CenturyLink modem needs to be connected to the Nighthawk's Internet port.
Note that you can connect it up this way and get it working even if the modem isn't in bridge mode. Some advanced functions (particularly port forwarding) become more difficult. But you should be able to get internet connections up and running. If routerlogin.net fails to connect, try switching over to 192.168.1.1.
Then you can switch the modem to bridge mode as a second step.
Note that if the modem is also providing cable TV services there might be some loss of services when switching to bridge mode. I don't think that will be an issue with CenturyLink, but you might want to confirm that. My own ISP (Verizon FIos) uses their router to provide the program guide, video on demand, and some DVR services. So I use my Netgear router behind theirs (double-routing). So it is possible to leave the modem in router mode if that is necessary.
StephenB
Feb 08, 2017Guru - Experienced User
http://www.routerlogin.net
LeeH wrote:
It looks like your wired connection is to the modem running in router mode 192.168.0.2.
I agree, and that is what I wanted to check. Note I specifically asked for the laptop to be connected to the modem ethernet for this test.
Also, this confirms that the Nighthawk's current IP address is 192.168.1.1 Even if http://www.routerlogin.com. or http://www.routerlogin.net fail, you should be able to reach the Nighthawk's login screen using http://192.168.1.1
LeeH wrote:
You need to tell your ISP to configure your modem in bridge mode...
That is one option.
You can also switch the Nighthawk router over to AP mode, and leave your modem alone.
There are instructions here: https://kb.netgear.com/24104/How-do-I-change-my-Nighthawk-router-to-AP-mode-after-I-ve-already-run-setup
After it's in AP mode, it will have a 192.168.0.x address. You'll need to log into the modem router (http://192.168.0.1) to see that address, and to manage routing functions (like port forwarding).
StElmoQn
Feb 08, 2017Aspirant
Stephen and Lee,
Thanks for the diagnosis.
I prefer to run the modem as a bridge and use my Nighthawk as the true router. That being said, what exactly will be the setup?
My docking stations (Targus ACP71USZ 3.0 USB) currently has the ethernet connected to the internet port of the Nighthawk, and then the NIghthawk and the CenturyLink modem are connected from LAN port to LAN port. Of course the DSL line is going into the modem. Is this how the set up should remain for a wired ethernet connection or should the ethernet go from the Targus dock to the modem?
Please advise and I will get back into touch with my ISP to get this done and dusted.
Many many thanks to you both.
- StElmoQnFeb 08, 2017Aspirant
Just tried logging into the router at http://192.168.1.1 and get error message that the computer appears to be correctly connected but device is not responding.
Now what????
- StephenBFeb 09, 2017Guru - Experienced User
StElmoQn wrote:
I prefer to run the modem as a bridge and use my Nighthawk as the true router. That being said, what exactly will be the setup?
... and then the NIghthawk and the CenturyLink modem are connected from LAN port to LAN port.
Connecting the modem to a Nighthawk LAN port only works if the modem is routing. A LAN port from the CenturyLink modem needs to be connected to the Nighthawk's Internet port.
Note that you can connect it up this way and get it working even if the modem isn't in bridge mode. Some advanced functions (particularly port forwarding) become more difficult. But you should be able to get internet connections up and running. If routerlogin.net fails to connect, try switching over to 192.168.1.1.
Then you can switch the modem to bridge mode as a second step.
Note that if the modem is also providing cable TV services there might be some loss of services when switching to bridge mode. I don't think that will be an issue with CenturyLink, but you might want to confirm that. My own ISP (Verizon FIos) uses their router to provide the program guide, video on demand, and some DVR services. So I use my Netgear router behind theirs (double-routing). So it is possible to leave the modem in router mode if that is necessary.
- StElmoQnFeb 09, 2017Aspirant
Connecting the modem to a Nighthawk LAN port only works if the modem is routing. A LAN port from the CenturyLink modem needs to be connected to the Nighthawk's Internet port.
Stephen!
Just correcting this connection FIXED my problem! I now have the ethernet cord from the Targus docking station going into a LAN port, and the Century Link modem is now connected to the Nighthawk internet port. Immediately the wired ethernet connection returned and I can log into my router again!
Thank you so very much for all of your help!!!
- StElmoQnFeb 09, 2017Aspirant
One last question...I promise!
I know I need to go back in and change the name of my wireless network back after doing a factory reset on the Nighthawk, but I wondered if there is also a way to changed the name of the wired network from NetgearXX to something else?
- StephenBFeb 09, 2017Guru - Experienced User
StElmoQn wrote:
, but I wondered if there is also a way to changed the name of the wired network from NetgearXX to something else?
My Windows systems actually don't name the wired network itself. But if wifi is enabled, they still use the wireless network name, with the both the wifi connection and "local area network" listed.
So if the wifi network is called NetgearXX, all you should need to do is change the wifi network name (and of course update the connection info on the PCs and other clients).