-
December 9th, 2015, 06:26 PM
#1
ERROR_failed_connection_initialisation while connection (Android)
Hello,
I can not connect a server. I always get this error «ERROR_failed_connection_initialisation while connection».
My Smartphone: Sony Xperia Z3 Compact with Android 5.1.1
Here is the Logfile from the Teamspeak App (I tried to connect to the official server):
08.12.2015 9:20:14 nachm. com.teamspeak.ts3client.StartGUIFragment onCreate
INFO: Start
08.12.2015 9:20:14 nachm. com.teamspeak.ts3client.StartGUIFragment onCreate
INFO: Finished loading GUI
08.12.2015 9:20:17 nachm. com.teamspeak.ts3client.StartGUIFragment w
INFO: Found Audio RECSampleRate:44100
08.12.2015 9:20:17 nachm. com.teamspeak.ts3client.StartGUIFragment w
INFO: Found Audio PLAYSampleRate:44100
08.12.2015 9:20:17 nachm. com.teamspeak.ts3client.a.k a
INFO: recSa:44100 PlaySa:44100 RecS:0 PlayS:0
08.12.2015 9:20:17 nachm. com.teamspeak.ts3client.bookmark.e a
INFO: Loading lib
08.12.2015 9:20:17 nachm. com.teamspeak.ts3client.data.e n
INFO: Start AUDIO
08.12.2015 9:20:17 nachm. com.teamspeak.ts3client.data.e n
INFO: Setting PTT: false
08.12.2015 9:20:17 nachm. com.teamspeak.ts3client.data.e n
INFO: Setting BT:false
08.12.2015 9:20:18 nachm. com.teamspeak.ts3client.tsdns.j run
INFO: 9 -> ERROR TS_TYPE_SRVTS3: _ts3._udp.voice.teamspeak.com
08.12.2015 9:20:18 nachm. com.teamspeak.ts3client.tsdns.j run
INFO: 0 -> TS_TYPE_DIRECT: Result for voice.teamspeak.com: 194.97.114.2
08.12.2015 9:20:18 nachm. com.teamspeak.ts3client.tsdns.j run
INFO: 7 -> ERROR TS_TYPE_SRVTSDNS: _tsdns._tcp.voice.teamspeak.com
08.12.2015 9:20:18 nachm. com.teamspeak.ts3client.tsdns.j run
INFO: 6 -> ERROR TS_TYPE_SRVTSDNS: _tsdns._tcp.voice.teamspeak.com
08.12.2015 9:20:18 nachm. com.teamspeak.ts3client.tsdns.j run
INFO: 5 -> TS_TYPE_SRVTSDNS: Result for _tsdns._tcp.teamspeak.com: 194.97.114.2
08.12.2015 9:20:18 nachm. com.teamspeak.ts3client.tsdns.f b
INFO: PUBLISH:0 — 5 — 194.97.114.2 — 9987
08.12.2015 9:20:18 nachm. com.teamspeak.ts3client.ConnectionBackground a
INFO: Connect status: STATUS_CONNECTING
08.12.2015 9:20:18 nachm. com.teamspeak.ts3client.tsdns.j run
INFO: 2 -> TS_TYPE_TSDNS: Result for voice.teamspeak.com: 194.97.114.2
08.12.2015 9:20:18 nachm. com.teamspeak.ts3client.data.e a
INFO: ClientLib Connect_return:0
08.12.2015 9:20:18 nachm. com.teamspeak.ts3client.tsdns.j run
INFO: 3 -> TS_TYPE_TSDNS: Result for voice.teamspeak.com: 194.97.114.2
08.12.2015 9:20:21 nachm. com.teamspeak.ts3client.tsdns.j run
INFO: 1 -> ERROR TS_TYPE_TSDNS: voice.teamspeak.com
08.12.2015 9:20:23 nachm. com.teamspeak.ts3client.ConnectionBackground a
INFO: Connect status: STATUS_DISCONNECTED
08.12.2015 9:20:32 nachm. com.teamspeak.ts3client.t d
INFO: Stop AUDIO
08.12.2015 9:20:32 nachm. com.teamspeak.ts3client.t d
INFO: Disconnecting from Server
08.12.2015 9:20:32 nachm. com.teamspeak.ts3client.a.k b
INFO: Release Audio
08.12.2015 9:20:32 nachm. com.teamspeak.ts3client.t d
INFO: ClientLib closed
08.12.2015 9:20:32 nachm. com.teamspeak.ts3client.t d
INFO: Connect status: STATUS_DISCONNECTEDWhat can I do to resolve this problem?
-
December 15th, 2015, 12:49 PM
#2
Connection problems can have mayn reason. There is no general way to solve them.
But you can try one of these:
http://forum.teamspeak.com/threads/9…of-information
by Vlad Constantinescu
Vlad might have a degree in Animal Husbandry and Livestock Management, but he’s currently rocking anything software related, ranging from testing programs to writing in-depth reviews about them…. read more
Updated on December 22, 2020
- Cisco AnyConnect is a popular business VPN solution that lets users access corporate resources remotely from any supported device.
- However, sometimes it may face certain technical difficulties. The connection subsystem initialization failure error is by far one of the most common issues.
- Check out our Cisco Hub to discover more Cisco-related guides, news, and fixes.
- Visit our VPN Troubleshooting section to learn how you can fix more common VPN issues.
Cisco AnyConnect is more than just a VPN, as it empowers your workforce to be able to work from any location, on any device, and at any time.
However, this doesn’t mean that it’s free of errors. In fact, it has quite a few issues, but thankfully none of them is without a solution.
One of the most common problems is the failed to initialize the connection subsystem in Cisco AnyConnect error.
Apparently, it mostly occurs for Windows users, but it also happens in the following scenarios:
- Establishing VPN connections with Cisco AnyConnect Secure Mobility Client app on Windows 8.1, RT 8.1, or Windows Server 2012 R2
- After installing Windows update 3023607 on your computer
Microsoft has confirmed that the failed to initialize connection subsystem in Cisco AnyConnect error is related to Microsoft products.
Namely:
Windows Server 2012 R2 Datacenter, Standard, Essentials and Foundation, Windows 8.1 Enterprise and Pro, Windows 8.1, and Windows RT 8.1.
Check out some solutions that can help you work around this error and fix it on your computer.
Failed to initialize connection subsystem in Cisco AnyConnect error fix
Go to Microsoft Update
You can install the most recent cumulative security update for Internet Explorer directly from Windows’ built-in update tool.
Alternatively, you could download and apply the update manually.
However, if you choose the latter, you should check the Affected Software table in Microsoft’s Security Bulletin MS15-018 for download links.
If this didn’t do the trick, move on to our next suggested fix.
Run compatibility troubleshooter on Cisco AnyConnect
The failed to initialize connection subsystem in Cisco AnyConnect error usually has to do with a recent Windows Update.
Having issues while installing Cisco AnyConnect? Check out our guide and learn how to bypass them easily.
However, you can also use Cisco AnyConnect’s proprietary troubleshooter tool to try and solve it.
All you have to do is follow these steps:
- Close Cisco AnyConnect
- Go to the Cisco AnyConnect Secure Mobility Client folder:
C:Program Files (x86)CiscoCisco AnyConnect Secure Mobility Client
- Right-click vpnui.exe
- Click Run compatibility troubleshooter
- Select Try recommended settings
- Go with the wizard’s suggestion (Windows 8 compatibility)
- Click Test Program to open the program
- Close
Note: For vpnagent.exe – the local service that supports the client user interface – you may need to repeat these steps.
Disable Internet Connection Sharing
Use the registry editor
If you have the failed to initialize connection subsystem in Cisco AnyConnect error, you can fix it by making a small edit to the registry using the steps below:
- Right-click Start
- Select Run
- Type regedit
- Press Enter
- Go to HKEY_CURRENT_USERSoftwareMicrosoftWin
- Create a new key called GlobalOfflineUser
- Give it 1 as the value
- Restart your computer and load the VPN
Check whether you are able to connect.
Conclusion
All things considered, if you encounter the failed to initialize the connection subsystem in Cisco AnyConnect error, there are ways to fix it.
We recommend you try our suggested methods one by one. We’re confident you’ll find one that eventually does the trick.
Which one of our suggested fixes worked best for you? Let us know by dropping a comment in the section below.
Your connection is not secure — websites you visit can find out your details:
- Your IP Address:
loading
Companies can sell this information, alongside your location and internet provider name, and profit from it by serving targeted ads or monitoring your data usage.
We recommend Private Internet Access, a VPN with a no-log policy, open source code, ad blocking and much more; now 79% off.
Today I tried to use my VPN connection to one of my business client on my laptop running Windows 10 Technical Preview with the Cisco AnyConnect Secure Mobility Client version 3.1.03103.
PROBLEM
When I tried to connect with Cisco VPN Client, I received the following error:
Failed to initialize connection subsystem.
SOLUTION 1
I reinstalled the Cisco AnyConnect Secure Mobility Client and still received the same error. Obviously, I was using a beta version and knew some of the applications may not work. I then configured the Cisco AnyyConnet Client to run in Windows 8 compatibility mode and was able to get the VPN client to work without even rebooting the computer. Here’s the step-by-step procedure.
- If you have upgraded your Windows 8 to Windows 10 Technical Preview, remove the Cisco AnyConnect client and then reinstall it.
- Go to C:Program Files (x86)CiscoCisco AnyConnect Secure Mobility Client where the VPN client is installed.
- Right-click the file vpnui.exe and select Troubleshoot compatibility.
- On the Program Compatibility Troubleshooter screen select the option Try recommended settings.
- On the next screen select Yes, save the settings for this program.
- You will notice the system applies the settings and configures the compatibility mode to Windows 8. You must click Test the program but you will notice the clicking the button doesn’t do anything at all. That’s okay. You must click the link at least once in order to click Next at the bottom of the screen.
- The next screen shows the problem was fixed for this incompatible program. Click Close.
- Run the Services Console (services.msc).
- Restart the Cisco AnyConnect Secure Mobility Agent service.
- Try to run the Cisco VPN client. There is no need to reboot the computer. It Cisco VPN client should start without the error.
SOLUTION 2
Another option that might work for you requires a registry hack. You need to add a key (that is missing in newer Windows version, including Windows 10). This registry key enables/disables the Internet Explorer’s ability to work offline. Here’s Microsoft’s standard warning about working with the registry.
WARNING: Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk.
- Start the registry editor (RegEdit.exe).
- Go to HKEY_CURRENT_USERSoftwareMicrosoftWindowsCurrentVersionInternet Settings.
- Add a new DWORD (32-bit) Value called GlobalUserOffline and set it to 0 (that’s a zero).
- Here’s a KB article from Microsoft that applies to older versions of IE but explains this registry key in more detail.
If you are having this issue in Windows 8/8.1 you may want to try one of the above solutions but I should point out that I didn’t have any issues with this client in Windows 8/8.1. I would love to hear if either solution worked for you.
Copyright ©2014 Zubair Alexander. All rights reserved.
This div height required for enabling the sticky sidebar
We use cookies on our website to give you the most relevant experience by remembering your preferences and repeat visits. By clicking “Accept”, you consent to the use of ALL the cookies.
Describe the bug
I can’t connect to my server because of this
Logs
Client
8/10/2018 17:21:46 ClientUI Info Connect to server: 192.168.2.39
8/10/2018 17:21:46 ClientUI Info Initiating connection: 192.168.2.39:9987
8/10/2018 17:21:46 ClientUI Info Connect status: Connecting
8/10/2018 17:21:46 PktHandler Devel Puzzle solve time: 0
8/10/2018 17:21:47 SCHandler Info more virtual server slots than the server license allows - abort connection
8/10/2018 17:21:47 SCHandler Warning Error while parsing packet: failed connection initialization
8/10/2018 17:21:47 ClientUI Info Connect status: Disconnected
8/10/2018 17:21:47 ClientUI Info Failed to connect to server, want autoreconnect = 0
Server
Full Trace Log: https://gist.github.com/82777201f41d21ce100ee2d6c4970d5b
[2018-08-10 19:09:47] [ERROR] GEN | [WebList] Invalid web manager key response (-1) Error Resource temporarily unavailable
[2018-08-10 19:09:52] [ERROR] 1 | [192.168.2.36:57818/undefined] Handling of packet Init1 needs more than 10ms (23ms)
[2018-08-10 19:09:52] [ERROR] 1 | [192.168.2.36:57818/undefined] Handling of packet Init1 needs more than 10ms (172ms)
[2018-08-10 19:09:52] [ERROR] 1 | [192.168.2.36:57818/undefined] Handling of packet Command needs more than 10ms (22ms)
[2018-08-10 19:09:57] [ERROR] Timer VoiceClient::tick needs more than 21 milliseconds. Max allowed was 3 milliseconds.
[2018-08-10 19:09:57] [INFO] 1 | Voice client 0/lKH+LiXlQdPi9HkhCDjC+yMkDBY= (undefined) from 192.168.2.36:57818 left.
[2018-08-10 19:10:04] [ERROR] 1 | [192.168.2.36:57818/undefined] Handling of packet Init1 needs more than 10ms (180ms)
[2018-08-10 19:10:04] [ERROR] 1 | [192.168.2.36:57818/undefined] Handling of packet Command needs more than 10ms (15ms)
[2018-08-10 19:10:04] [ERROR] 1 | Command handling of command clientinit needs 132ms
[2018-08-10 19:10:04] [ERROR] 1 | [192.168.2.36:57818/felix] Handling of packet Command needs more than 10ms (136ms)
[2018-08-10 19:10:04] [INFO] 1 | Voice client 3/lKH+LiXlQdPi9HkhCDjC+yMkDBY= (felix) from 192.168.2.36:57818 joined.
[2018-08-10 19:10:05] [ERROR] 1 | Ticking of client 192.168.2.36:57818 (felix) needs more that 2500 microseconds! (3696 microseconds)
[2018-08-10 19:10:06] [ERROR] Timer VoiceClient::tick -> resend needs more than 4140 microseconds. Max allowed was 3000 microseconds.
[2018-08-10 19:10:06] [ERROR] 1 | Ticking of client 192.168.2.36:57818 (felix) needs more that 2500 microseconds! (6054 microseconds)
[2018-08-10 19:10:14] [ERROR] 1 | Ticking of client 192.168.2.36:57818 (felix) needs more that 2500 microseconds! (2513 microseconds)
[2018-08-10 19:10:24] [ERROR] 1 | Ticking of client 192.168.2.36:57818 (felix) needs more that 2500 microseconds! (2620 microseconds)
[2018-08-10 19:10:25] [ERROR] Timer VoiceClient::tick needs more than 15 milliseconds. Max allowed was 3 milliseconds.
[2018-08-10 19:10:25] [ERROR] 1 | Ticking of client 192.168.2.36:57818 (felix) needs more that 2500 microseconds! (17561 microseconds)
[2018-08-10 19:10:26] [INFO] 1 | Voice client 3/lKH+LiXlQdPi9HkhCDjC+yMkDBY= (felix) from 192.168.2.36:57818 left.
[2018-08-10 19:10:47] [ERROR] 1 | [192.168.2.36:57818/undefined] Handling of packet Init1 needs more than 10ms (128ms)
[2018-08-10 19:10:47] [ERROR] 1 | [192.168.2.36:57818/undefined] Handling of packet Command needs more than 10ms (15ms)
[2018-08-10 19:10:47] [ERROR] 1 | Command handling of command clientinit needs 44ms
[2018-08-10 19:10:47] [ERROR] 1 | [192.168.2.36:57818/felix] Handling of packet Command needs more than 10ms (47ms)
[2018-08-10 19:10:47] [INFO] 1 | Voice client 3/lKH+LiXlQdPi9HkhCDjC+yMkDBY= (felix) from 192.168.2.36:57818 joined.
[2018-08-10 19:11:07] [ERROR] Timer VoiceClient::tick needs more than 4131 microseconds. Max allowed was 3000 microseconds.
[2018-08-10 19:11:07] [ERROR] Timer VoiceClientConnection::invokePacketResend() - disconnect needs more than 15 milliseconds. Max allowed was 5 milliseconds.
[2018-08-10 19:11:07] [ERROR] Timer VoiceClient::tick -> resend needs more than 17 milliseconds. Max allowed was 3 milliseconds.
[2018-08-10 19:11:07] [ERROR] 1 | Ticking of client 192.168.2.36:57818 (felix) needs more that 2500 microseconds! (25331 microseconds)
[2018-08-10 19:11:08] [INFO] 1 | Voice client 3/lKH+LiXlQdPi9HkhCDjC+yMkDBY= (felix) from 192.168.2.36:57818 left.
[2018-08-10 19:17:34] [INFO] GEN | Stopping instance
[2018-08-10 19:17:34] [INFO] GEN | Stopping all server instances!
[2018-08-10 19:17:34] [INFO] GEN | Stopping application
[2018-08-10 19:17:36] [INFO] GEN | Application suspend successful!
Environment information:
Operating system: Linux minopia.de 4.14.52-v7+ #1123 SMP Wed Jun 27 17:35:49 BST 2018 i686 GNU/Linux
TeaSpeak version: v1.2.4-beta [Build: 1533846495]
Using TeaSpeak x86 via exagear on a RPi3B+
-
December 9th, 2015, 06:26 PM
#1
ERROR_failed_connection_initialisation while connection (Android)
Hello,
I can not connect a server. I always get this error «ERROR_failed_connection_initialisation while connection».
My Smartphone: Sony Xperia Z3 Compact with Android 5.1.1
Here is the Logfile from the Teamspeak App (I tried to connect to the official server):
08.12.2015 9:20:14 nachm. com.teamspeak.ts3client.StartGUIFragment onCreate
INFO: Start
08.12.2015 9:20:14 nachm. com.teamspeak.ts3client.StartGUIFragment onCreate
INFO: Finished loading GUI
08.12.2015 9:20:17 nachm. com.teamspeak.ts3client.StartGUIFragment w
INFO: Found Audio RECSampleRate:44100
08.12.2015 9:20:17 nachm. com.teamspeak.ts3client.StartGUIFragment w
INFO: Found Audio PLAYSampleRate:44100
08.12.2015 9:20:17 nachm. com.teamspeak.ts3client.a.k a
INFO: recSa:44100 PlaySa:44100 RecS:0 PlayS:0
08.12.2015 9:20:17 nachm. com.teamspeak.ts3client.bookmark.e a
INFO: Loading lib
08.12.2015 9:20:17 nachm. com.teamspeak.ts3client.data.e n
INFO: Start AUDIO
08.12.2015 9:20:17 nachm. com.teamspeak.ts3client.data.e n
INFO: Setting PTT: false
08.12.2015 9:20:17 nachm. com.teamspeak.ts3client.data.e n
INFO: Setting BT:false
08.12.2015 9:20:18 nachm. com.teamspeak.ts3client.tsdns.j run
INFO: 9 -> ERROR TS_TYPE_SRVTS3: _ts3._udp.voice.teamspeak.com
08.12.2015 9:20:18 nachm. com.teamspeak.ts3client.tsdns.j run
INFO: 0 -> TS_TYPE_DIRECT: Result for voice.teamspeak.com: 194.97.114.2
08.12.2015 9:20:18 nachm. com.teamspeak.ts3client.tsdns.j run
INFO: 7 -> ERROR TS_TYPE_SRVTSDNS: _tsdns._tcp.voice.teamspeak.com
08.12.2015 9:20:18 nachm. com.teamspeak.ts3client.tsdns.j run
INFO: 6 -> ERROR TS_TYPE_SRVTSDNS: _tsdns._tcp.voice.teamspeak.com
08.12.2015 9:20:18 nachm. com.teamspeak.ts3client.tsdns.j run
INFO: 5 -> TS_TYPE_SRVTSDNS: Result for _tsdns._tcp.teamspeak.com: 194.97.114.2
08.12.2015 9:20:18 nachm. com.teamspeak.ts3client.tsdns.f b
INFO: PUBLISH:0 — 5 — 194.97.114.2 — 9987
08.12.2015 9:20:18 nachm. com.teamspeak.ts3client.ConnectionBackground a
INFO: Connect status: STATUS_CONNECTING
08.12.2015 9:20:18 nachm. com.teamspeak.ts3client.tsdns.j run
INFO: 2 -> TS_TYPE_TSDNS: Result for voice.teamspeak.com: 194.97.114.2
08.12.2015 9:20:18 nachm. com.teamspeak.ts3client.data.e a
INFO: ClientLib Connect_return:0
08.12.2015 9:20:18 nachm. com.teamspeak.ts3client.tsdns.j run
INFO: 3 -> TS_TYPE_TSDNS: Result for voice.teamspeak.com: 194.97.114.2
08.12.2015 9:20:21 nachm. com.teamspeak.ts3client.tsdns.j run
INFO: 1 -> ERROR TS_TYPE_TSDNS: voice.teamspeak.com
08.12.2015 9:20:23 nachm. com.teamspeak.ts3client.ConnectionBackground a
INFO: Connect status: STATUS_DISCONNECTED
08.12.2015 9:20:32 nachm. com.teamspeak.ts3client.t d
INFO: Stop AUDIO
08.12.2015 9:20:32 nachm. com.teamspeak.ts3client.t d
INFO: Disconnecting from Server
08.12.2015 9:20:32 nachm. com.teamspeak.ts3client.a.k b
INFO: Release Audio
08.12.2015 9:20:32 nachm. com.teamspeak.ts3client.t d
INFO: ClientLib closed
08.12.2015 9:20:32 nachm. com.teamspeak.ts3client.t d
INFO: Connect status: STATUS_DISCONNECTEDWhat can I do to resolve this problem?
-
December 15th, 2015, 12:49 PM
#2
Connection problems can have mayn reason. There is no general way to solve them.
But you can try one of these:
http://forum.teamspeak.com/threads/9…of-information
by Vlad Constantinescu
Vlad might have a degree in Animal Husbandry and Livestock Management, but he’s currently rocking anything software related, ranging from testing programs to writing in-depth reviews about them…. read more
Updated on December 22, 2020
- Cisco AnyConnect is a popular business VPN solution that lets users access corporate resources remotely from any supported device.
- However, sometimes it may face certain technical difficulties. The connection subsystem initialization failure error is by far one of the most common issues.
- Check out our Cisco Hub to discover more Cisco-related guides, news, and fixes.
- Visit our VPN Troubleshooting section to learn how you can fix more common VPN issues.
Cisco AnyConnect is more than just a VPN, as it empowers your workforce to be able to work from any location, on any device, and at any time.
However, this doesn’t mean that it’s free of errors. In fact, it has quite a few issues, but thankfully none of them is without a solution.
One of the most common problems is the failed to initialize the connection subsystem in Cisco AnyConnect error.
Apparently, it mostly occurs for Windows users, but it also happens in the following scenarios:
- Establishing VPN connections with Cisco AnyConnect Secure Mobility Client app on Windows 8.1, RT 8.1, or Windows Server 2012 R2
- After installing Windows update 3023607 on your computer
Microsoft has confirmed that the failed to initialize connection subsystem in Cisco AnyConnect error is related to Microsoft products.
Namely:
Windows Server 2012 R2 Datacenter, Standard, Essentials and Foundation, Windows 8.1 Enterprise and Pro, Windows 8.1, and Windows RT 8.1.
Check out some solutions that can help you work around this error and fix it on your computer.
Failed to initialize connection subsystem in Cisco AnyConnect error fix
Go to Microsoft Update
You can install the most recent cumulative security update for Internet Explorer directly from Windows’ built-in update tool.
Alternatively, you could download and apply the update manually.
However, if you choose the latter, you should check the Affected Software table in Microsoft’s Security Bulletin MS15-018 for download links.
If this didn’t do the trick, move on to our next suggested fix.
Run compatibility troubleshooter on Cisco AnyConnect
The failed to initialize connection subsystem in Cisco AnyConnect error usually has to do with a recent Windows Update.
Having issues while installing Cisco AnyConnect? Check out our guide and learn how to bypass them easily.
However, you can also use Cisco AnyConnect’s proprietary troubleshooter tool to try and solve it.
All you have to do is follow these steps:
- Close Cisco AnyConnect
- Go to the Cisco AnyConnect Secure Mobility Client folder:
C:Program Files (x86)CiscoCisco AnyConnect Secure Mobility Client
- Right-click vpnui.exe
- Click Run compatibility troubleshooter
- Select Try recommended settings
- Go with the wizard’s suggestion (Windows 8 compatibility)
- Click Test Program to open the program
- Close
Note: For vpnagent.exe – the local service that supports the client user interface – you may need to repeat these steps.
Disable Internet Connection Sharing
Use the registry editor
If you have the failed to initialize connection subsystem in Cisco AnyConnect error, you can fix it by making a small edit to the registry using the steps below:
- Right-click Start
- Select Run
- Type regedit
- Press Enter
- Go to HKEY_CURRENT_USERSoftwareMicrosoftWin
- Create a new key called GlobalOfflineUser
- Give it 1 as the value
- Restart your computer and load the VPN
Check whether you are able to connect.
Conclusion
All things considered, if you encounter the failed to initialize the connection subsystem in Cisco AnyConnect error, there are ways to fix it.
We recommend you try our suggested methods one by one. We’re confident you’ll find one that eventually does the trick.
Which one of our suggested fixes worked best for you? Let us know by dropping a comment in the section below.
Your connection is not secure — websites you visit can find out your details:
-
- Your IP Address:
loading
Companies can sell this information, alongside your location and internet provider name, and profit from it by serving targeted ads or monitoring your data usage.
We recommend Private Internet Access, a VPN with a no-log policy, open source code, ad blocking and much more; now 79% off.
Newsletter
Today I tried to use my VPN connection to one of my business client on my laptop running Windows 10 Technical Preview with the Cisco AnyConnect Secure Mobility Client version 3.1.03103.
PROBLEM
When I tried to connect with Cisco VPN Client, I received the following error:
Failed to initialize connection subsystem.
SOLUTION 1
I reinstalled the Cisco AnyConnect Secure Mobility Client and still received the same error. Obviously, I was using a beta version and knew some of the applications may not work. I then configured the Cisco AnyyConnet Client to run in Windows 8 compatibility mode and was able to get the VPN client to work without even rebooting the computer. Here’s the step-by-step procedure.
- If you have upgraded your Windows 8 to Windows 10 Technical Preview, remove the Cisco AnyConnect client and then reinstall it.
- Go to C:Program Files (x86)CiscoCisco AnyConnect Secure Mobility Client where the VPN client is installed.
- Right-click the file vpnui.exe and select Troubleshoot compatibility.
- On the Program Compatibility Troubleshooter screen select the option Try recommended settings.
- On the next screen select Yes, save the settings for this program.
- You will notice the system applies the settings and configures the compatibility mode to Windows 8. You must click Test the program but you will notice the clicking the button doesn’t do anything at all. That’s okay. You must click the link at least once in order to click Next at the bottom of the screen.
- The next screen shows the problem was fixed for this incompatible program. Click Close.
- Run the Services Console (services.msc).
- Restart the Cisco AnyConnect Secure Mobility Agent service.
- Try to run the Cisco VPN client. There is no need to reboot the computer. It Cisco VPN client should start without the error.
SOLUTION 2
Another option that might work for you requires a registry hack. You need to add a key (that is missing in newer Windows version, including Windows 10). This registry key enables/disables the Internet Explorer’s ability to work offline. Here’s Microsoft’s standard warning about working with the registry.
WARNING: Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk.
- Start the registry editor (RegEdit.exe).
- Go to HKEY_CURRENT_USERSoftwareMicrosoftWindowsCurrentVersionInternet Settings.
- Add a new DWORD (32-bit) Value called GlobalUserOffline and set it to 0 (that’s a zero).
- Here’s a KB article from Microsoft that applies to older versions of IE but explains this registry key in more detail.
If you are having this issue in Windows 8/8.1 you may want to try one of the above solutions but I should point out that I didn’t have any issues with this client in Windows 8/8.1. I would love to hear if either solution worked for you.
Copyright ©2014 Zubair Alexander. All rights reserved.
This div height required for enabling the sticky sidebar
We use cookies on our website to give you the most relevant experience by remembering your preferences and repeat visits. By clicking “Accept”, you consent to the use of ALL the cookies.
Windows Server 2012 R2 Datacenter Windows Server 2012 R2 Standard Windows Server 2012 R2 Essentials Windows Server 2012 R2 Foundation Windows 8.1 Enterprise Windows 8.1 Pro Windows 8.1 Windows RT 8.1 More…Less
Symptoms
This issue occurs when the following conditions are true:
-
You run a Cisco AnyConnect Secure Mobility Client application to establish virtual private network (VPN) connections in Windows 8.1, Windows RT 8.1, or Windows Server 2012 R2.
-
You have installed update 3023607 on the computer. For more information about update 3023607, see the Secure Channel cumulative update changes TLS protocol renegotiation and fallback behavior.
Resolution
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the «Applies to» section.
References
See the terminology that Microsoft uses to describe software updates.
More Information
The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.
Need more help?
Не удалось инициализировать подсистему подключения в Cisco AnyConnect. Ошибка в Windows.
Cisco AnyConnect – это больше, чем просто виртуальная частная сеть, поскольку она позволяет вашей рабочей силе работать из любого места, на любом устройстве и в любое время.
Это упрощает безопасный доступ к конечным точкам, обеспечивая безопасность, необходимую для обеспечения безопасности и защиты вашего бизнеса.
Некоторые из его основных функций и преимуществ включают в себя высокозащищенный доступ к сетевому предприятию из любого места и с любого устройства, лучшую видимость поведения пользователей и конечных точек по всему предприятию, комплексную защиту от угроз независимо от того, где они находятся, а также упрощенное управление и удобство использования на всех устройствах. в помещении и за его пределами, с одним агентом.
Хотя все эти функции и преимущества удивительны, при попытке соединения с AnyConnect Cisco вы можете столкнуться с некоторыми общими проблемами устранения неполадок.
Одна из таких распространенных проблем – когда вы получаете не удалось инициализировать подсистему соединения в ошибке Cisco AnyConnect, особенно при использовании операционной системы Windows.
Эта проблема возникает, когда выполняются следующие условия:
- Вы запускаете приложение Cisco AnyConnect Secure Mobility Client для установки VPN-подключений в Windows 8.1, RT 8.1 или Windows Server 2012 R2.
- Вы установили обновление Windows 3023607 на свой компьютер
Microsoft подтвердила, что не удалось инициализировать подсистему подключения в Cisco AnyConnect ошибка в продуктах Microsoft, таких как Windows Server 2012 R2 Datacenter, Standard, Essentials и Foundation, Windows 8.1 Enterprise и Pro, Windows 8.1 и Windows RT 8.1.
Ознакомьтесь с некоторыми решениями, которые могут помочь вам обойти эту ошибку и устранить ее на своем компьютере.
Не удалось инициализировать подсистему подключения в ошибке Cisco AnyConnect
- Перейти в Центр обновления Майкрософт
- Запустите средство устранения неполадок совместимости на Cisco AnyConnect
- Отключить общий доступ к подключению к Интернету
- Изменить реестр
1. Зайдите в Центр обновления Майкрософт
Центр обновления Майкрософт поможет вам установить самое последнее накопительное обновление для системы безопасности Internet Explorer, поскольку уязвимость в SChannel делает возможным обход функций безопасности: 10 марта 2015 г. (MS15-031).
Если вы загружаете и устанавливаете обновления вручную, проверьте ссылки на скачивание в таблице «Подвержены уязвимости» в бюллетене по безопасности Microsoft MS15-018.
Если это не поможет, попробуйте следующее решение.
2. Запустите средство устранения неполадок совместимости на Cisco AnyConnect
Не удалось инициализировать подсистему подключения в Cisco AnyConnect ошибка обычно связана с недавним Центром обновления Windows, поэтому вы можете запустить средство устранения неполадок совместимости для решения проблемы, выполнив следующие действия:
- Закройте окно Cisco AnyConnect и мини-значок панели задач
- Перейдите в папку клиента Cisco AnyConnect Secure Mobility – вы можете проверить в C: Program Files (x86) Cisco Cisco AnyConnect Secure Mobility Client .
- Щелкните правой кнопкой мыши vpnui.exe .
- Нажмите Запустить средство устранения неполадок совместимости .
- Выберите Попробуйте рекомендуемые настройки .
- Выберите, что предлагает мастер (совместимость с Windows
- Нажмите Тестовая программа , чтобы открыть программу.
- близко
Примечание. Для vpnagent.exe – локальной службы, которая поддерживает пользовательский интерфейс клиента – вам может потребоваться повторить эти шаги.
Это исправило не удалось инициализировать подсистему соединения в ошибке Cisco AnyConnect? Если нет, попробуйте следующее решение.
- ТАКЖЕ ЧИТАЙТЕ: как включить клиент Cisco VPN в Windows 10
3. Отключите общий доступ к Интернету
Иногда не удалось инициализировать подсистему подключения в Cisco AnyConnect ошибка может произойти, потому что в вашей локальной сети включен общий доступ к подключению к Интернету (ICS).
Вот как это решить:
- Нажмите Пуск .
- Выберите Настройки .
- Нажмите Сеть и Интернет .
- В поле поиска введите Локальный .
- Выберите Просмотр локальных служб .
- Нажмите правой кнопкой мыши на Общий доступ к подключению к Интернету .
- Выберите Свойства .
- Перейдите на вкладку Общие .
- Перейдите в Тип запуска .
- Нажмите стрелку раскрывающегося списка и выберите Отключено .
4. Отредактируйте реестр
Если вам не удалось инициализировать подсистему подключения в ошибке Cisco AnyConnect, вы можете исправить ее, внеся небольшое изменение в реестр, выполнив следующие действия:
- Нажмите правой кнопкой мыши Пуск .
- Выберите Выполнить .
- Введите regedit
- Нажмите Enter .
- Перейдите на страницу HKEY_CURRENT_USER Software Microsoft Win .
- Создайте новый ключ с именем GlobalOfflineUser .
- Введите значение 1 в качестве значения
- Перезагрузите компьютер и загрузите VPN
Проверьте, можете ли вы подключиться.
Было ли какое-либо из этих решений исправить ошибку инициализации подсистемы подключения в Cisco AnyConnect? Дайте нам знать, оставив комментарий в разделе ниже.
Источник
Ошибка Cisco AnyConnect VPN: «не удалось инициализировать подсистему подключения.»
мой клиент CICSO AnyConnect VPN на Windows 7 вдруг начал давать ошибку:
не удалось инициализировать подсистему связи.
перезагрузка не помогала. Как я могу решить эту проблему?
4 ответов
последний патч для Windows-вторник обновление -KB3023607 — вызывает ту же проблему с Cisco AnyConnect VPN. Возможные варианты исправления:
на панели задач Windows щелкните правой кнопкой мыши значок Cisco AnyConnect и выберите Quit.
откройте Проводник и перейдите в: C:Program Files (x86)CiscoCisco AnyConnect Secure Mobility Client .
найти vpnui.exe щелкните правой кнопкой мыши на нем и выберите опцию устранение неполадок совместимости.
Выберите Попробовать Рекомендуемые Настройки.
Нажмите кнопку тестовая программа (обратите внимание, что Windows выбирает режим совместимости Windows 7 в случае вы должны установить его вручную). Выбор «Протестируйте программу» запустит клиента Cisco AnyConnect, давая вам тест шанс входа в систему. Это должно сработать.
Как только доказано, что Cisco AnyConnect работает, выберите для сохранения настроек. Если это не работает, средство устранения неполадок дает вам варианты пробовать снова с различными установками. Совместимости Windows 7 работал для меня, и я запускаю Windows 8.1.
Устранение неполадок совместимости программ даст вам окончательный отчет. Закрыть средство устранения неполадок, и вы должны быть хорошо идти.
решение Fix it, описанное в этом разделе, не предназначено в качестве замены для любого обновления безопасности. Мы рекомендуем вам всегда установите последние обновления безопасности. Тем не менее, мы предлагаем это исправить решение как обходной путь для некоторых сценариев.
чтобы установить или удалить это решение, нажмите кнопку Исправить или ссылка под заголовком включить это исправление или отключить это исправление заголовок. Нажмите кнопку Выполнить в диалоговом окне загрузка файла и следуйте шаги мастера Fix it.
Источник
Cisco AnyConnect VPN Error: “Failed to initialize connection subsystem.”
My Cicso AnyConnect VPN client on Windows 7 suddenly started giving the error:
Failed to initialize connection subsystem.
Rebooting didn’t help. How can I resolve this?
4 Answers 4
The most recent Windows patch-Tuesday update — KB3023607 — causes the same problem with Cisco AnyConnect VPN. Your options for correcting this include:
On the Windows Taskbar, right-click on the Cisco AnyConnect icon and choose Quit.
Open File Explorer and navigate to: C:Program Files (x86)CiscoCisco AnyConnect Secure Mobility Client .
Find vpnui.exe , right-click on it, and then choose the Troubleshoot Compatibility option.
Choose Try Recommended Settings.
Click Test Program (notice that Windows chooses Windows 7 compatibility mode in case you have to set it manually). Choosing to «Test the Program» will launch the Cisco AnyConnect client, giving you the chance test logging in. It should work.
Once it’s proven that Cisco AnyConnect works, choose to save the settings. If it doesn’t work, the troubleshooter gives you the options of trying again with different settings. The Windows 7 compatibility worked for me and I run Windows 8.1.
Program Compatibility Troubleshooter will give you a final report. Close the troubleshooter and you should be good to go.
The Fix it solution that’s described in this section is not intended as a replacement for any security update. We recommend that you always install the latest security updates. However, we offer this Fix it solution as a workaround for some scenarios.
To install or remove this Fix it solution, click the Fix it button or link under the Enable this fix it heading or the Disable this fix it heading. Click Run in the File Download dialog box, and then follow the steps in the Fix it Wizard.
Источник
Describe the bug
I can’t connect to my server because of this
Logs
Client
8/10/2018 17:21:46 ClientUI Info Connect to server: 192.168.2.39
8/10/2018 17:21:46 ClientUI Info Initiating connection: 192.168.2.39:9987
8/10/2018 17:21:46 ClientUI Info Connect status: Connecting
8/10/2018 17:21:46 PktHandler Devel Puzzle solve time: 0
8/10/2018 17:21:47 SCHandler Info more virtual server slots than the server license allows - abort connection
8/10/2018 17:21:47 SCHandler Warning Error while parsing packet: failed connection initialization
8/10/2018 17:21:47 ClientUI Info Connect status: Disconnected
8/10/2018 17:21:47 ClientUI Info Failed to connect to server, want autoreconnect = 0
Server
Full Trace Log: https://gist.github.com/82777201f41d21ce100ee2d6c4970d5b
[2018-08-10 19:09:47] [ERROR] GEN | [WebList] Invalid web manager key response (-1) Error Resource temporarily unavailable
[2018-08-10 19:09:52] [ERROR] 1 | [192.168.2.36:57818/undefined] Handling of packet Init1 needs more than 10ms (23ms)
[2018-08-10 19:09:52] [ERROR] 1 | [192.168.2.36:57818/undefined] Handling of packet Init1 needs more than 10ms (172ms)
[2018-08-10 19:09:52] [ERROR] 1 | [192.168.2.36:57818/undefined] Handling of packet Command needs more than 10ms (22ms)
[2018-08-10 19:09:57] [ERROR] Timer VoiceClient::tick needs more than 21 milliseconds. Max allowed was 3 milliseconds.
[2018-08-10 19:09:57] [INFO] 1 | Voice client 0/lKH+LiXlQdPi9HkhCDjC+yMkDBY= (undefined) from 192.168.2.36:57818 left.
[2018-08-10 19:10:04] [ERROR] 1 | [192.168.2.36:57818/undefined] Handling of packet Init1 needs more than 10ms (180ms)
[2018-08-10 19:10:04] [ERROR] 1 | [192.168.2.36:57818/undefined] Handling of packet Command needs more than 10ms (15ms)
[2018-08-10 19:10:04] [ERROR] 1 | Command handling of command clientinit needs 132ms
[2018-08-10 19:10:04] [ERROR] 1 | [192.168.2.36:57818/felix] Handling of packet Command needs more than 10ms (136ms)
[2018-08-10 19:10:04] [INFO] 1 | Voice client 3/lKH+LiXlQdPi9HkhCDjC+yMkDBY= (felix) from 192.168.2.36:57818 joined.
[2018-08-10 19:10:05] [ERROR] 1 | Ticking of client 192.168.2.36:57818 (felix) needs more that 2500 microseconds! (3696 microseconds)
[2018-08-10 19:10:06] [ERROR] Timer VoiceClient::tick -> resend needs more than 4140 microseconds. Max allowed was 3000 microseconds.
[2018-08-10 19:10:06] [ERROR] 1 | Ticking of client 192.168.2.36:57818 (felix) needs more that 2500 microseconds! (6054 microseconds)
[2018-08-10 19:10:14] [ERROR] 1 | Ticking of client 192.168.2.36:57818 (felix) needs more that 2500 microseconds! (2513 microseconds)
[2018-08-10 19:10:24] [ERROR] 1 | Ticking of client 192.168.2.36:57818 (felix) needs more that 2500 microseconds! (2620 microseconds)
[2018-08-10 19:10:25] [ERROR] Timer VoiceClient::tick needs more than 15 milliseconds. Max allowed was 3 milliseconds.
[2018-08-10 19:10:25] [ERROR] 1 | Ticking of client 192.168.2.36:57818 (felix) needs more that 2500 microseconds! (17561 microseconds)
[2018-08-10 19:10:26] [INFO] 1 | Voice client 3/lKH+LiXlQdPi9HkhCDjC+yMkDBY= (felix) from 192.168.2.36:57818 left.
[2018-08-10 19:10:47] [ERROR] 1 | [192.168.2.36:57818/undefined] Handling of packet Init1 needs more than 10ms (128ms)
[2018-08-10 19:10:47] [ERROR] 1 | [192.168.2.36:57818/undefined] Handling of packet Command needs more than 10ms (15ms)
[2018-08-10 19:10:47] [ERROR] 1 | Command handling of command clientinit needs 44ms
[2018-08-10 19:10:47] [ERROR] 1 | [192.168.2.36:57818/felix] Handling of packet Command needs more than 10ms (47ms)
[2018-08-10 19:10:47] [INFO] 1 | Voice client 3/lKH+LiXlQdPi9HkhCDjC+yMkDBY= (felix) from 192.168.2.36:57818 joined.
[2018-08-10 19:11:07] [ERROR] Timer VoiceClient::tick needs more than 4131 microseconds. Max allowed was 3000 microseconds.
[2018-08-10 19:11:07] [ERROR] Timer VoiceClientConnection::invokePacketResend() - disconnect needs more than 15 milliseconds. Max allowed was 5 milliseconds.
[2018-08-10 19:11:07] [ERROR] Timer VoiceClient::tick -> resend needs more than 17 milliseconds. Max allowed was 3 milliseconds.
[2018-08-10 19:11:07] [ERROR] 1 | Ticking of client 192.168.2.36:57818 (felix) needs more that 2500 microseconds! (25331 microseconds)
[2018-08-10 19:11:08] [INFO] 1 | Voice client 3/lKH+LiXlQdPi9HkhCDjC+yMkDBY= (felix) from 192.168.2.36:57818 left.
[2018-08-10 19:17:34] [INFO] GEN | Stopping instance
[2018-08-10 19:17:34] [INFO] GEN | Stopping all server instances!
[2018-08-10 19:17:34] [INFO] GEN | Stopping application
[2018-08-10 19:17:36] [INFO] GEN | Application suspend successful!
Environment information:
Operating system: Linux minopia.de 4.14.52-v7+ #1123 SMP Wed Jun 27 17:35:49 BST 2018 i686 GNU/Linux
TeaSpeak version: v1.2.4-beta [Build: 1533846495]
Using TeaSpeak x86 via exagear on a RPi3B+