AnyConnect using https
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-12-2019 11:41 AM - edited 02-21-2020 09:40 PM
My network engineer did a security update on my Cisco ASA 5506
After the update, I was unable to connect to the ASA
I received this message
Could not connect to the server. Please verify the internet connection and server address.
I added https:// in front of the address in AnyConnect I was able to connect until I received a certificate block which I was unable to bypass when I unchecked untrusted servers
Any ideas? Could the security cert need to be reloaded?
- Labels:
-
AnyConnect
-
Remote Access
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-12-2019 12:16 PM
either you can download the cert in your computer/laptop than it will trust the cert. or unless you get the cert sort out for the ASA.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-12-2019 01:13 PM
I am talking about reloading the security cert i purchased on the 5506 ASA. I have too many users to load a security cert on each laptop
I am unsure why a security update would force me to put https in front of the VPN name in AnyConnect
I used to add the name vpn name vpn.anyserver.com in AnyConnect and never had an issue connecting
Now I have to type https://vpn. anyserver.com for AnyConnect to connect to the VPN
When it connects I get blocked for security issue untrusted server
I can bypass the block but it should not be this way
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-18-2019 07:56 AM
Hi,
There can be multiple reasons behind this issue.
1. AnyConnect/XML Profile could be a possible reason for the error you are facing. Please try deleting the XML profile and then test. XML Profile can be found at
%ProgramData%\Cisco\Cisco AnyConnect Secure Mobility Client\Profile
2. Cisco Any-Connect Client could be another possible reason. Update the Cisco Any-Connect Client.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-18-2019 11:41 AM
I understand your problem, can you provide the DART logs after a connection attempt?
You can either share it here or send it to shaktiku@cisco.com
Here is a document that explains how to collect DART logs
https://community.cisco.com/t5/security-documents/how-to-collect-the-dart-bundle-for-anyconnect/ta-p/3156025
Thanks
Shakti
