01-14-2014 06:43 PM - edited 02-21-2020 07:26 PM
01-15-2014 07:21 PM
Your best bet is to install a properly trusted certificate on the head-end, this way there will be no invalid certificate dialogs to deal with.
01-18-2014 08:54 AM
This has nothing to do with the vpn server, and everything to do with the client. I get exactly the same behavior when connecting to various corporate VPNs that I have access to, all of which have valid and trusted certificates.
My certificate may not be from a trusted source, but it is NOT empty. There is something wrong with the client, as other people are able to connect fine.
01-18-2014 09:56 PM
Then uninstall the client completely and reinstall it.
Sent from Cisco Technical Support iPad App
01-19-2014 12:00 PM
06-11-2014 12:42 PM
I have the same problem. Is working good on client AnyConnect MAC OS, Android, Iphone and Windows XP , but on Win7 don´t work. Do you have the fix for this issue?. I installed the ASA certified on Windows but the answer is the same: Warning: The following Certificate received from the Server could not be verified.
Win7, 64, AnyConnect 3.011042, ASA 5550, 8.4(7).
appreciate any help....
01-19-2014 04:28 AM
Just be careful about posting DART-Bundles. I examined that once and it turned out it had for example a complete list of all SSIDs and BSSIDs of hotel and customer's WLANs which I connected to in the last four (!!!) months, giving a detailed roaming profile. Also timestamps when I opened the lid of my notebook, traces and logs of other softwareinstallers and several sensitive details about my operating system. This is not what I would post in public and I would even hesitate to give that to Cisco support. Especially in these times...
I haven't examined the DART-Bundle of Windows so far but at least the OS X DART collects all sort of information which is completely irrelevant to Anyconnect issues and (funny enough) doesn't contain Anyconnect debug information.
06-11-2014 01:08 PM
The version you are using is approximately 1.5 years old and there have been a few dozen patch releases in between. Before doing any further troubleshooting, please try to upgrade to 3.1.05160 (the current release) and re-test. Once you have done that, if it is still failing, please generate a Diagnostics bundle and send it to email@example.com so that we can investigate (or open up a TAC case for formal support).
06-11-2014 03:33 PM
Thank you for your answer. I changed the AnyConnection version to 3.1.05160 (the last version on client VPN and ASA image) and I try again but it is still failing. The app send me the next message:
"Connection Attempt failed. Please try again"
I will send you the DART Bundle file to firstname.lastname@example.org. I'll wait for your help.
Thank you again.
06-11-2014 05:29 PM
PSD, thank you for your valuable help. The problem was on ASA device, with a misconfigured encryption algorithms like you said . I had to configure on ASA device this command line: "ssl encryption aes256-sha1 aes128-sha1 3des-sha1 des-sha1" and it worked. Thank you.
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: