08-01-2018 12:23 PM - edited 02-21-2020 09:25 PM
Hello,
We recently had a user bring in a Windows XP laptop that they had been using to connect to our VPN, using the AnyConnect 3.1 client. After we migrated from a older ASA, to an ASA running FTD 6.2.3.2, that client is no longer able to connect to the VPN, and gets an error message:
Connection attempt failed, please try again
Reinstalling the 3.1 client doesn't resolve the problem. Is the 3.1 client not compatible with the current FTD release? As expected, the 4.x AnyConnect client won't install on XP.
Thanks
Solved! Go to Solution.
08-02-2018 01:23 AM
The VPN headend (ASA or FTD) will always try to upgrade a client who connects with an older version of AnyConnect using the locally stored and configured pkg file.
If the client is unable to install and run the current AnyConnect release, then they will be unable to connect to the VPN.
08-02-2018 01:23 AM
The VPN headend (ASA or FTD) will always try to upgrade a client who connects with an older version of AnyConnect using the locally stored and configured pkg file.
If the client is unable to install and run the current AnyConnect release, then they will be unable to connect to the VPN.
08-06-2018 12:30 PM
Thank you Marvin, this was very helpful.
08-07-2018 01:28 PM - edited 08-07-2018 01:29 PM
The VPN headend (ASA or FTD) will always try to upgrade a client who connects with an older version of AnyConnect using the locally stored and configured pkg file.
Unless skipping the update is enabled in the XML Client Profile.
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: