topic Finally I fixed my problem. I in Network Security

[Solved] ASDM 743 can't login to ASA5512

cwhlaw2009 — Fri, 21 Feb 2020 13:41:12 GMT

Dear all,

I CAN access my new asa5512 (version9.12) by asdm-731-101.

But I CANNOT access by asdm-743 in same setting!!

My asa is Security Plus license and I have uninstall old asdm windows program and download new asdm by webpage

But still can't connect asa.

If i change back asdm to 731-101

And install asdm 731-101 windows program, everything is work!

Why?

1) in same setting i can 731 is ok and 743 is not work

2) I added ssl encryption aes128-sha1 3des-sha1 but not work

3) my asa is Security Plus license

Have you tried upgrading your

Philip D'Ath — Mon, 11 Jan 2016 05:45:42 GMT

Have you tried upgrading your java?

I found the problem,

cwhlaw2009 — Mon, 11 Jan 2016 06:37:00 GMT

I found the problem,

My java is version 8 update 66, my asdm 731 is OK.

But 743 is not OK.

After i downgrade to java version 7 update 45, everything is OK.

...Oh my god!

Why this problem still here!

Because my 731 is no problem, I think C$ fixed, but....

Have you tried ASDM 7.5(2)?

Philip D'Ath — Mon, 11 Jan 2016 06:43:31 GMT

Have you tried ASDM 7.5(2)? I'm currently using 7.5(1) without issue.

I use asdm-743,asdm-751-90

cwhlaw2009 — Mon, 11 Jan 2016 06:47:08 GMT

I use asdm-743,asdm-751-90 and asdm-752 have same problem!

Java 8 update 66 can work

Marvin Rhoads — Mon, 11 Jan 2016 22:20:09 GMT

Java 8 update 66 can work fine with ASDM 7.5(2) and 7.5(1). I use it all the time.

You do need to make sure Java will trust your ASA's SSL certificate. Oracle has lately been making the default when updating Java to revert to highest security level (nless you explicitly unselect it during the Java update process) which, among other things, "untrusts" previously exempted https sites.

Control Panel > Java > Security. Make sure "High" (not "Very high") is selected. While you're in that window, add your ASA's address to the Exception Site List.

Attachment is my java.

cwhlaw2009 — Tue, 12 Jan 2016 09:19:50 GMT

Attachment is my java. version is java 8 update 66. My windows is WIN7 x64.

I select High and add my ASA IP. Is it correct?

You just sparked a memory of

Philip D'Ath — Tue, 12 Jan 2016 09:35:15 GMT

You just sparked a memory of a problem I had long ago with ASDM. You can install both 32 and 64 bit java installed on a x64 bit machine.

You may find you are looking at the version of one, when the other is being used.

Uninstall java. Do a search to make sure there are no java executables left on your machine. And then install just the one of the "bit" versions.

I think i have one java 32bit

cwhlaw2009 — Tue, 12 Jan 2016 10:05:32 GMT

I think i have one java 32bit in my win7, because after install 8 update 66, system said uninstalled previous java.

Try clearing the temporary

Marvin Rhoads — Tue, 12 Jan 2016 13:54:59 GMT

Try clearing the temporary Internet files in the Java control panel.

It can definitely work - see below. Have you tried to launch the demo version from your Java launcher? That is a good tool for figuring out whether the problem is on your workstation of the ASA.

Finally I fixed my problem. I

cwhlaw2009 — Mon, 18 Jan 2016 02:04:16 GMT

Finally I fixed my problem. I find these two site give me a big hint.

http://www.petenetlive.com/KB/Article/0000915

http://www.joeypiccola.com/tech/2014/9/4/asdm-unable-to-launch-device-manager-from-xxxx

I follow their method still can't fix and in ASA I can't find any ASDM login log. That mean ASDM can't reach ASA. Next I try another PC and login succeed .

And than I open my java log and find some TLSv1 error.

I open JAVA > Advanced, I saw Use TLSv1.0, Use TLSv1.1 and Use TLSv2.0 are enabled!! But I uncheck them > click Apply and enable again.

Finally I tested "Run Cisco ASDM as a Java Web Start application" and ASDM Launcher are work!

Thanks ALL