Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

Cisco Employee

AnyConnect "Always On VPN" connection issue...

Hi All,

In one my customer premises, there is ASA 5520 with 8.2 version. Customer wants to use Always on VPN solution for their mobile clients. This is a POC situation and things are not working. We have selected Self Certificate for this POC as of now. The below is the errors captured from the client device (WIndows Based Lappy), Certificate is downloaded and made "trusted" as of now.

Please help with similar known issues with probable solutions.

Error Seen at Client End:

[19-11-2013 20:31:46] VPN Connecting

[19-11-2013 20:31:46] Contacting

ITC-POC-VPN.ITC.IN.

[19-11-2013 20:31:46] Processing CRLs...

[19-11-2013 20:31:47] Connection attempt has failed.

[19-11-2013 20:31:47] AnyConnect cannot confirm it is connected to your secure gateway.  The local network may not be trustworthy.  Please try another network.

[19-11-2013 20:33:47] VPN Connecting

[19-11-2013 20:33:47] Contacting

ITC-POC-VPN.ITC.IN.

[19-11-2013 20:33:47] Processing CRLs...

[19-11-2013 20:33:48] Connection attempt has failed.

[19-11-2013 20:33:48] AnyConnect cannot confirm it is connected to your secure gateway.  The local network may not be trustworthy.  Please try another network.

Thanks in Advance... I can share other inputs if required.

  • VPN
Everyone's tags (1)
1 REPLY

AnyConnect "Always On VPN" connection issue...

When you downloaded the self signed certificate from the ASA which store did you place it in? Did you have windows choose automatically? You may want to force it into the trusted root authority store.

Thanks,

Tarik Admani
*Please rate helpful posts*

Tarik Admani *Please rate helpful posts*
760
Views
0
Helpful
1
Replies
This widget could not be displayed.