ASDM Connection

[jsiegfried]

I can't connect via ASDM 7.5(2) 153 to newly installed ASA 9.4(2)11.   I can connect via https://host_ip/admin/exec/ sh ver or do any other command.   I also get unable to connect to via ASDM with Java Web Start to run too?  Running Java 8r111.    I can connect to other installed ASA via ASDM?  

[Marvin Rhoads]

Please share output of the following commands:

dir
show run asdm
show run ssl
show activation-key
show run http

[jsiegfried]

I have attached the outputs of the commands you requested,  thanks for your help.  

[Marvin Rhoads]

That looks mostly OK.

I don't see any ssl commands so that could be an issue. Normally we would have an identity certificate (either self-signed or CA-issued) and an ssl trustpoint binding that certificate to an interface. However it's not mandatory.

What error do you get when you browse to the ASA's management interface? Can you also confirm that you are coming in from one of the defined addresses - there are a limited number iof individual hosts permitted per the "http" commands in the output you shared.

[jsiegfried]

I get no error when I browser to the ASA management interface. My host is .123. I can run commands to the asa via the browser,  https://192.168.61.21/admin/exec/sh ver, etc.  When I try to run Cisco ASDM as Java Web Start application,  I can start downloading the application,  prompt for username/password,  then get the application error " unable to launch the application"?  Fellow staff are able ASDM into the ASA.  I am able to run ASDM to other ASA with the same build all day,  thanks for your help

[Marvin Rhoads]

OK, that additional information is helpful. From what you're describing it almost certainly sounds like a Java issue. There are several things necessary for ASDM to work properly and after all the basics are covered, client side Java issues are the most common problems.

To troubleshoot that, I find it useful to open the Java console. You can control that in the Java Control Panel applet, advanced tab. Change the setting to "show console" and try the Java web start application once again.

I'd also try using the ASDM installer vs. the Java web start application as it seems generally more reliable for me.

If all else fails, I sometimes fire up Wireshark and watch the raw frames as I try to launch the application. If you have something like a cipher mismatch that will show up there. (Although given that "show run sll " is blank, the ASA you are having trouble with has not has SSL ciphers locked down.)

[jsiegfried]

I was to get ASDM working,  it was a java problems in my security setting.  I had  to add the whole url  https://192.168.60.21/idm.idm.jnpl