Some tabs could be disabled due to communication error

Исправлено: AnyConnect не смог установить соединение с указанным безопасным шлюзом —

Сообщение об ошибке ‘AnyConnect не смог установить соединение с указанным безопасным шлюзом’Появляется, когда пользователи пытаются подключиться к VPN с помощью клиента AnyConnect. Эта проблема возникает из-за того, что VPN-клиент AnyConnect не может успешно выполнить процесс соединения с удаленным сервером, и на его пути существуют некоторые блокировки. Сегодня мы рассмотрим упомянутое сообщение об ошибке, включая причины сообщения об ошибке и различные решения, которые вы можете реализовать, чтобы избавиться от ошибки.

AnyConnect не смог установить соединение с указанным безопасным шлюзом

По какой причине AnyConnect не смогла установить соединение с указанным сообщением об ошибке безопасного шлюза?

Это может быть связано со многими причинами. Иногда это блокировка антивирусом или брандмауэром, а иногда это может быть вызвано плохим подключением к Интернету. Следующее будет основными причинами; упомянуть вкратце —

• Проблема с антивирусом или брандмауэром: Антивирусное программное обеспечение может иногда вмешиваться в процесс подключения VPN-клиента AnyConnect и не разрешать ему подключаться к внешним сетям или серверам по соображениям безопасности. Много раз это заблокирует много входящих и исходящих соединений. Таким образом, вы не сможете подключиться к своему любимому VPN с помощью Anyconnect.
• Неправильная конфигурация клиента: Если вы неправильно настроили свой клиент Anyconnect и сохраненные в нем конфигурации VPN неверны, тогда вы столкнетесь с проблемами при установлении успешных соединений.
• Интернет ограничения: Время от времени ваш провайдер может заблокировать IP-адреса некоторых стран, и вы не можете сознательно пытаться подключиться к VPN той же страны, которая была заблокирована вашим провайдером. Тогда вы столкнетесь с проблемами.

Чтобы обойти сообщение об ошибке, вы можете следовать решениям, приведенным ниже.

Решение 1. Отключение антивируса

Обо всем по порядку. Поскольку в большинстве случаев проблема вызвана антивирусной блокировкой, которая является распространенным сценарием. Поэтому, в таком случае, вы должны попытаться отключить любой сторонний антивирус, который вы установили в своей системе, а затем попытаться подключиться к VPN с помощью AnyConnect. Надеюсь, это изолирует проблему.

Отключить антивирус

Решение 2. Остановите службу подключения к Интернету

Иногда служба ICS работает, что вызывает проблемы для клиента AnyConnect, чтобы соединиться с VPN. Вам придется отключить его, чтобы решить проблему. Вот как отключить службу:

1. Нажмите Windows + R и введите services.msc
2. Когда откроется окно с сервисами, выполните поиск Общий доступ к интернету оказание услуг. Щелкните правой кнопкой мыши и выберите Стоп.
   Остановка службы ICS
3. Затем выйдите из Сервисы окна, закрыв его.

Решение 3. Отключите общий доступ к подключению к Интернету (ICS)

Было несколько случаев, когда ICS был включен в Windows, тогда пользователи сталкивались с этой проблемой. Чтобы отключить ICS, следуйте инструкциям ниже:

1. Откройте панель управления
2. Идти к Сеть и Интернет-обмен а затем нажмите Смените настройки адаптера.
   Центр коммуникаций и передачи данных
3. После этого вам нужно будет щелкнуть правой кнопкой мыши на подключение к общей сети, а затем нажмите на свойства.
4. В окне свойств нажмите на разделение
5. Оказавшись там, вы должны снять флажок с надписью «Разрешить другим пользователям сети подключаться к Интернету через этот компьютер».
6. После этого нажмите ОК.

Если ваша проблема была вызвана включением ICS, то это должно быть исправлено.

Решение 4. Выберите опцию Подключиться к текущей сети в AnyConnect VPN.

Иногда VPN-клиент Any Connect колеблется между разными сетями, поэтому вам нужно выбрать вариант подключения только к текущей сети. Это может решить проблему для вас. Вот как это сделать:

1. Открой Клиент AnyConnect, и где вы видите сеть написано, щелкните правой кнопкой мыши на нем.
2. Нажмите на «Подключаться только к текущей сети».
   Клиент Cisco AnyConnect

Решение 5. Попробуйте альтернативное соединение

Время от времени используемое вами интернет-соединение может иметь некоторые ограничения или работать неправильно, что является причиной проблемы. В таком случае вам придется использовать альтернативное соединение, например, WiFi или мобильную точку доступа, чтобы узнать, сможете ли вы подключиться к VPN.

Источник

Basic Troubleshooting on Cisco AnyConnect Secure Mobility Client Errors

Available Languages

Download Options

Bias-Free Language

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.

Objective

The objective of this document is to show you basic troubleshooting steps on some common errors on the Cisco AnyConnect Secure Mobility Client. When installing the Cisco AnyConnect Secure Mobility Client, errors may occur and troubleshooting may be needed for a successful setup.

Note that the errors discussed in this document is not an exhaustive list and varies with the configuration of the device used.

For additional information on AnyConnect licensing on the RV340 series routers, check out the article AnyConnect Licensing for the RV340 Series Routers.

Software Version

Basic Troubleshooting on Cisco AnyConnect Secure Mobility Client Errors

Note: Before attempting to troubleshoot, it is recommended to gather some important information first about your system that might be needed during the troubleshooting process. To learn how, click here.

1. Problem: Network Access Manager fails to recognize your wired adapter.

Solution: Try unplugging your network cable and reinserting it. If this does not work, you may have a link issue. The Network Access Manager may not be able to determine the correct link state of your adapter. Check the Connection Properties of your Network Interface Card (NIC) driver. You may have a «Wait for Link» option in the Advanced Panel. When the setting is On, the wired NIC driver initialization code waits for auto negotiation to complete and then determines if a link is present.

2. Problem: When AnyConnect attempts to establish a connection, it authenticates successfully and builds the Secure Socket Layer (SSL)session, but then the AnyConnect client crashes in the vpndownloader if using Label-Switched Path (LSP) or NOD32 Antivirus.

Solution: Remove the Internet Monitor component in version 2.7 and upgrade to version 3.0 of ESET NOD32 AV.

3. Problem: If you are using an AT&T Dialer, the client operating system sometimes experiences a blue screen, which causes the creation of a mini dump file.

Solution: Upgrade to the latest 7.6.2 AT&T Global Network Client.

4. Problem: When using McAfee Firewall 5, a User Datagram Protocol (UDP)Datagram Transport Layer Security (DTLS) connection cannot be established.

Solution: In the McAfee Firewall central console, choose Advanced Tasks > Advanced options and Logging and uncheck the Block incoming fragments automatically check box in McAfee Firewall.

5. Problem: The connection fails due to lack of credentials.

Solution: The third-party load balancer has no insight into the load on the Adaptive Security Appliance (ASA) devices. Because the load balance functionality in the ASA is intelligent enough to evenly distribute the VPN load across the devices, using the internal ASA load balancing instead is recommended.

6. Problem: The AnyConnect client fails to download and produces the following error message:

Solution: Upload the patch update to version 1.2.1.38 to resolve all dll issues.

7. Problem: If you are using Bonjour Printing Services, the AnyConnect event logs indicate a failure to identify the IP forwarding table.

Solution: Disable the Bonjour Printing Service by typing net stop “bonjour service” at the command prompt. A new version of mDNSResponder (1.0.5.11) has been produced by Apple. To resolve this issue, a new version of Bonjour is bundled with iTunes and made available as a separate download from the Apple web site.

8. Problem: An error indicates that the version of TUN or network tunnel is already installed on this system and is incompatible with the AnyConnect client.

Solution: Uninstall the Viscosity OpenVPN Client.

9. Problem: If a Label-Switched Path (LSP) module is present on the client, a Winsock catalog conflict may occur.

Solution: Uninstall the LSP module.

10. Problem: If you are connecting with a Digital Subscriber Line (DSL) router, DTLS traffic may fail even if successfully negotiated.

Solution: Connect to a Linksys router with factory settings. This setting allows a stable DTLS session and no interruption in pings. Add a rule to allow DTLS return traffic.

11. Problem: When using AnyConnect on some Virtual Machine Network Service devices, performance issues have resulted.

Solution: Uncheck the binding for all IM devices within the AnyConnect virtual adapter. The application dsagent.exe resides in C:WindowsSystemdgagent. Although it does not appear in the process list, you can see it by opening sockets with TCPview (sysinternals). When you terminate this process, normal operation of AnyConnect returns.

12. Problem: You receive an “Unable to Proceed, Cannot Connect to the VPN Service” message. 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. If it is running and the error message still appears, another VPN application on the workstation may need to be disabled or even uninstalled. After taking that action, reboot, and repeat this step.

13. Problem: When Kaspersky 6.0.3 is installed (even if disabled), AnyConnect connections to the ASA fail right after CSTP state = CONNECTED. The following message appears:

Solution: Uninstall Kaspersky and refer to their forums for additional updates.

14. Problem: If you are using Routing and Remote Access Service (RRAS), the following termination error is returned to the event log when AnyConnect attempts to establish a connection to the host device:

Solution: Disable the RRAS service.

15. Problem: If you are using a EVDO wireless card and Venturi driver while a client disconnect occurred, the event log reports the following:

Solutions:

• Check the Application, System, and AnyConnect event logs for a relating disconnect event and determine if a NIC card reset was applied at the same time.
• Ensure that the Venturi driver is up to date. Disable Use Rules Engine in the 6.7 version of the AT&T Communications Manager.

If you encounter other errors, contact the support center for your device.

For further information and community discussion on AnyConnect licensing updates, click here.

Источник

AnyConnect VPN Client Troubleshooting Guide — Common Problems

Available Languages

Download Options

Bias-Free Language

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.

Contents

Introduction

This document describes a troubleshooting scenario which applies to applications that do not work through the Cisco AnyConnect VPN Client.

Prerequisites

Requirements

There are no specific requirements for this document.

Components Used

The information in this document is based on a Cisco Adaptive Security Appliance (ASA) that runs Version 8.x.

The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.

Troubleshooting Process

This typical troubleshooting scenario applies to applications that do not work through the Cisco AnyConnect VPN Client for end-users with Microsoft Windows-based computers. These sections address and provide solutions to the problems:

Installation and Virtual Adapter Issues

Complete these steps:

Obtain the device log file:

Windows XP / Windows 2000:

Note: Hidden folders must be made visible in order to see these files.

If you see errors in the setupapi log file, you can turn up verbosity to 0x2000FFFF.

Obtain the MSI installer log file:

If this is an initial web deploy install, this log is located in the per-user temp directory.

Windows XP / Windows 2000:

If this is an automatic upgrade, this log is in the temp directory of the system:

The filename is in this format: anyconnect-win-x.x.xxxx-k9-install-yyyyyyyyyyyyyy.log. Obtain the most recent file for the version of the client you want to install. The x.xxxx changes based on the version, such as 2.0.0343, and yyyyyyyyyyyyyy is the date and time of the install.

Obtain the PC system information file:

From a Command Prompt/DOS box, type this:

Windows XP / Windows 2000:

Note: After you type into this prompt, wait. It can take between two to five minutes for the file to complete.

Obtain a systeminfo file dump from a Command Prompt:

Windows XP and Windows Vista:

Refer to AnyConnect: Corrupt Driver Database Issue in order to debug the driver issue.

Disconnection or Inability to Establish Initial Connection

If you experience connection problems with the AnyConnect client, such as disconnections or the inability to establish an initial connection, obtain these files:

The configuration file from the ASA in order to determine if anything in the configuration causes the connection failure:

From the console of the ASA, type write net x.x.x.x:ASA-Config.txt where x.x.x.x is the IP address of a TFTP server on the network.

From the console of the ASA, type show running-config . Let the configuration complete on the screen, then cut-and-paste to a text editor and save.

The ASA event logs:

In order to enable logging on the ASA for auth, WebVPN, Secure Sockets Layer (SSL), and SSL VPN Client (SVC) events, issue these CLI commands:

Originate an AnyConnect session and ensure that the failure can be reproduced. Capture the logging output from the console to a text editor and save.

In order to disable logging, issue no logging enable .

The Cisco AnyConnect VPN Client log from the Windows Event Viewer of the client PC:

Choose Start > Run.

Right-click the Cisco AnyConnect VPN Client log, and select Save Log File as AnyConnect.evt.

Note: Always save it as the .evt file format.

If the user cannot connect with the AnyConnect VPN Client, the issue might be related to an established Remote Desktop Protocol (RDP) session or Fast User Switching enabled on the client PC. The user can see the AnyConnect profile settings mandate a single local user, but multiple local users are currently logged into your computer. A VPN connection will not be established error message error on the client PC. In order to resolve this issue, disconnect any established RDP sessions and disable Fast User Switching. This behavior is controlled by the Windows Logon Enforcement attribute in the client profile, however currently there is no setting that actually allows a user to establish a VPN connection while multiple users are logged on simultaneously on the same machine. Enhancement request CSCsx15061 was filed to address this feature.

Note: Make sure that port 443 is not blocked so the AnyConnect client can connect to the ASA.

When a user cannot connect the AnyConnect VPN Client to the ASA, the issue might be caused by an incompatibility between the AnyConnect client version and the ASA software image version. In this case, the user receives this error message: The installer was not able to start the Cisco VPN client, clientless access is not available .

In order to resolve this issue, upgrade the AnyConnect client version to be compatible with the ASA software image.

When you log in the first time to the AnyConnect, the login script does not run. If you disconnect and log in again, then the login script runs fine. This is the expected behavior.

When you connect the AnyConnect VPN Client to the ASA, you might receive this error: User not authorized for AnyConnect Client access, contact your administrator .

This error is seen when the AnyConnect image is missing from the ASA. Once the image is loaded to the ASA, AnyConnect can connect without any issues to the ASA.

This error can be resolved by disabling Datagram Transport Layer Security (DTLS). Go to Configuration > Remote Access VPN > Network (Client) Access > AnyConnect Connection Profiles and uncheck the Enable DTLS check box. This disables DTLS.

The dartbundle files show this error message when the user gets disconnected: TUNNELPROTOCOLDPDMGR_ERROR_NO_DPD_RESPONSE:The secure gateway failed to respond to Dead Peer Detection packets . This error means that the DTLS channel was torn due to Dead Peer Detection (DPD) failure. This error is resolved if you tweak the DPD keepalives and issue these commands:

The svc keepalive and svc dpd-interval commands are replaced by the anyconnect keepalive and anyconnect dpd-interval commands respectively in ASA Version 8.4(1) and later as shown here:

Problems with Passing Traffic

When problems are detected with passing traffic to the private network with an AnyConnect session through the ASA, complete these data-gathering steps:

Obtain the output of the show vpn-sessiondb detail svc filter name ASA command from the console. If the output shows Filter Name: XXXXX , then gather the output for show access-list XXXXX. Verify that the access-list XXXXX does not block the intended traffic flow.

Export the AnyConnect statistics from AnyConnect VPN Client > Statistics > Details > Export (AnyConnect-ExportedStats.txt).

Check the ASA configuration file for nat statements. If Network Address Translation (NAT) is enabled, these must exempt data that returns to the client as a result of NAT. For example, to NAT exempt (nat 0) the IP addresses from the AnyConnect pool, use this on the CLI:

Determine if the tunneled default gateway needs to be enabled for the setup. The traditional default gateway is the gateway of last resort for non-decrypted traffic.

For example, if the VPN Client needs to access a resource which is not in the routing table of the VPN Gateway, the packet is routed through the standard default gateway. The VPN gateway does not need the complete internal routing table in order to resolve this. The tunneled keyword can be used in this instance.

Verify if the AnyConnect traffic is dropped by the inspection policy of the ASA. You could exempt the specific application that is used by AnyConnct client if you implement the Modular Policy Framework of Cisco ASA. For example, you could exempt the skinny protocol with these commands.

AnyConnect Crash Issues

Complete these data-gathering steps:

Ensure that the Microsoft Utility Dr Watson is enabled. In order to do this, choose Start > Run, and run Drwtsn32.exe. Configure this and click OK:

When the crash occurs, gather the .log and .dmp files from C:Documents and SettingsAll UsersApplication DataMicrosoftDr Watson. If these files appear to be in use, then use ntbackup.exe.

Obtain the Cisco AnyConnect VPN Client log from the Windows Event Viewer of the client PC:

Choose Start > Run.

Right-click the Cisco AnyConnect VPN Client log, and select Save Log File As AnyConnect.evt.

Note: Always save it as the .evt file format.

Fragmentation / Passing Traffic Issues

Some applications, such as Microsoft Outlook, do not work. However, the tunnel is able to pass other traffic such as small pings.

This can provide clues as to a fragmentation issue in the network. Consumer routers are particularly poor at packet fragmentation and reassembly.

Try a scaling set of pings in order to determine if it fails at a certain size. For example, ping -l 500, ping -l 1000, ping -l 1500, ping -l 2000.

It is recommended that you configure a special group for users that experience fragmentation, and set the SVC Maximum Transition Unit (MTU) for this group to 1200. This allows you to remediate users who experience this issue, but not impact the broader user base.

Problem

TCP connections hang once connected with AnyConnect.

Solution

In order to verify if your user has a fragmentation issue, adjust the MTU for AnyConnect clients on the ASA.

Uninstall Automatically

Problem

The AnyConnect VPN Client uninstalls itself once the connection terminates. The client logs show that keep installed is set to disabled.

Solution

AnyConnect uninstalls itself despite that the keep installed option is selected on the Adaptive Security Device Manager (ASDM). In order to resolve this issue, configure the svc keep-installer installed command under group-policy.

Issue Populating the Cluster FQDN

Problem: AnyConnect client is pre-populated with the hostname instead of the cluster Fully Qualified Domain Name (FQDN).

When you have a load-balancing cluster set up for SSL VPN and the client attempts to connect to the cluster, the request is redirected to the node ASA and the client logs in successfully. After some time, when the client tries to connect to the cluster again, the cluster FQDN is not seen in the Connect to entries. Instead, the node ASA entry to which the client has been redirected is seen.

Solution

This occurs because the AnyConnect client retains the host name to which it last connected. This behavior is observed and a bug has been filed. For complete details about the bug, refer to Cisco bug ID CSCsz39019. The suggested workaround is to upgrade the Cisco AnyConnect to Version 2.5.

Backup Server List Configuration

A backup server list is configured in case the main server selected by the user is not reachable. This is defined in the Backup Server pane in the AnyConnect profile. Complete these steps:

Download the AnyConnect Profile Editor (registered customers only) . The file name is AnyConnectProfileEditor2_4_1.jar.

Create an XML file with the AnyConnect Profile Editor.

Go to the server list tab.

Click Add.

Type the main server on the Hostname field.

Add the backup server below the backup server list on the Host address field. Then, click Add.

Once you have the XML file, you need to assign it to the connection you use on the ASA.

In ASDM, choose Configuration >Remote Access VPN >Network (Client) Access >AnyConnect Connection Profiles.

Select your profile and click Edit.

Click Manage from the Default Group Policy section.

Select your group-policy and click Edit.

Select Advanced and then click SSL VPN Client.

Click New. Then, you need to type a name for the Profile and assign the XML file.

Connect the client to the session in order to download the XML file.

AnyConnect: Corrupt Driver Database Issue

This entry in the SetupAPI.log file suggests that the catalog system is corrupt:

W239 driver signing class list «C:WINDOWSINFcertclas.inf» was missing or invalid. Error 0xfffffde5: Unknown Error. , assuming all device classes are subject to driver signing policy.

You can also receive this error message: Error(3/17): Unable to start VA, setup shared queue, or VA gave up shared queue .

You can receive this log on the client: «The VPN client driver has encountered an error» .

Repair

This issue is due to Cisco bug ID CSCsm54689. In order to resolve this issue, make sure that Routing and Remote Access Service is disabled before you start AnyConnect. If this does not resolve the issue, complete these steps:

Open a command prompt as an Administrator on the PC (elevated prompt on Vista).

Run net stop CryptSvc .

When prompted, choose OK in order to attempt the repair.

Exit the command prompt.

Failed Repair

If the repair fails, complete these steps:

Open a command prompt as an Administrator on the PC (elevated prompt on Vista).

Run net stop CryptSvc .

Rename the %WINDIR%system32catroot2 to catroot2_old directory.

Exit the command prompt.

Analyze the Database

You can analyze the database at any time in order to determine if it is valid.

Open a command prompt as an Admimistrator on the PC.

Error Messages

Error: Unable to Update the Session Management Database

While the SSL VPN is connected through a web browser, the Unable to Update the Session Management Database. error message appears, and the ASA logs show %ASA-3-211001: Memory allocation Error. The adaptive security appliance failed to allocate RAM system memory .

Solution 1

This issue is due to Cisco bug ID CSCsm51093. In order to resolve this issue, reload the ASA or upgrade the ASA software to the interim release mentioned in the bug. Refer to Cisco bug ID CSCsm51093 for more information.

Solution 2

This issue can also be resolved if you disable threat-detection on ASA if threat-detection is used.

Error: «Module c:Program FilesCiscoCisco AnyConnect VPN Clientvpnapi.dll failed to register»

When you use the AnyConnect client on laptops or PCs, an error occurs during the install:

When this error is encountered, the installer cannot move forward and the client is removed.

Solution

These are the possible workarounds to resolve this error:

The latest AnyConnect client is no longer officially supported with Microsoft Windows 2000. It is a registry problem with the 2000 computer.

Remove the VMware applications. Once AnyConnect is installed, VMware applications can be added back to the PC.

Add the ASA to their trusted sites.

Copy these files from the ProgramFilesCiscoCiscoAnyconnect folder to a new folder and run the regsvr32 vpnapi.dll command prompt:

• vpnapi.dll
• vpncommon.dll
• vpncommoncrypt.dll

Reimage the operating system on the laptop/PC.

The log message related to this error on the AnyConnect client looks similar to this:

Error: «An error was received from the secure gateway in response to the VPN negotiation request. Please contact your network administrator»

When clients try to connect to the VPN with the Cisco AnyConnect VPN Client, this error is received.

This message was received from the secure gateway:

«Illegal address class» or «Host or network is 0» or «Other error»

Solution

The issue occurs because of the ASA local IP pool depletion. As the VPN pool resource is exhausted, the IP pool range must be enlarged.

Cisco bug ID is CSCsl82188 is filed for this issue. This error usually occurs when the local pool for address assignment is exhausted, or if a 32-bit subnet mask is used for the address pool. The workaround is to expand the address pool and use a 24-bit subnet mask for the pool.

Error: Session could not be established. Session limit of 2 reached.

When you try to connect more than two clients with the AnyConnect VPN Client, you receive the Login Failed error message on the Client and a warning message in the ASA logs that states Session could not be established. Session limit of 2 reached . I have the AnyConnect essential license on the ASA, which runs Version 8.0.4.

Solution 1

This error occurs because the AnyConnect essential license is not supported by ASA version 8.0.4. You need to upgrade the ASA to version 8.2.2. This resolves the error.

Note: Regardless of the license used, if the session limit is reached, the user will receive the login failed error message.

Solution 2

This error can also occur if the vpn-sessiondb max-anyconnect-premium-or-essentials-limit session-limit command is used to set the limit of VPN sessions permitted to be established. If the session-limit is set as two, then the user cannot establish more than two sessions even though the license installed supports more sessions. Set the session-limit to the number of VPN sessions required in order to avoid this error message.

Error: Anyconnect not enabled on VPN server while trying to connect anyconnect to ASA

You receive the Anyconnect not enabled on VPN server error message when you try to connect AnyConnect to the ASA.

Solution

This error is resolved if you enable AnyConnect on the outside interface of the ASA with ASDM. For more information on how to enable AnyConnect on the outside interface, refer to Configure Clientless SSL VPN (WebVPN) on the ASA.

Error:- %ASA-6-722036: Group client-group User xxxx IP x.x.x.x Transmitting large packet 1220 (threshold 1206)

The %ASA-6-722036: Group User IP Transmitting large packet 1220 (threshold 1206) error message appears in the logs of the ASA. What does this log mean and how is this resolved?

Solution

This log message states that a large packet was sent to the client. The source of the packet is not aware of the MTU of the client. This can also be due to compression of non-compressible data. The workaround is to turn off the SVC compression with the svc compression none command. This resolves the issue.

Error: The secure gateway has rejected the agent’s vpn connect or reconnect request.

When you connect to the AnyConnect Client, this error is received: «The secure gateway has rejected the agent’s vpn connect or reconnect request. A new connection requires re-authentication and must be started manually. Please contact your network administrator if this problem persists. The following message was received from the secure gateway: no assigned address» .

This error is also received when you connect to the AnyConnect Client: «The secure gateway has rejected the connection attempt. A new connection attempt to the same or another secure gateway is needed, which requires re-authentication. The following message was received from the secure gateway:Host or network is 0» .

This error is also received when you connect to the AnyConnect Client: «The secure gateway has rejected the agent’s vpn connect or reconnect request. A new connection requires a re-authentication and must be started manually. Please contact the network administrator if the problem persists. The following message was received from the secure gateway: No License» .

Solution

The router was missing pool configuration after reload. You need to add the concerned configuration back to the router.

The «The secure gateway has rejected the agent’s vpn connect or reconnect request. A new connection requires a re-authentication and must be started manually. Please contact the network administrator if the problem persists. The following message was received from the secure gateway: No License» error occurs when the AnyConnect mobility license is missing. Once the license is installed, the issue is resolved.

Error: «Unable to update the session management database»

When you try to authenticate in WebPortal, this error message is received: «Unable to update the session management database» .

Solution

This problem is related to memory allocation on the ASA. This issue is mostly encountered when the ASA Version is 8.2.1. Originally, this requires a 512MB RAM for its complete functionality.

As a permanent workaround, upgrade the memory to 512MB.

As a temporary workaround, try to free the memory with these steps:

Disable the threat-detection.

Disable SVC compression.

Error: «The VPN client driver has encountered an error»

This is an error message obtained on the client machine when you try to connect to AnyConnect.

Solution

In order to resolve this error, complete this procedure in order to manually set the AnyConnect VPN agent to Interactive:

Right-click My Computer > Manage > Services and Applications > Services > and select the Cisco AnyConnect VPN Agent.

Right-click Properties, then log on, and select Allow service to interact with the desktop.

This sets the registry Type value DWORD to 110 (default is 010) for the HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesvpnagent.

Note: If this is to be used, then the preference would be to use the .MST transform in this instance. This is because if you set this manually with these methods, it requires that this be set after every install/upgrade process. This is why there is a need to identify the application that causes this problem.

When Routing and Remote Access Service (RRAS) is enabled on the Windows PC, AnyConnect fails with the The VPN client driver has encountered an error. error message. In order to resolve this issue, make sure that Routing and RRAS is disabled before starting AnyConnect. Refer to Cisco bug ID CSCsm54689 for more information.

Error: «Unable to process response from xxx.xxx.xxx.xxx»

AnyConnect clients fail to connect to a Cisco ASA. The error in the AnyConnect window is «Unable to process response from xxx.xxx.xxx.xxx» .

Solution

In order to resolve this error, try these workarounds:

Remove WebVPN from the ASA and reenable it. «Login Denied , unauthorized connection mechanism , contact your administrator» .

Solution

This error message occurs mostly because of configuration issues that are improper or an incomplete configuration. Check the configuration and make sure it is as required to resolve the issue.

Secure VPN via remote desktop is not supported error message appears.

Solution

This issue is due to these Cisco bug IDs: CSCsu22088 and CSCso42825. If you upgrade the AnyConnect VPN Client, it can resolve the issue. Refer to these bugs for more information.

Error: «The server certificate received or its chain does not comply with FIPS. A VPN connection will not be established»

When you attempt to VPN to the ASA 5505, the The server certificate received or its chain does not comply with FIPS. A VPN connection will not be established error message appears.

Solution

In order to resolve this error, you must disable the Federal Information Processing Standards (FIPS) in the AnyConnect Local Policy file. This file can usually be found at C:ProgramDataCiscoCisco AnyConnect VPN ClientAnyConnectLocalPolicy.xml . If this file is not found in this path, then locate the file at a different directory with a path such as C:Documents and SettingsAll UsersApplication DataCisco AnyConnectVPNClientAnyConnectLocalPolicy.xml . Once you locate the xml file, make changes to this file as shown here:

Change the phrase:

true

false

Then, restart the computer. Users must have administrative permissions in order to modify this file.

Error: «Certificate Validation Failure»

Users are unable to launch AnyConnect and receive the Certificate Validation Failure error.

Solution

Certificate authentication works differently with AnyConnect compared to the IPSec client. In order for certificate authentication to work, you must import the client certificate to your browser and change the connection profile in order to use certificate authentication. You also need to enable this command on your ASA in order to allow SSL client-certificates to be used on the outside interface:

ssl certificate-authentication interface outside port 443

Error: «VPN Agent Service has encountered a problem and needs to close. We are sorry for the inconvenience»

When AnyConnect Version 2.4.0202 is installed on a Windows XP PC, it stops at updating localization files and an error message shows that the vpnagent.exe fails.

Solution

This behavior is logged in Cisco bug ID CSCsq49102. The suggested workaround is to disable the Citrix client.

Error: «This installation package could not be opened. Verify that the package exists»

When AnyConnect is downloaded, this error message is received:

«Contact your system administrator. The installer failed with the following error: This installation package could not be opened. Verify that the package exists and that you can access it, or contact the application vendor to verify that this is a valid Windows Installer package.»

Solution

Complete these steps in order to fix this issue:

Remove any anti-virus software.

Disable the Windows firewall.

If neither Step 1 or 2 helps, then format the machine and then install.

If the problem still persists, open a TAC Case.

Error: «Error applying transforms. Verify that the specified transform paths are valid.»

This error message is recieved during the auto-download of AnyConnect from the ASA:

This is the error message received when connecting with AnyConnect for MacOS:

Solution

Complete one of these workarounds in order to resolve this issue:

The root cause of this error might be due to a corrupted MST translation file (for example, imported). Perform these steps to fix this:

Remove the MST translation table.

Configure the AnyConnect image for MacOS in the ASA.

From the ASDM, follow the Network (Client) Access > AnyConnect Custom > Installs path and delete the AnyConnect package file. Make sure the package remains in Network (Client) Access > Advanced > SSL VPN > Client Setting.

If neither of these workarounds resolve the issue, contact Cisco Technical Support.

Error: «The VPN client driver has encountered an error»

This error is received:

Solution

This issue can be resolved when you uninstall the AnyConnect Client, and then remove the anti-virus software. After this, reinstall the AnyConnect Client. If this resolution does not work, then reformat the PC in order to fix this issue.

Error: «A VPN reconnect resulted in different configuration setting. The VPN network setting is being re-initialized. Applications utilizing the private network may need to be restored.»

This error is received when you try to launch AnyConnect:

Solution

In order to resolve this error, use this:

The svc mtu command is replaced by the anyconnect mtu command in ASA Version 8.4(1) and later as shown here:

AnyConnect Error While Logging In

Problem

The AnyConnect receives this error when it connects to the Client:

Solution

The issue can be resolved if you make these changes to the AnyConnect profile:

Add this line to the AnyConnect profile:

IE Proxy Setting is Not Restored after AnyConnect Disconnect on Windows 7

Problem

In Windows 7, if the IE proxy setting is configured for Automatically detect settings and AnyConnect pushes down a new proxy setting, the IE proxy setting is not restored back to Automatically detect settings after the user ends the AnyConnect session. This causes LAN issues for users who need their proxy setting configured for Automatically detect settings.

Solution

This behavior is logged in Cisco bug ID CSCtj51376. The suggested workaround is to upgrade to AnyConnect 3.0.

Error: AnyConnect Essentials can not be enabled until all these sessions are closed.

This error message is received on Cisco ASDM when you attempt to enable the AnyConnect Essentials license:

Solution

This is the normal behavior of the ASA. AnyConnect Essentials is a separately licensed SSL VPN client. It is entirely configured on the ASA and provides the full AnyConnect capability, with these exceptions:

No Cisco Secure Desktop (CSD) (including HostScan/Vault/Cache Cleaner)

No clientless SSL VPN

Optional Windows Mobile Support

This license cannot be used at the same time as the shared SSL VPN premium license. When you need to use one license, you need to disable the other.

Error: Connection tab on Internet option of Internet Explorer hides after getting connected to the AnyConnect client.

The connection tab on the Internet option of Internet Explorer hides after you are connected to the AnyConnect client.

Solution

This is due to the msie-proxy lockdown feature. If you enable this feature, it hides the Connections tab in Microsoft Internet Explorer for the duration of an AnyConnect VPN session. If you disable the feature, it leaves the display of the Connections tab unchanged.

Error: Few users getting Login Failed Error message when others are able to connect successfully through AnyConnect VPN

A few users receive the Login Failed Error message when others can connect successfully through the AnyConnect VPN.

Solution

This issue can be resolved if you make sure the do not require pre-authentication checkbox is checked for the users.

Error: The certificate you are viewing does not match with the name of the site you are trying to view.

During the AnyConnect profile update, an error is shown that says the certificate is invalid. This occurs with Windows only and at the profile update phase. The error message is shown here:

Solution

This can be resolved if you modify the server list of the AnyConnect profile in order to use the FQDN of the certificate.

This is a sample of the XML profile:

Note: If there is an existing entry for the Public IP address of the server such as , then remove it and retain only the FQDN of the server (for example, but not ).

Cannot Launch AnyConnect From the CSD Vault From a Windows 7 Machine

When the AnyConnect is launched from the CSD vault, it does not work. This is attempted on Windows 7 machines.

Solution

Currently, this is not possible because it is not supported.

AnyConnect Profile Does Not Get Replicated to the Standby After Failover

The AnyConnect 3.0 VPN client with ASA Version 8.4.1 software works fine. However, after failover, there is no replication for the AnyConnect profile related configuration.

Solution

This problem has been observed and logged under Cisco bug ID CSCtn71662. The temporary workaround is to manually copy the files to the standby unit.

AnyConnect Client Crashes if Internet Explorer Goes Offline

When this occurs, the AnyConnect event log contains entries similar to these:

Solution

This behavior is observed and logged under Cisco bug ID CSCtx28970. In order to resolve this, quit the AnyConnect application and relaunch. The connection entries reappear after relaunch.

Error Message: TLSPROTOCOL_ERROR_INSUFFICIENT_BUFFER

The AnyConnect client fails to connect and the Unable to establish a connection error message is received. In the AnyConnect event log, the TLSPROTOCOL_ERROR_INSUFFICIENT_BUFFER error is found.

Solution

This occurs when the headend is configured for split-tunneling with a very large split-tunnel list (approximately 180-200 entries) and one or more other client attributes are configured in the group-policy, such as dns-server.

In order to resolve this issue, complete these steps:

Reduce the number of entries in the split-tunnel list.

Use this configuration in order to disable DTLS:

For more information, refer to Cisco bug ID CSCtc41770.

Error Message: «Connection attempt has failed due to invalid host entry»

The Connection attempt has failed due to invalid host entry error message is received while AnyConnect is authenticated with the use of a certificate.

Solution

In order to resolve this issue, try either of these possible solutions:

• Upgrade the AnyConnect to Version 3.0.
• Disable Cisco Secure Desktop on your computer.

For more information, refer to Cisco bug ID CSCti73316.

Error: «Ensure your server certificates can pass strict mode if you configure always-on VPN»

When you enable the Always-On feature on AnyConnect, the Ensure your server certificates can pass strict mode if you configure always-on VPN error message is received.

Solution

This error message implies that if you want to use the Always-On feature, you need a valid sever certificate configured on the headend. Without a valid server certificate, this feature does not work. Strict Cert Mode is an option that you set in the AnyConnect local policy file in order to ensure the connections use a valid certificate. If you enable this option in the policy file and connect with a bogus certificate, the connection fails.

Error: «An internal error occurred in the Microsoft Windows HTTP Services»

This Diagnostic AnyConnect Reporting Tool (DART) shows one failed attempt:

Also, refer to the event viewer logs on the Windows machine.

Solution

This could be caused due to a corrupted Winsock connection. Reset the connection from the command promt with this command and restart your windows machine:

netsh winsock reset

Error: «The SSL transport received a Secure Channel Failure. May be a result of a unsupported crypto configuration on the Secure Gateway.»

This Diagnostic AnyConnect Reporting Tool (DART) shows one failed attempt:

Solution

Windows 8.1 does not support RC4 according to the following KB update:

Either configure DES/3DES ciphers for SSL VPN on the ASA using the command «ssl encryption 3des-sha1 aes128-sha1 aes256-sha1 des-sha1» OR edit the Windows Registry file on the client machine as mentioned below:

Источник

При запуске OpenVPN сервера или подключения из клиента OpenVPN вы можете столкнуться с ошибкой:

All TAP-Windows adapters on this system are currently in use
Exiting due to fatal error

Или

All wintun adapters on this system are currently in use or disabled

Или

No TAP Adapter Available

Вы можете увидеть эту ошибку логе OpenVPN сервера (файл C:Program FilesOpenVPNlogopenvpn.log) или в клиенте OpenVPN GUI/

Это известная ошибка, связанная с тем что в Windows не установлены или некорректно работают виртуальные сетевые адаптеры TAP или wintun.

Чтобы исправить эту ошибку нужно выполнить один из следующих шагов (расположены в порядке от самого простого к самому сложному):

1. Перезапустить TAP-Windows/WinTun через панель управления.
2. Переустановить драйвер TAP-Windows/Wintun;
3. Создать новый сетевой адаптер для OpenVPN (или другого VPN клиента)

Выведите список всех TAP адаптеров, доступных клиенту OpenVPN:

cd "c:Program FilesOpenVPNbin"
“C:Program FilesOpenVPNbinopenvpn.exe” --show-adapters

В нашем случае установлен как Wintun, так и TAP адаптер:

'OpenVPN Wintun' {1199219C-C5AD-4722-B195-C80332101710} wintun
'OpenVPN TAP-Windows6' {9C6B25CA-0AF0-4752-AD4A-032947F6A6FD} tap-windows6

Для устранения ошибки обычно достаточно включить и отключить TAP адаптер в панели управления Windows, перезагрузить компьютер или переустановить клиент OpenVPN.

Вы можете включить и отключить сетевой адаптер WinTap из панели управления ncpa.cpl. Щелкните в панели управления по нужному адаптеру (TAP-Windows или Wintun Userspace Tunnel) и выберите Disable. Затем включите его (Enable.)

Также вы можете перезапустить все сетевые интерфейсе OpenVPN TAP с помощью PowerShell:

$TapAdapter= Get-NetAdapter| where {$_.InterfaceDescription -like "*TAP-Windows*"}
Disable-NetAdapter -Name $TapAdapter -Confirm:$false
Enable-NetAdapter -Name $TapAdapter -Confirm:$false

Если предыдущий способ не помог, попробуйте переустановить драйвера для вашего виртуального TAP адаптера вручную

1. Скачайте последнюю версию TAP драйвера для Windows здесь (http://build.openvpn.net/downloads/releases/). Например, tap-windows-9.24.7.zip или wintun-amd64-0.8.1.
2. Распакуйте архив, запустите Device Manager (devmgmt.msc), щелкните правой кнопкой по сетевому адаптеру TAP-Windows Adapter v9 в секции Network Adapters и выберите Update driver;
3. Укажите путь к каталогу с драйвером TAP.

Если вы не видите в панели управления TAP-Windows Adapter V9, откройте консоль Device Manager и включите опцию View-> Show hidden device.

Если в секции Network adapters есть устройства типа unknown device, откройте его свойства, перейдите на вкладку Details и проверьте значение свойства Device instance path.

Если здесь указано ROOTNET000, значит попробуйте выполнить авматотический поиск дрвйвера или вручную укажите путь к INF файлу (например C:Program FilesOpenVPN Connectdriverstapamd64win10OemVista.inf). После этого в панели управления появится ваш TAP адаптер.

В Windows 7 драйвер TAP, подписанный с помощью SHA256, не будет работать корректно, пока вы вручную не установите обновление KB4474419.

В самых редких случаях может помочь полное пересоздание TAP/Wintun адаптера.

Перед установкой нужно удалить существующий сетевой адаптер TAP и его драйвер. Для этого запустите программу C:Program FilesTAP-WindowsUninstall.exe или просто удалите устройство из Device Manager (Uninstall device).

Для установки TAP драйвера используется утилита tapinstall.exe.

Распакуйте архив и запустите установочный файл с правами администратора.

В новых версиях OpenVPN для управления виртуальными сетевыми адаптерами используется утилита c:Program FilesOpenVPNbintapctl.exe.

Вывести список сетевых адаптеров OpenVPN:

tapctl.exe list

Удалить адаптер:

tapctl.exe delete "OpenVPN TAP-Windows6"

Создать новый адаптер TAP:

tapctl.exe create

Создать новый wintun адаптер:

tapctl.exe create --hwid wintun

Обязательно проверьте, что новый сетевой адаптер TAP-Windows Adapter появился в списке сетевых подключения в панели управления Windows (консоль ncpa.cpl).

Также ошибка “ All TAP-Windows adapters on the system are currently in use” может возникнуть, если вы пытаетесь установить несколько OpenVPN подключений с одного компьютера. Для каждого VPN подключения нужно создать свой адаптер.

Вы можете создать дополнительный WinTap сетевой адаптер с помощью скрипта (bat файл) %ProgramFiles%TAP-Windowsbinaddtap.bat.

Или с помощью команды (в современных версиях клиента OpenVPN):

c:Program FilesOpenVPNbintapctl.exe.tapctl.exe create

В результате в панели управления появится два (или более) сетевых адаптеров TAP-Windows Adapter V9, и вы сможете одновременно установить несколько одновременных OpenVPN сессий с разными серверами.

Теперь вы можете использовать ваше OpenVPN подключение в Windows и настроить автоматическое подключение к VPN. [/alert]

I’m getting the same error, here are some more details:

running: Windows Server 2003, IIS 6.0 / ASP 3.0,
2.13 GHz, 1 GB ram

My web site is in Beta, so I hardly have any visitors to the site.

According to the event viewer I’m getting this warning 3 times every 3 minutes,
then it stops for a few hours.

Then sometimes I get the error:

A process serving application pool ‘DefaultAppPool’ terminated unexpectedly. The process id was ‘3900’. The process exit code was ‘0x800703e9’.

which follow by:

Application pool ‘DefaultAppPool’ is being automatically disabled due to a series of failures in the process(es) serving that application pool.

Which then causes a ‘Service Unavailable’ message when browsing to the website.

after reading too many post about this issue, I did the following steps:

1. I read that it might be registry access right, so I installed a monitor and trace all the W3SVC Access Denied errors and grant permition

2. I read that the 0x800703e9 error means stack over flow which causes a w3wp.exe crash and I should install a Debug tool and try to get a memory dump.
   I did that but I didn’t get any dump, so I installed a new debugging tool, but didn’t got a crash yet.

My web site is doing some data mining which keeps the server busy.

Conclusion:

1. I don’t know what is going on there… but I do know that my server machine is way to slow on resource, so I’m going to upgrade and reinstall it, I’m certain that it will solve the problem…

2. The problem happens all the time, even when my .net code is idle, therefore it is a problem in the server, and not in my code.

3. I think that the first warnning “A process serving application pool …» happens every some time, and every now and then it causes the Application Pool to restart, therefore a attaching a debugger doesn’t help — the process keeps restarting and the debugger is not effective any longer…
   I think that the 0x800703e9 error (which causes the Service Unavailable) maybe happens when the app pool restart, I guess that it needs a lot of resource and since my machine is too slow it gets the 0x800703e9 … as said before this is a stack over flow, but I think that it is caused by low resource and not by an endless recursion.

4. I think that the ‘registry access right’ which is claimed by Microsoft to be the issue, is nonsense, but I didn’t got ‘Service Unavailable’ since so it might helped (thought I still get the warnning “A process serving application pool …» ).

Hope this help someone…

Some Windows users are reportedly getting the ‘Connection attempt failed‘ error when running the Cisco AnyConnect application in the hopes of establishing a virtual private network (VPN). This issue is reported to occur with Windows 8.1 and Windows 10.

As it turns out, this particular issue can occur due to several different common scenarios. Here’s a list of potential culprits that might be triggering this error code:

• Missing Hotfix for TLS Protocol Renegotiation – As it turns out, there are a couple of updates with the potential of causing issues with Cisco AnyConnect. Several affected users have managed to fix the issue by installing every pending update in order to resolve the inconsistency with the TLS protocol renegotiation and fallback behavior.
• Incompatibility with Windows 10 – According to a lot of Windows 10 users, you can expect to see this problem occurring due to an incompatibility affecting the SSL/TLS API that inhibits the Cisco AnyConnect tool from communicating with an outside server. In this case, you should be able to resolve the issue by forcing the vpnui.exe file to open in compatibility mode with Windows 8.
• Error caused by Windows Update KB 3034682 – If you find yourself in a scenario where the issue suddenly started to occur after WU installed update KB 3034682, chances are the update contains a problematic security rule that is interfering with Cisco AnyConnect. In this case, you can resolve the issue by uninstalling and hiding the problematic update with a specialized utility.
• Hyper-V Conflict on Windows 10 – It’s a well-known fact that Hyper-V is known to conflict with a lot of VPN facilitators such as Cisco AnyConnect and this scenario is no exception. If you find yourself in this scenario, you should be able to resolve the issue by disabling Hyper-V prior to launching the application.
• Connection Sharing is Enabled – As it turns out, you can also expect to see this error code popping up due to a network sharing functionality that interferes with Cisco AnyConnect. If this scenario is applicable, you should be able to fix the problem by disabling the network connection sharing from the Network Connections tab.
• Internet Explorer is configured to Work Offline – Since Cisco AnyConnect and IE share some common functionality, you can expect to see this error in those situations where IE’s offline mode is enabled by default. In this case, you can fix the issue by making some changes via the Registry Editor.

Now that you know every potential scenario that might be responsible for the apparition of the ‘Connection attempt failed‘ error, here’s a list of verified methods that other users have successfully deployed in order to bypass the error message:

1. Install every Pending Windows Update

As it turns out, one of the most common instances that might trigger this problem is a security update (3023607) that ends up affecting the default behavior regarding the TLS protocol renegotiation and fallback behavior.

According to some affected users, the issue was finally resolved after they run the Microsoft Update utility and installed every security and cumulative update including March cumulative security update for Internet Explorer (MS15-018) and Vulnerability in SChannel could allow security feature bypass: March 10, 2015 (MS15-031).

If you’re not certain that you have every available Windows update installed on your computer, follow the instructions below:

1. Press Windows key + R to open up a Run dialog box. Next, type ”ms-settings:windowsupdate’ and press Enter to open up the Windows Update tab of the Settings app.
2. Inside the Windows update screen, go ahead and click on Check for updates. Next, follow the on-screen prompts to install every Windows update that is currently scheduled to be installed.

   Note: Install every type of update including cumulative and security updates, not just important ones.

3. You should keep in mind that if you have a lot of pending updates, you will be prompted to restart before every update is installed. If this happens, restart your PC as instructed, but make sure to return to this screen at the next startup and finish the installation of the rest of the updates.
4. After every pending update is installed, reboot your computer once again and see if the Cisco AnyConnect error is now fixed.

2. Run Cisco AnyConnect in Compatibility Mode (Windows 10 only)

If installing every pending update didn’t do the trick for you or you’re encountering the issue on Windows 10, chances are you’re dealing with an incompatibility issue. This most commonly occurs due to a Critical Windows 10 Update (3023607) that changes some details in regards to the SSL/TLS API in a way that breaks the Cisco AnyConnect app.

If you face this issue on Windows 10, the easiest way to fix it is to force the main executable (the one you use to launch Cisco AnyConnect) to run in Compatibility Mode with Windows 8.

In case you find yourself in this particular scenario, follow the instructions below to force the vpnui.exe executable to run in compatibility mode with Windows 8:

1. Open File Explorer and navigate to the location where you installed the Cisco AnyCOnnect Mobility Client folder. Unless you installed the utility in a custom location, you’ll find it in:

   C:Program Files (x86)CiscoCisco AnyConnect Secure Mobility Client

2. Once you’re inside the correct location, right-click on vpnui.exe and click on the Properties entry from the context menu that just appeared.
3. Once you’re inside the Properties screen, click on Compatibility, then go to Compatibility mode and check the box where it says ‘Run this program in compatibility mode for:’.
4. After checking the box, it will unlock a list of other versions of Windows, select the list and click on Windows 8.
5. Finally, click on Apply and launch the game to see if the graphics error still occurs.

If you already tried forcing the vpnui.exe executable to run in compatibility mode with Windows 8 and you’re still seeing the same Connection attempt failed error, move down to the next potential fix below.

3. Uninstalling & hide the KB 3034682 update

If the first 2 methods did not work for you or were not applicable, the last resort would be to simply uninstall the problematic update that is causing the update on Windows 10 (3034682).

However, keep in mind that unless you take some steps to hide the problematic update, it will eventually find your way onto your computer and cause the same issue all over again after several system restarts.

But you can prevent this from occurring by using the Microsoft Show or Hide troubleshooter to hide the problematic update after you uninstall the KB 3034682 update.

If you’re looking for specific instructions on how to do this, follow the instructions below:

1. Press Windows key + R to open up a Run dialog box. Next, type “ms-settings:windowsupdate” inside the text box and press Enter to open up the Windows Update screen of the Settings app.
2. Inside the Windows Update screen, click on View Update history from the left-hand section of the screen.
3. Next, from the list of recently installed updates loads up, click on Uninstall updates (at the top of the screen).
4. Scroll down through the list of installed updates and locate the KB3034682 update inside the list of installed updates.
5. After you manage to locate the correct update, right-click on it and choose Uninstall from the context menu. Then, click Yes at the confirmation prompt to start the process.
6. Once the update has been uninstalled, visit the download page of the Microsoft Show or Hide troubleshooter package and download the troubleshooter.
7. Once the download is complete, open the .diagcab file and immediately click on the Advanced button. Next, check the box associated with Apply Repairs Automatically.
8. Hit Next to advance to the next menu and wait for the utility to finish the scan for updates before finally clicking on Hide Updates.
9. Once the operation is complete, check the box associated with the update that you want to hide, then click on Next to advance to hide the selected update from Windows Update.
10. Finally, wait until the procedure is complete, then restart your computer and see if the issue has been resolved once the next startup sequence is complete.

If the same issue is still occurring even after you went through the trouble of uninstalling and hiding the problematic update, move down to the next potential fix below.

4. Disabling Hyper-V (Windows 10)

As it turns out, it turns out that you can also expect to encounter this error due to a conflict between Cisco AnyConnect and the main Hyper-V service that’s enabled by default on Windows 10.

Several affected users that were also encountering this problem have reported that they finally managed to fix the ‘Connection attempt failed’ error by temporarily disabling Hyper-V and all associated services before rebooting the computer and using Cisco AnyConnect.

If you suspect this scenario might be applicable to your current situation, follow the instructions below to disable Hyper-V from the Windows Features menu:

1. Start by pressing Windows key + R to open up a Run dialog box. Inside the text box, type ‘appwiz.cpl’ and press Enter to open up the Programs and Features menu. If you are prompted by the UAC (User Account Control), click Yes to grant admin access.
2. Next, from the Programs and Features menu, use the menu on the left to click on Turn Windows features on or off. At the User Account Control prompt, click Yes to grant admin access.
3. Once you’re inside the Windows Features screen, scroll down through the list of Windows Features and uncheck the box associated with Hyper-V. Next, click on Ok to save the changes.
4. Once the Hyper-V functionality is disabled, restart your computer and see if the problem is fixed once the next startup is complete.

5. Disable Network Connection sharing

If none of the methods above have worked for you, and you are currently sharing a network connection via the Microsoft Hosted Network Virtual Adapter, you might be able to resolve the ‘Connection attempt failed‘ error by disabling the shared network connection.

If this scenario is applicable to your particular scenario, several affected users have managed to fix this issue by accessing the Network Connections tab and modifying the default Sharing configuration so that network connection sharing is not allowed.

If you’re looking for specific step-by-step instructions on how to do this, follow the instructions below:

1. Start by press Windows key + R to open up a Run dialog box. Inside the ‘ncpa.cpl’ inside the text box and press Enter to open up the Network Connections tab. If you’re prompted by the UAC (User Account Control), click Yes to grant admin access.
2. Inside the Network Connections tab, look through the list of network adapters and identify the one created specifically for hosting hotspot networks. Traditionally, it should be named Microsoft Hosted Network Virtual Adapter. 
3. Once you identify the correct network adapter, right-click on it and choose Properties from the context menu that just appeared.

   Note: When you see the UAC (User Account Control), click Yes to grant admin access.

4. Inside the Properties screen of the Microsoft Hosted Network Virtual Adapter, access the Sharing tab from the menu at the top, then uncheck the box associated with Allow other network users to connect through this computer’s Internet connection.
   
5. Finally, click Ok to save the changes, then restart your computer.
6. Attempt to start the hotspot network once again and see if the issue is now resolved.

In case the same kind of problem is still occurring, move down to the next potential fix below.

6. Disable IE’S Ability to Work Offline via Registry Editor

If none of the methods above have proven to be effective in your case, it’s also possible to face this problem to the fact that Internet Explorer is configured to ‘work in offline mode’. IE’s Offline mode is notoriously known to conflict with a lot of VPN facilitators such as the Cisco AnyConnect software.

This would not be a problem if Microsoft didn’t remove the option to change this default behavior and made it so that the option now defaults to online.

Since there’s no longer an option to make this modification from the GUI menu, you’ll have to resort to a Registry modification.

Follow the instructions below to disable Internet Explorer’s ability to work in Offline Mode via Registry Editor:

1. Press Windows key + R to open up a Run dialog box. Next, type ‘regedit’ and press Ctrl + Shift + Enter to open up an elevated Registry Editor prompt. When you are prompted by the UAC (User Account Control), click Yes to grant admin access.
2. Inside the Registry Editor, use the left-hand side menu to navigate to the following location:

   HKEY_CURRENT_USERSoftwareMicrosoftWindowsCurrentVersionInternet Settings

   Note: You can either navigate to this location manually or you can paste the location directly into the navigation bar and press Enter to get there instantly.

3. Once you get to the correct location, move down to the right-hand side section and locate the GlobalUserOffline DWORD key.
4. When you see it, double-click on it and set the Base to Hexadecimal and the value to 0, and click Ok to save the changes.
5. Restart your computer and see if the problem is fixed once the next startup is complete.