On my Windows 10 computer, I can connect to the VPN using AnyConnect 3.1.02026 without difficulty. However, once I disconnect, I need to reboot my computer to connect again. When I try to connect the second (and subsequent) times I get the message,
"The VPN client driver has encountered an error. Please restart your computer or device, then try again."
followed by the message:
"AnyConnect was not able to establish a connection to the specified secure gateway. Please try connecting again."
If I reboot the computer, AnyConnect will connect (once).
Is it happening on a single Win 10 machine or multiple machines ?
Please share the DART file of the affected PC.
You can also check the following workaround:
Please rate helpful posts and mark correct answers.
This sounds exactly like what we are experiencing.
Windows 10 Anniversary Update 64bit
It will connect once consistently, but ALWAYS requires a reboot to connect a second time.
I verified it's not the same as http://www.cisco.com/c/en/us/support/docs/security/asa-5500-x-series-next-generation-firewalls/100597-technote-anyconnect-00.html#anc37
The 'Interact with Desktop' is checked, and RRAS is not enabled.
I have an issues with Cisco AnyConnect VPN. When users wants to connect to the VPN, it's connected but, they don't have access to the internal network, but when I reboot (reload) our ASA, then user can connect to the vpn and they have access to internal network. It's happens sometimes for different user. I don't know what is the issues, could you please help me.
We have ASA 5505 and we are using Cisco AnyConnect (Split tunneling) to access to the internal network.
I too have been seeing this lately on AnyConnect 4.2.02075 (and still with the latest 4.2.03013). I haven't had time to open a TAC case on it yet.
I did find through trial and error that a total reboot was not required - simply a Windows logoff / logon does the trick for me.
I did try unsuccessfully to stop and start the VPN client and UI services from Windows' Process manager. I also found and applied the "interact with desktop" workaround. No joy.
Do you perchance have AnyConnect NAM also installed? I dug through my DART log and saw some indicators of it being a potential issue. I turned off NAM and the VPN started working after it was failing earlier. It looks like some NAM-related bug as I can reproduce the issue simply by disabling and re-enabling NAM.
It also may be related to that plus the one VPN that seems to be causing the issue is an ASA running old 8.2(5) code.