ASDM unable to launch device manager

Unanswered Question
Oct 6th, 2008

hi, i have installed ASA 5550 and every thing works fine, one day i noticed that my ASDM is not working. when i try to connect it gives me error " unable to launch device manager from xx.xx.xx.xx ip "

i have enabled http server and also http xx.xx.xx.xx 255.255.255.255 inside.

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 4.9 (5 ratings)
Loading.
satish_zanjurne Mon, 10/06/2008 - 02:37

Hi,

1.Have you configure webvpn on same port where ASDM is running. ?

2.ASDM and WebVPN cannot be enabled on the same interface of the ASA, as both are listening on the same port, 443, by default.

3.Solution would be you can either change the https server port number for launching ASDM, or the listening port for WebVPN in order to overcome this problem.

http://www.cisco.com/en/US/products/ps6120/products_tech_note09186a00807be2a1.shtml

HTH..rate if helpful..

pbhosale90 Sat, 03/15/2014 - 10:54

Hi, I had the same problem with asdm on Cisco ASA 8.4(2).

 

I tried changing the port of WebVpn but the issue was not resolved.

Then I checked the security settings of Java.

I added the asdm URL i.e., https://10.0.0.1 to the Security TAB of the Java Control Panel...

 

Added the URL from Edit Site List...>Typed the URL and clicked Add.

 

And this resolved my asdm issue.

 

marioderosa2008 Mon, 01/04/2010 - 04:23

Hi,

I too am having this problem.

I have done a show run and found that the http server is enabled on both inside and outside

The webvpn is enabled on the outside interface

I am able to connect the VPN, but then when i try and launch the ASDM client it says that it cannot launch

if i browse to https://ip_address_of _ASA it does not display a page.

I was going to follow the article that you posted but my question is that when I VPN in and launch the ASDM pointing to the internal IP of the ASA, that means that there should be no conflict due to the webvpn cleint not being enabled on the inside interface.

So I am confused now.

Any help appreciated.

Mario

marioderosa2008 Mon, 01/04/2010 - 04:31

just also found out that i am running ASA 8.0 (4)

so i do not think that article applies to me.

Any other thoughts/suggestions would be very helpful.

Mario

stevenmcconnell Wed, 01/22/2014 - 07:59

Issue with ASDM previously working then misteriously one day it stops working and your unable to connect to it. Is directly related to a java update, I downgraded from Java Version 7.5 to 6.4 and I am successfully able to connect to my ASA again.

Here are the files if you need them for either x64 or x86

http://tcpsolution.com/files/java/jre-6u43-windows-i586.exe

http://tcpsolution.com/files/java/jre-6u43-windows-x64.exe

http://tcpsolution.com/files/java/jre-7u40-windows-i586.exe

http://tcpsolution.com/files/java/jre-7u40-windows-x64.exe

Steve Ballantyne Tue, 03/11/2014 - 11:51

This saved me too.  And you don't necessarily have to remove your current version of Java.  I just installed 6u43, and then edited the shortcut that starts Cisco ASDM and changed the path to javaws to point to the path for 6u43.

Thanks for the hint!

"Ferris Bueller, you're my hero"

Buhlz_I_TX Wed, 08/06/2014 - 09:20

Hi Steve,

Another confirmation that rolling back Java to 6 resolved the issue. 

 

Thanks for the fix mate smiley

 

/Cheers

 

mmuthiah72 Wed, 01/22/2014 - 08:59

I had issue login into ASDM as well after genarating a self signed cert required for vpn server.   The issue fixed when i added cert to my java keystore.   The java console will show what exactly the issue is.

Actions

This Discussion