cannot reach router's GUI

[pdoyle]

RT-N66R now won't allow access to GUI at 192.168.1.1; though we still have internet connection. Download Master GUI is accessible. Might be related to shutting off circuit breaker in house yesterday...this has happened before. I've shut off Norton firewall ...cleared cache in firefox, tried explorer too. unplugged router. i've tried wireless , and also wired connection. I'd rather not have to reset from factory settings...plus, this shouldn't be happening 2 months in a row. The firmware was released in the spring 2015 and is the latest, other than the beta release from Asus. Any ideas? thanks!

 

[pdoyle]

RT-N66R now won't allow access to GUI at 192.168.1.1; though we still have internet connection. Download Master GUI is accessible. Might be related to shutting off circuit breaker in house yesterday...this has happened before. I've shut off Norton firewall ...cleared cache in firefox, tried explorer too. unplugged router. i've tried wireless , and also wired connection. I'd rather not have to reset from factory settings...plus, this shouldn't be happening 2 months in a row. The firmware was released in the spring 2015 and is the latest, other than the beta release from Asus. Any ideas? thanks!

I've also released and renewed the pc's IP address...and Asus Device Discovery shows router still at 192.168.1.1, same subnet mask and SSID; selecting Configure brings 'Settings have been updated. Web page will now refresh.
Changes have been made to the IP address or port number. You will now be disconnected from RT-N66R.
To access the settings of RT-N66R, reconnect to the wireless network and use the updated IP address and port number.'

 

[netwrks]

With your device directly connected to router and keying in ipconfig from a DOS prompt, what IP Address does your device get?

 

[L&LD]

Did you close your browser (and cleared it's cache)?

 

[pdoyle]

With your device directly connected to router and keying in ipconfig from a DOS prompt, what IP Address does your device get?

192.168.1.239 subnet mask of 255.255.255.0 192.168.1.1 gateway

Yes, I cleared cache and restarted both firefox and explorer

 

[pdoyle]

Did you close your browser (and cleared it's cache)?

Yes, I cleared cache and restarted both firefox and explorer

 

[L&LD]

Just noticed you're running an old version of the firmware.

May want to try the latest available.

http://support.asus.com/download.aspx?slanguage=en&m=RT-N66U+(VER.B1)&os=8

 

[pdoyle]

Just noticed you're running an old version of the firmware.

May want to try the latest available.

http://support.asus.com/download.aspx?slanguage=en&m=RT-N66U+(VER.B1)&os=8

seems rt-n66U and rt-n66R have different firmware version labels...i bought this at Best buy, i thought I had the rt-n66R?
plus how can I upload if I cannot access the GUI?

 

[netwrks]

seems rt-n66U and rt-n66R have different firmware version labels...i bought this at Best buy, i thought I had the rt-n66R?
plus how can I upload if I cannot access the GUI?

Looks like the only way to resuscitate your router will be to do a factory reset. Chances are, some part of you FW may be corrupted.

 

[L&LD]

seems rt-n66U and rt-n66R have different firmware version labels...i bought this at Best buy, i thought I had the rt-n66R?
plus how can I upload if I cannot access the GUI?

RT-N66U and RT-N66R use the same firmware. The 'r' model is simply used by bestbuy to prevent price matching.

 

[pdoyle]

maybe I will also use the latest firmware even though it's beta...i read some warnings from other users about using this latest beta version.
can I then upload my .cfg setttings file? or might that be affected by the corrupted FW as well?

 

[L&LD]

Whenever you upgrade firmware, using a cfg file is not recommended. Especially when you're already experiencing problems.

Reset the router using the reset button on the back after you have unplugged all USB devices.

Flash the firmware and using the GUI, reset to factory defaults and do at least one hard reboot (pull the power plug and wait a minute or so).

Now, manually and minimally configure the router to secure it and connect to your ISP.

I would also use a different ssid too at this point.

Hope this solves the issues for you.

 

[netwrks]

maybe I will also use the latest firmware even though it's beta...i read some warnings from other users about using this latest beta version.
can I then upload my .cfg setttings file? or might that be affected by the corrupted FW as well?

That would be hard to tell, what exactly is broken? (FW or config). Curious why you would consider a beta version that could give you additional grief.

 

[wh7qq]

I've seen this kind of behavior in the past and the only solution has been to get rid of the windows network configuration and start over from there. Windows doesn't behave nicely with this kind of network disruption and even linux sometimes requires a new network configuration. It may not be a firmware problem at all. Clear your windows network connection, reboot the PC and start over again before yougo to the trouble of doing the firmware upgrade.

 

[pdoyle]

I've seen this kind of behavior in the past and the only solution has been to get rid of the windows network configuration and start over from there. Windows doesn't behave nicely with this kind of network disruption and even linux sometimes requires a new network configuration. It may not be a firmware problem at all. Clear your windows network connection, reboot the PC and start over again before yougo to the trouble of doing the firmware upgrade.

by " clearing windows network connection"; do you mean, clear usernames and passwords for accessing the router?

 

[pdoyle]

using a different SSID would in effect remove the windows connections and configuration settings, correct? I'd have to change all three SSIDs; 2.4 GHz, 5ghz, and guest network.

 

[pdoyle]

That would be hard to tell, what exactly is broken? (FW or config). Curious why you would consider a beta version that could give you additional grief.

agreed.
What's broken, as far as I know, is just that I cannot access the GUI; so I cannot control the router. we still have internet connectivity. So I could not install a firmware upgrade if I wanted to.

 

[wh7qq]

by " clearing windows network connection"; do you mean, clear usernames and passwords for accessing the router?

I mean going into the Windows "Network Connections" menu and deleting the connection to the router and starting from scratch (reboot PC first) by creating a new network connection, just like when the computer was new. The router username and password are not affected by this as these are stored in the router's NVRAM but you often can rediscover these from the saved username and password in your browser, if you have previously saved them there.

When you create a new network connection, you should be able to access 192.168.1.1 and you will have to enter your username and password to open the router web interface. On the other hand, if you do a hard reset on your router (as would be a good idea), you should be able to get in using the router's default username and password. BTW, dump your old router cfg files as they will just get you back into trouble if you get lazy and try to use them.

All of the above should be performed with nothing other than a single PC connected to a LAN port on the router. Once you have gotten that connection squared away, the router's DHCP should be able to access the WAN when you connect it.

 

[pdoyle]

I mean going into the Windows "Network Connections" menu and deleting the connection to the router and starting from scratch (reboot PC first) by creating a new network connection, just like when the computer was new. The router username and password are not affected by this as these are stored in the router's NVRAM but you often can rediscover these from the saved username and password in your browser, if you have previously saved them there.

When you create a new network connection, you should be able to access 192.168.1.1 and you will have to enter your username and password to open the router web interface. On the other hand, if you do a hard reset on your router (as would be a good idea), you should be able to get in using the router's default username and password. BTW, dump your old router cfg files as they will just get you back into trouble if you get lazy and try to use them.

All of the above should be performed with nothing other than a single PC connected to a LAN port on the router. Once you have gotten that connection squared away, the router's DHCP should be able to access the WAN when you connect it.

Will do. Will let y'all know layer tonight... Thanks big time for the help!! I now have hope

 

[TonyH]

Will do. Will let y'all know layer tonight... Thanks big time for the help!! I now have hope

Tried to ping 192.168.1.1?