09-19-2017 10:45 AM - edited 02-21-2020 06:19 AM
Hello
I upgraded the OS on our ASA 5505 from asa917-9-k8.bin to as917-16-k8.bin to mitigate the 200 day bug. All but one ASA upgraded nicely and can be reached by ASDM. This ASA upgraded but I can't connect to it in ASDM. It is the only device with multiple contexts system and notsystem. I have ASDM 7.6.2 on all ASA.
With ASDM open and other devices added I click on the IP address of this ASA just upgraded and it errors out-Device Error: Could Not Open Device <IP ADDRESS>.
Solved! Go to Solution.
09-19-2017 12:50 PM - edited 09-19-2017 12:51 PM
I found a solultion myself.
I issued the following command to get everything working:
ssl encryption aes256-sha1 aes128-sha1 3des-sha1 des-sha1
Looks like for some reason the device didn't have the ssl encryption enabled for the asdm to work.
09-19-2017 12:50 PM - edited 09-19-2017 12:51 PM
I found a solultion myself.
I issued the following command to get everything working:
ssl encryption aes256-sha1 aes128-sha1 3des-sha1 des-sha1
Looks like for some reason the device didn't have the ssl encryption enabled for the asdm to work.
09-19-2017 12:57 PM
You don't want to enable DES nowadays ... And also 3DES is typically not needed anymore if you don't have to support Windows XP.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide