01-10-2022 02:51 PM - edited 01-10-2022 03:08 PM
I've been using AnyConnect from my home PC to log into my company VPN for a while, but it suddenly started failing to connect with some weird behavior at the end of December. After I attempt to connect to the VPN and go through my login verification, here's what happens from the message history:
3:36:16 PM Establishing VPN session...
3:36:16 PM The AnyConnect Downloader is performing update checks...
3:36:16 PM Checking for profile updates...
3:36:16 PM Checking for product updates...
3:36:16 PM Checking for customization updates...
3:36:16 PM Performing any required updates...
3:36:16 PM The AnyConnect Downloader updates have been completed.
3:36:16 PM Establishing VPN - Initiating connection...
3:36:17 PM Establishing VPN session...
3:36:17 PM Establishing VPN - Examining system...
3:36:17 PM Establishing VPN - Activating VPN adapter...
3:36:58 PM Establishing VPN - Repairing VPN adapter...
3:37:40 PM Connection attempt has failed.
3:37:40 PM VPN session ended.
In addition, my computer seems to be creating multiple new network connections; every time I attempt to log in it creates one new Ethernet connection with a "Surfshark Tunnel" network adapter (note: I uninstalled Surfshark years ago), and then another one for the Cisco AnyConnect Secure Mobility Client Connection. The more times I try to log in, the more Ethernet connections are created. Also, in Device Manager I have a Surfshark Tunnel network adapter, but looking at the driver details, it's the Cisco driver under another name.
Things I've tried:
Any help would be appreciated.
Solved! Go to Solution.
01-11-2022 12:20 PM
Managed to find a solution to this, though it seems pretty ugly: for some reason the network adapter was using "Surfshark Tunnel" as its display name, even though the driver itself was for AnyConnect. So, I went and changed the FriendlyName field in the Windows registry at Computer\HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\ROOT\NET\0000 to "Cisco AnyConnect Secure Mobility Client Virtual Miniport Adapter for Windows x64" ... and now AnyConnect works, which is sorta shocking.
01-11-2022 12:20 PM
Managed to find a solution to this, though it seems pretty ugly: for some reason the network adapter was using "Surfshark Tunnel" as its display name, even though the driver itself was for AnyConnect. So, I went and changed the FriendlyName field in the Windows registry at Computer\HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\ROOT\NET\0000 to "Cisco AnyConnect Secure Mobility Client Virtual Miniport Adapter for Windows x64" ... and now AnyConnect works, which is sorta shocking.
11-09-2023 11:07 AM
Wow yeah, this worked. I tried everything under the sun. This one finally did it. Thank you. Mine was named NLWT TUN. You're right about it being shocking. Do better Cisco.
09-22-2023 10:48 AM
Throw that MF in the trash!!
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide