Locked Out of Web GUI

[wy-fy]

I configured this router a few weeks ago and it's been working flawlessly. I now want to configure the parental controls and tweak a few other settings but cannot reach the web interface. When I enter the router address, 192.168.1.1, I get a message that the server dropped the connection or is not responding or otherwise cannot connect, depending on which web browser I use.

I've been scouring the internet and message boards for a solution without any luck. The closest I've come is the following thread on this forum: http://forums.smallnetbuilder.com/showthread.php?t=7417

First off, unless telnet would have been enabled by default, I don't think I would have enabled it, so that's probably not an option. The other option seems to be to reset the router. However, there seem to be two methods, one using the Reset button and the other involving the WPS button. These two procedures apparently have different effects on the router, and I'm not sure which to use. Finally, I haven't been able to find a clear description of the process of holding one or more buttons while powering the router down and then up. Or is it vice-versa?

I'm using the Asus 3.0.0.4.270 firmware.

Any help would be much appreciated.

Thanks.

 

[TonyH]

Hi,
Ping the router? Tried ipconfig /all? Tried different browser? Worst comes you can reset the router back to
factory default settings.

 

[RMerlin]

Try https://192.168.1.1:8443 (in case you might have disabled HTTP but enabled HTTPS)

Also double check your router's IP. If you run "ipconfig", see what IP you get as your Default Gateway - that should be your router.

 

[wy-fy]

Thank you for the suggestions. I've tried 3 different browsers all with the same results. The RT-N66U does respond to Ping, and ipconfig shows default gateway as 192.168.1.1. I just can't access the router interface. "HTTPS" address version also failed, but thanks the suggestion! For some reason the router won't respond to login attempts.

 

[wy-fy]

As far as a factory reset goes, should I use the Reset button or the WPS button? As I understand it, to use the Reset button technique, I'd start with the router powered off, then push the reset button and power up the router.

With the WPS button, I'd push the button while the router is powered on, then cut the power for 30-seconds, then power-up while still depressing the WPS button.

Is the above essentially correct? What state is the router in after each procedure is performed? Which would I want to use given my current situation?

Thanks again.

 

[CaptainSTX]

Are you connecting to the router by using an Ethernet cable plugged directly into a LAN port? If not unplug your router, disconnect the cable plugged into the WAN port, then plug a cable directly from your PC into a LAN port on the router.

 

[wy-fy]

Yes, I've been connected to the router by ethernet cable plugged into a LAN port.

 

[RogerSC]

As far as a factory reset goes, should I use the Reset button or the WPS button? As I understand it, to use the Reset button technique, I'd start with the router powered off, then push the reset button and power up the router.

With the WPS button, I'd push the button while the router is powered on, then cut the power for 30-seconds, then power-up while still depressing the WPS button.

Is the above essentially correct? What state is the router in after each procedure is performed? Which would I want to use given my current situation?

Thanks again.

If you power on your router with the reset button pushed in, you'll get into "recovery mode", which is used for flashing the router. This is fine if you intend to re-flash it. If you want to reset the router, just push and hold the reset button with the power turned on for maybe a count of 10.

If you do what you describe with the WPS button, this will clear the nvram.

Either of the above will require you to re-enter your router's settings.

You might try just cycling the power, and see if that gets you back in touch with your router without having to re-enter your settings, if you haven't tried that already.

 

[mikeg]

Sounds like a problem I have had before , a power off / on solved my problem with logging in to the router.

Thank you for the suggestions. I've tried 3 different browsers all with the same results. The RT-N66U does respond to Ping, and ipconfig shows default gateway as 192.168.1.1. I just can't access the router interface. "HTTPS" address version also failed, but thanks the suggestion! For some reason the router won't respond to login attempts.

 

[wy-fy]

Telnet Command?

Thanks everyone. Resetting the router and starting over was the only thing that worked.

Unfortunately, I am now back at Square 1. The router kicked me off the web interface and would not let me back in immediately after I attempted to assign a static IP address to an access point. I am fairly certain this is exactly what happened before. Has anyone else had this issue?

I can reset the router and start over again, although it seems futile at this point, because I'll just get booted out of the web interface when I try to assign the static IP. However, this time I enabled Telnet both in the router settings and on my computer, so I think I should be able to connect through telnet.

Can someone tell me what the appropriate telnet command is?

 

[wy-fy]

I've tried: "telnet //192.168.1.1 8443" along with some variants and a few of the one letter commands suggested by windows.

As close as I get is "Could not open connection to the host, on port 8443. Connect failed."

 

[TonyH]

Hmmm,
Make sure your AC adapter is good. I use neat utility called putty to access the router via
telnet. SSH, serial console, etc.

 

[RogerSC]

Yes, "putty" is good for telnet on a Windows computer.

Also, just use the default telnet port, as long as you've enabled telnet in the "Administration" -> "System" page in the router GUI, that will work.

 

[mikeg]

I have had issues with web -gui hanging , not responding when I installed it and was setting my basic values.I tried Asus , Merlins firmware with the same problem. Finallly tired , I tried the TomatoUSB Shibby and everything worked and still works fine. You will need to do the clear nvram anyway so if your problem is not solved try the Tomato....

Thanks everyone. Resetting the router and starting over was the only thing that worked.

Unfortunately, I am now back at Square 1. The router kicked me off the web interface and would not let me back in immediately after I attempted to assign a static IP address to an access point. I am fairly certain this is exactly what happened before. Has anyone else had this issue?

I can reset the router and start over again, although it seems futile at this point, because I'll just get booted out of the web interface when I try to assign the static IP. However, this time I enabled Telnet both in the router settings and on my computer, so I think I should be able to connect through telnet.

Can someone tell me what the appropriate telnet command is?

 

[linkmaster]

I've tried: "telnet //192.168.1.1 8443" along with some variants and a few of the one letter commands suggested by windows.

As close as I get is "Could not open connection to the host, on port 8443. Connect failed."

command is just telnet 192.168.1.1

Thats all you need to get the login prompt from the windows command line prompt.

 

[wy-fy]

For some reason I could not get Telnet to work. I ended up flashing to Merlin's
3.0.0.4.270.26b. Problem solved!

 

[pepemosca]

Yes, "putty" is good for telnet on a Windows computer.

Also, just use the default telnet port, as long as you've enabled telnet in the "Administration" -> "System" page in the router GUI, that will work.

In Putty just change set:
Host: 192.168.1.1
Port: 23
Connection type: Telnet

And ofcourse have the Telnet option enabled at here: http://192.168.1.1/Advanced_System_Content.asp

 

[spartan77777]

Run into this also

Run into this alost exactly the same way.
Enabled HTTPS for web access and that was it. I couldn't get any pages through https either at 443 or 8443. It offly like
Fortunately had the telnet/ssh enabled prior to this and the configuration was backed up. So, a quick ssh connection and nvram_reset command brought it back. I think there is something wrong with the HTTPS setup.
flushed it with merlin version 3.0.0.4.272.30.2.