Re: SRW2024P web front end lost after installing firmware 1.2.9

CostaTsaousis · ‎10-13-2009

Hi,

I own a SRW2024P switch. I installed the latest available firmware and now the web front end is lost. It just shows an empty web page without any additional information, not even the login prompt. I tried the https alternative without luck either (it sends the certificate correctly, but only an empty page is presented, without any login prompt).

The telnet interface is working properly.

I tried to flash the firmware again, with the same results.

Any ideas?

Costa

Tiya Rabb · ‎10-15-2009

What browser(s) are you using when attempting to access GUI?

In the meantime, try changing the username from admin to something else, e.g. admin1. Then try to log on with new username.

CostaTsaousis · ‎10-20-2009

Thanks for the assistance.

In firefox it presents an empty page (no login prompt or anything else).

In i.e it gives a dialog that the current page is willing to close the window (strange - this happens on the main window, not a popup).

I changed the usernames and passwords. No luck.

I restored to factory defaults. No luck again.

Any other ideas?

Costa

Tiya Rabb · ‎10-22-2009

In i.e it gives a dialog that the current page is willing to close the window (strange - this happens on the main window, not a popup).

This is very interesting. What version(s) of IE is this? Just as a test, from the console menu, try changing the port number for the HTTP server of the switch, a random port number i.e. 15754. If this change allows GUI access, I would recommend flashing the firmware (once more), then directly after complete boot, reset to factory defaults, then manually reconfigure. I look forward to your response.

Message was edited by: Tiya Rabb

CostaTsaousis · ‎10-25-2009

I tested internet explorer 8 and firefox 3.0.14.

Changing the HTTP port has no effect (in IE it requests to close the window, in firefox does nothing).

I also tried to wget the url. This is what it produces:

Any other ideas?

jamccord · ‎10-26-2009

Please follow the directions from Microsoft and let me know if this resolves your issue.

http://support.microsoft.com/kb/282402

Regards,

Jason

CostaTsaousis · ‎10-26-2009

I did follow the MS fix, without any changes in the results.

The switch web front end is still unusable...

jamccord · ‎10-26-2009

Hello,

It is not uncommon to have to restart your computer and the switch several times before it will work properly after the MS fix is applied.

Please reboot both devices a couple of times after trying to log into the switch interface. Let me know what you find.

Jason

CostaTsaousis · ‎11-09-2009

Well, I did several reboots on both devices without any progress.

Actually, I believe the windows reboots are useless, since, as I said before, the switch returns an html page with just a javascript close window statement. There is nothing to be done on the web browser side to change that.

Do you suggest going back to the previous firmware?

jamccord · ‎11-09-2009

Hello Costa,

I would suggest that you call the Cisco Small Business Center at 1.866.606.1866 and speak with one of the engineers. The center is open 24/7/365 for your convenience.

We typically do not support going backwards in firmware, but it may be worth a shot to see if the firmware downgrade will allow you into the webui.

After that, reapply the new firmware and test again. Remember to reset the switch to factory defaults too.

Jason

robert.delien · ‎03-03-2011

I have the exact same problem. Calling Cisco isn't of any help: They simply hide behind barricades of contracts and lengthy procedures. Now that's something to keep in mind next time I need network equipment.

Anyway, I'm 'happy' to see I'm not to only one with this problem. I have tried the same suggestions, but to no avail. Are there any solutions to this problem yet? Otherwise I will just send it in for repair because it's still covered by warranty.

David Carr · ‎03-03-2011

Mr. Delien,

What browser are you using to access the switches gui?

If your using Internet Explorer try these steps.

Go to tools/ internet options/ security/ Custom Level.

Then at that screen scroll down to the activex Controls and plugins make sure all the options are enabled or prompt all the way to Script Activex controls marked safe for scripting*.

If using Firefox, you can get the addon named IE tab2 and click the firefox symbol in the lower right hand corner of the page and it will emulate an internet explorer page in firefox.

CostaTsaousis · ‎03-03-2011

Hi all,

As I have said before, the switch returns an html page with just a javascript window close statement. You cannot do anything on the web client to change that.

The solution for me was to downgrade the firmware.

Regards,

Costa

CostaTsaousis · ‎03-16-2011

Hi all,

well I used the really excellent Cisco service and replaced my switch with another one. Really impressed by the very fast response of all involved parties.

However, guess what: Once I upgraded to 1.2.9, the problem appears to this one (the new one) too.

I think I found the problem though. It only happens if you access the switch with a hostname. If you access it with an IP address it responds correctly.

Also, even with the hostname, try to get this url: http://hostname-of-your-switch/config/login.htm With this url, the web front end works as it should.

So, to my understanding there is a bug in firmware 1.2.9 where if you access the switch with a hostname, you cannot get to the login screen. The switch, instead of redirecting you to /config/login.htm, it sends back a page with a javascript statement to close the page.

Regards,

Costa

robert.delien · ‎03-16-2011

I was literally about to unplug my switch and replace it with the replacement that arrived today when the notification of your post came in. So I re-upgraded my old one to 1.2.9 and tried your discovery: I can confirm that the web front end of my switch too is accessible using just the IP address. That's rather sloppy. Now it didn't make much sense anymore to replace the switch.

But I had a couple of LACP problems too, so I decided to switch anyway. The replacement still came with the old firmware, so I upgraded and again I got the same problem. But again using just the IP address worked. I guess this is something to go into the knowledge base.

I'm hoping for a fix, but I'm not really counting on it after this machine going EOL.