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:
- Cisco Anyconnect Unable To Contact Server Settings
- Unable To Access Local Network When Cisco VPN ... - Server Fault
Chat with IT Support Call 513-529-7900 Submit a help ticket Response Expectations Divisional Resources ©2021 Miami University. All rights reserved. The VPN service for AnyConnect is not running. Solution: Determine if another application conflicted with the service by going to the Windows Administration Tools then make sure that the Cisco AnyConnect VPN Agent is not running. The MX only supports TLS 1.2, hence you need AnyConnect client version 4.8 or higher to connect to the MX (AnyConnect server). Unable to connect due to captive portal This error message is usually seen when there is a captive portal enabled on the network the user is connecting from.
- 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
Cisco Anyconnect Unable To Contact Server Settings
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:
Unable To Access Local Network When Cisco VPN ... - Server Fault
@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
@oem10.inf,%VPNVA64_Desc%;
seems to work better, too.