What should be done when an attempt to connect to VPN using Cisco AnyConnect generates this message: AnyConnect was not able to establish a connection to the specified secure gateway. Please try connecting again. In the Windows Control Panel navigate to Internet options (Network and Internet Connections, and then Internet Options). Something strange would happen when I connected to a Firepower 2130 running Firepower Threat Defense with Cisco AnyConnect. Basically, the AnyConnect client would contact the VPN gateway just fine, prompt for user credentials, authenticate and connect but then literally after about 3 seconds of being connected it would immediately drop and attempt to reconnect again. Cisco AnyConnect takes long time to initiate connection and Authentication failed. Unable to Proceed, Cannot Connect to the VPN Service. VPN Client Driver Encounters Errors after a Microsoft Windows Update. Method 1 Step-by-Step to fix VPN Authentication failed Error.
- Aug 02, 2019 You have uninstalled Cisco AnyConnect from the PC, but you still have the connectivity issue. In this scenario we would suggest you to perform this steps and check. Press Windows + R key from the keyboard to open Run command. Type inetcpl.cpl and click OK.
- The fix is quite simple actually, go to Network Connections from Control Panel, right-click Cisco AnyConnect Security Mobility Client Connection, and choose Properties. Then disable IPv6, change IPv4 IP settings from Fixed IP to Dynamic. Close all Network Properties dialog boxes, and try VPN connecting again. It should go through fine now.
I was trying to log into work but had trouble making a VPN connection. I use Cisco AnyConnect VPN Client. This post describes how to fix the following error messages when using Windows 8 Pro:
- AnyConnect was not able to establish a connection to the specified secure gateway. Please try connecting again.
- The VPN client driver encountered an error. Please restart your computer or device, then try again.
The steps to fix this problem are as follows:
1. Edit a registry entry by running a program called regedit. Right-click on it and Run as administrator. Note that I use Start8, by Stardock, to have a Start button and menu. After you left-click on Run as administrator, your computer might ask you to enter the admin password.
2. Go to the appropriate VPN registry directory called ComputerHKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesvpnva
3. Double left-click the DisplayName key.
An Edit String pop-up window will appear.
The text under the Value data: field on my computer looked like this.
@oem20.inf,%vpnva_Desc%;Cisco AnyConnect VPN Virtual Miniport Adapter for Windows x64
4. Change the field to
Cisco AnyConnect VPN Virtual Miniport Adapter for Windows x64
by removing all the text and characters that are on the left of the word Cisco.
The end result should look like this:
5. Left-click the ‘OK’ button.
6. Exit the Registry Editor
7. Run Cisco AnyConnect VPN Client and reconnect.
That’s all there is to it. Good luck!
Update : 2/13/2014
I recently updated my computer on February 13, 2014 with Microsoft’s updates and saw that the text under the Value data: field on my computer looked like this:
@oem10.inf,%VPNVA64_Desc%;Cisco AnyConnect Secure Mobility Client Virtual Miniport Adapter for Windows x64
It is different from what I had originally posted. I’m not really sure how or why it changed and I don’t have time to find out. I also updated to Cisco AnyConnect Secury Mobility Client Version 3.1.04066. As far as I can tell, the value of …
@oem10.inf,%VPNVA64_Desc%;Cisco AnyConnect Secure Mobility Client Virtual Miniport Adapter for Windows x64
.. works, but the value of
Cisco AnyConnect VPN Virtual Miniport Adapter for Windows x64
does not work with Cisco AnyConnect Secury Mobility Client Version 3.1.04066.
Update : 2/15/2014
Changing the Value data: field to
Cisco AnyConnect Secure Mobility Client Virtual Miniport Adapter for Windows x64
without
AnyConnect VPN Client FAQ
@oem10.inf,%VPNVA64_Desc%;
Cisco Anyconnect Not Connecting To Server
seems to work better, too.