connection attempt failed cisco anyconnect что делать

12.07.202212.07.2022 admin 0 Comments

How to Fix Cisco Anyconnect ‘Connection attempt failed’ on Windows 10

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.

Connection Attempt Failed with Cisco AnyConnect

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:

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:

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:

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:

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:

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:

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:

Источник

Fix Cisco AnyConnect error Connection attempt failed

Some users of Windows 10 who use the Cisco AnyConnect tool on a regular basis, have come across an error that is called, Connection attempt failed. This usually happens when you’re attempting to run a virtual private network (VPN) but worry not because there are ways to solve it. It can also due to a network or PC issue and you are asked to verify internet connectivity and try again.

Cisco AnyConnect error Connection attempt failed

Let us discuss this from a more detailed perspective.

1] Open Cisco AnyConnect via Compatibility Mode

To do this, you must first source the primary executable file. Not everyone knows how to get this done, so if you fall under that category, then you will want to open the File Explorer and navigate to the following location:

After accessing the folder, please right-click on vpnui.exe, then select Properties.

From there, go to Compatibility > Compatibility mode. Finally, check the box where it says, Run this program in compatibility mode for.

Select Windows 8 or Windows 7 from the list, then hit Apply > OK.

Restart your computer, then attempt to run Cisco AnyConnect once more to see if the Connection attempt failed error still makes an appearance.

2] Disable Microsoft Hyper V in Windows 10

One other way to solve the Connection attempt failure is to turn off Hyper V in Windows 10. There are three easy steps to take in order to disable Hyper V.

As you will see from the article, there are multiple ways to disable Hyper V, so use the method that works best for you.

3] Turn off Internet Connection sharing

If the options above fail, then your next step is to disable Internet Connection Sharing from within Windows 10. It’s quite easy, and you will learn all you need to know once you’ve read every word.

Date: June 3, 2021 Tags: Network

Fix Error 0x80070043, Windows cannot access, The Network name cannot be found

How to update Network drivers in Windows 11/10

Network & Internet Settings in Windows 11

[email protected]

Vamien McKalin possesses the awesome power of walking on water like a boss. He’s also a person who enjoys writing about technology, comics, video games, and anything related to the geek world.

Источник

connection attempt has failed anyconnect

[11/11/2013 1:55:55 PM] Ready to connect. [11/11/2013 1:57:05 PM] Contacting —.—.—.— [11/11/2013 1:57:07 PM] Please enter your username and password. [11/11/2013 1:57:08 PM] User credentials entered. [11/11/2013 1:57:08 PM] Establishing VPN session. [11/11/2013 1:57:09 PM] Checking for profile updates. [11/11/2013 1:57:09 PM] Checking for product updates. [11/11/2013 1:57:10 PM] Checking for customization updates. [11/11/2013 1:57:10 PM] Performing any required updates. [11/11/2013 1:57:15 PM] Establishing VPN session. [11/11/2013 1:57:15 PM] Establishing VPN — Initiating connection. [11/11/2013 1:57:16 PM] Disconnect in progress, please wait. [11/11/2013 1:57:29 PM] Connection attempt has failed. [11/11/2013 1:59:31 PM] Ready to connect.

Я попытался отключить брандмауэр и антивирус. Я не думал, что это будет иметь значение, поскольку мой ноутбук использует тот же брандмауэр и антивирус, и мне не нужно было его отключать. Мой ноутбук использует Windows 7 Home 64-bit, а мой компьютер с ошибкой использует 64-разрядную версию Windows 7 Ultimate.

6 ответов

Решением для меня было отключить общий доступ к подключению Интернета (ICS).

Чтобы устранить эту проблему:

Я вижу, что отключение ICS не работало для OP, но это работало для меня и многих других, по мнению различных форумов, кажется.

ответ Натана на этой странице не работал для меня, потому что флажки Allow other network users[. ] были очищены для всех все равно.

Я отключил ICS таким образом:

KB ID 0001279В DtdВ 31/01/17

Problem

We had a firewall fail at work this week, as part of the rebuild the latest OS was put on it, version 9.7(1). I thought no more about it until I tried to VPN in and got this;

I used my Windows 10 VM and that connected fine, only my MacBook could not connect, this VPN tunnel is a big deal I need it to get onto client’s networks. I tried my other VPN connections and every one was fine, only the recently rebuilt one didn’t work? Ive seen OSX throw a wobbly with AnyConnect in the past so I did a complete uninstall, В deleted the opt/cisco folder and put on the latest version (4.4.00243 at time of writing) no change.

Connection attempt has failed due to server communication errors. Please retry the connection

A look in the client message history showed me this..

No valid certificates available for authentication.

I checked my certificates, and the certificate on the firewall both they, (and the certificate chain,) were fine.

Debugging AnyConnect gave NO OUTPUT at all, but debugging SSL showed me this;

Try Googling that and getting a result! In fact that’s probably what brought you here.

Solution

If you change a Cisco OS and things like this stop working normally it’s because they’ve dropped support for something that’s got a security hole in it. In the wake of the Poodle Exploit I assumed it was an SSL/TLS problem, but that wasn’t it.

I was in the right ball park though, and a bit of lateral thinking and SSL cipher problems I’ve had with ASDM, made me think, what if it’s SHA that’s been dropped because everyone is dropping SHA1 cause it’s the hashing algorithm of Satan?

Well as soon as I added a SHA1 ciphers back in, everything started working again!

Disclaimer: SHA1 is bad, where practical all cert ciphers should be at least SHA256