01-18-2012 07:36 AM
I manually set up my E4200 (v1 hardware, v1.0.03 firmware) months ago ago and it was working perfectly. My wired and wireless PCs connected to the Internet perfectly. I logged in to the browser-based utility occasionally when I needed to upgrade the firmware or my DSL flaked out and I needed to reboot the E4200. My problem is now I cannot log in to the browser-based utility. Internet connectivity is fine. I have made no configuration changes. When I connect to the URL I get the Certificate Error message "There is a problem with this website's security certificate.", which is normal. I then click on the "Continue to this website (not recommended)." link. It would normally ask me to login. Now it simply displays the "cannot display the webpage" error. I hit the Factory Reset button and that reset the configuration enabling me to login to the browser-based utility. I then reloaded my .CFG file which contains the good configuration I saved when I could connect to the browser-based utility. Afterwards I could not connect to the browser-based utility. I tried the Factory Reset button again and re-flashed the v1.0.03 firmware, then reloaded my .CFG file. Same result. Does anyone have any suggestions? Could this be a hardware failure? It doesn't make any sense to me that software would suddenly stop working with no change in configuration. (I have over 30 years experience in the IT industry, so I know some of you will be skeptical of the claim that "I didn't change anything." But really, I didn't change anything.) Thanks.
Solved! Go to Solution.
01-18-2012 03:29 PM
Hello, I also have this problem when on Windows 7 using Chrome 16 and Internet Explorer 9 and the admin web interface is configured to use https. Firefox 9 seems to work though. My iPad seems to work as well (iOS 5, Mobile Safari, with wireless access to admin web gui on). Also E4200, v1 hardware, 1.0.03 firmware.
Although when I finally get to the https interface it is slooooooooow.
01-19-2012 05:29 PM
Which windows you are running in your computer? Let me know which browser you are using? Try the following the following:
Click "Safety" on the Command bar
Select "Delete Browsing History"
Select the option for cookies and click Delete
Alternatively, Internet Explorer 8's new InPrivate browsing feature allows users to browse the internet without recording information from visited sites (including cookies). To use InPrivate mode:
Click "Safety" on the Command bar
Select "InPrivate Browsing"
After doing the following steps check whether it loads the Web based setup or not...
01-19-2012 05:47 PM
I hate to take a simplistic approach to this, but if your .cfg file is not working for you, stop using it. Reset your router and configure it carefully by hand. I would also not switch your web interface to https until I had it working on http, and let that be the only change that you make at that point. If it works with http, and you switch it to https, and it stops working, then I'd get hold of Linksys support and tell them about your problems and see if they have any help for you. Personally, I tried https, too, since I like it and expect it to work. Even though it did work, it was too slow to stay with it, so I switched back to http. There is some problem there, but I haven't experienced it not working at all. So I'm wondering if something corrupted your .cfg file somehow...
02-03-2012 07:20 PM
I tried both of the solutions offered by the two generous posters here and neither worked. Today the radio in the router failed. I exchanged the router for a new one, and happened to get an E4200v2. It had firmware 2.0.26. I manually configured it (but kept administration to HTTP only, not HTTPS). After it rebooted I suffered the same symptoms as described in the original post (without the certificate error). I went through several factory resets and manual configurations before I discovered what was happening. After saving my configuration and rebooting, the IP address of the router was changed to 10.x.x.x. It should have been 192.168.2.1, which explains why I could not connect to the "console". I upgraded the firmware to 2.0.36 and started from scratch again. Again the change to the private 10 network. I am firmly convinced that the configuration I am entering is causing buggy code in the router to be executed when it saves the configuration, resulting in unwanted changes to the configuration. It is reproducable on my router, so I'm fairly certain it can be reproduced in the lab. I will gladly communicate the specifics of this situation with a Cisco engineer so that the bug can be fixed. I just don't know how to start the conversation.
04-16-2012 07:10 AM
Any solution to this problem? I have the same fault and the router used tp allow remote administration over https previously but now it rejects it. I have added a security exception in the browser but still no connection. When I look at the faulty (?) certificate I note that is has its local IP as CA name.. if it matters..
Quite annoying! I really need to access it remotely.
04-19-2012 03:36 PM - edited 04-19-2012 03:42 PM
I have seen the same behaviour: not being able to login to the browser console (default at 192.168.1.1) while the router is functioning fine, all PC's are online and you are able to ping the router both on ipaddress and netbios name.
Reading this thread: I remember also to have increased the security level by restricting the console to "HTTPS only" some weeks ago (by unchecking "HTTP".) This behaviour appears on W7, 64bit with IE9, but also with Chrome and Firefox.
The solution (in my case) was simple:
Connect a / or walk over to a WindowsXP machine in your network (with IE7 or IE8).
connect to the browser console (default: HTTPS://192.168.1.1).
Provide your admin and credentials
And voila you are in,
Next, configure the router to also allow HTTP, (to improve security uncheck the abilty to connect to the console via WLan)
Apply the changes and you are done.
(If you walk over to your W7 IE9 machine you will notice that you are able to login again).
Hopefully this will work for you just as it did for me.
PS If you use HTTPS your browser will complain about an unvalid certificate, this is correct as this is a (sort of) SelfSigned certificate not being provided by Trusted Third Party (Verisign / Digicert etc.). Since you are making the connection to this source in your own home, which you trust, it is fine to ignore the warning and proceed to the console.
04-24-2012 03:38 PM
OMG you just saved eight hours of my time. Seriously I had exactly the same problem and was just going to do a hard reset and reconfigure everything - I unfortunately misplaced my backup file. I have about 15 devices using the router so this will be a very lengthy process. I can't believe it's this easy - just use IE 6 on WinXP! This certificate thing breaks down the communication with the new browsers. It's just stupid. Thanks for sharing.