04-06-2012 11:06 PM
04-07-2012 05:14 AM - edited 04-07-2012 05:25 AM
It's NOT SOLVED!
I'm using the 1.0.04 firmware(E4200) for a while now..
This firmware is not the solution for me....
Still can't access both my E4200 (and E1000 v2.1.02) via HTTPS.
Using up to date windows 7 and up to date windows XP . Tried different web-browsers.
04-08-2012 01:49 PM
Not that it makes any difference, it is still https broken, but the latest build is 1.0.04 build 11, according to my 2400 it's dated Jan 16, 2012.
Looks like Cisco think router security is a low priority, and we're not going to see any early release of a new firmware version to fix this issue.
We'll all just have to wait for the next scheduled release date, whenever that is.........
04-08-2012 02:52 PM
04-08-2012 10:03 PM
Fix your product Linksys! Or, at least give us an update here on the forum!
Does it make sense to continue to have multiple users create new support tickets when you could simply address us on the forum and/or put out a technical note in your support database?
04-09-2012 02:51 AM - edited 04-09-2012 03:08 AM
There is no mention of a fix for the https problem in the E3000 126.96.36.199 relase notes.
Nex time, maybe.
However there is a workaround mentioned in the 5th post in this thread (for Windows / IE anyway) - problem is due to security update for Windows. I'd say the firmware as it stands has only ever been tested with IE on a Windows platform without the (recent) security update.
I suppose you can't really expect them to test with every browser on every platform... And they didn't expect anyone to actually want to use the https exclusively... The non-secure http no doubt works still?
04-18-2012 02:40 PM
I posted in another thread that referenced this one. Figured I'd post it here as well...
I also experienced the same problem today with my E3000 after setting it to HTTPS. Tried chat support only to be told I was out of warranty, but luckily they tried to assist anyway. The suggestion was to restore the router, which I figured but didn't want to do. Fortunately for me I found this thread and was able to access the router through my phone (yeah lol) and reset it back to HTTP. Up until this point I had tried Firefox, IE, and Chrome - all up to date - and it didn't work. The Cisco Connect utility also wouldn't work. Anyway back to plain old HTTP for me but I figured I'd post here anyway.
Phone used is a Samsung Galaxy S2 if anyone cares. I only mention it because it was the only way I was able to get into the router and change everything back.
05-01-2012 09:07 PM
I found this problem only under windows and only in browsers, which use "ssl false start" of "ssl snap start".
Solution for Chrome:
run chrome from command line with a parameter --disable-ssl-false-start.
Or try to use opera (I checked v11).
About ssl false start see link here: http://www.conceivablytech.com/3299/products/false
05-02-2012 12:10 AM
Wonderful having to use your phone to change settings in your router huh?
We find that this issue still affects other products such as Fortigate SSL VPN and probably affects Cisco's Easy VPN.
The 'fix' from Microsoft doesn't work and the only solution is to disable the security update.
I was really hoping Cisco would come through with a fix or workaround that still provides secure access to their devices.