SSL Engine Error

[Rchaoua12]

Greetings!

I have several customers that are encountering the following issue. When they attempt to use Cisco AnyConnect VPN (version 2.5.6005 or 2.4.1012), they recieve the following error "The VPN client agent SSL engine encountered an error. Please restart your computer or device, then try again. If the issue persists, please contact your network administrator."

We've tried restarting the PC and re-installing the VPN client. The users can connect using other networks just not their home network. Has anyone come across this issue before?

[techdata]

Hi,

That error that you are getting is a bit general. So are you able to connect anywhere but from home.

Does this happens after you authenticate? or are you not even able to authenticate?

Is it possible to send the DART?

[Javier Portuguez]

Hi Rachid,

Whenever you encounter this kind of issues, run the DART and look for any obvious error, if not then open a TAC case or post it here

On the other hand, have you tried with a newer version, like 3.1?

HTH.

[Rchaoua12]

Thanks for the replies. I cannot replicate the error on my network at home. The issue is with someone else's laptop. I will have them use DART to gather information. The user authenticates but then is dropped from the VPN session and provided the SSL error. I think that their SP may be the issue, given that they are able to connect from other wifi networks.

[JerryP4621]

We had a few end-users who experienced this error after a head end upgrade to 4.10.01075. What corrected it for us on 1 occasion was have the enduser restart all ISP network equipment at their house. In two instances where that didn't correct it we performed  "Network reset" in Windows 10. Search for "Network Reset" in the search bar and follow the prompts.. No need to have them wait 5 Minutes as the popup indicates you can reboot their machine immediately after.

Note: Our endusers do not have Admin rights and the drivers/adapters reloaded without issue for us. Just something to watch out for. 

Testing the issue was interesting. We tested this theory by having them connect to a hotspot or other connection on the same machine other than the one used to upgrade.. It was successful.  

Hope this helps someone out there as this was the last instance on the Webs in regards to this particular issue.