locked
Cisco VPN no longer working since upgrade to 8.1

    General discussion

  • Hi,

    I am by no means a tech head but does anyone know why this may have now stopped working? It worked fine under windows 8 but since applying the evaluation update it now tries to connect for a while then comes up with a termination message as its obviosuly not connecting. Have tried looking at the Meraki platform but this doesn't work as I understand the server I am trying to connect to also has to be using this, which I believe it isn't

    Any ideas would be appreciated,

    Thanks!

    Thursday, June 27, 2013 1:58 PM

All replies

  • I too am having a similar issue.

    Installing the Windows 8.1 Consumer Preview overwrote my network connections (along with my graphics card drivers). I figured a re-install of the Cisco IPSec VPN client would resolve the issue. 

    Instead, upon re-installing the Client, BOTH of my network adapters were really, really broken. Despite having a wired connection, my Local Area Connection wasn't showing up, along with the VPN adapter. The only connection I had was a Bluetooth connection.

    So, sometimes when your connection to the nearest hop is broken, the adapter will lease you a 169.254.x.x address. Not my PC. I get no lease. I cannot ping. I cannot tracert. No DNS, DHCP, TCPIP. Meanwhile, 'diagnosing' the issue using Windows' built-in tool identifies the issue as the NIC not being able to get a DHCP lease, but fails immediately and cannot rectify the issue.

    My only solution to getting a working network connection is to uninstall the Cisco VPN Client. I'm posting here because this is the first Google hit for "Windows 8.1 Cisco VPN client issues", and I'm clearly not the only person having an issue.

    If anyone has any ideas, they are much appreciated.

    Thursday, June 27, 2013 10:53 PM
  • After some struggle I was able to get the Cisco IPsec VPN client to work.

    Not sure exactly what eventually fixed it but I did make the usual registry change, which didn't seem to work at first, so I uninstalled the vpn and re-installed then rebooted and this time it worked.

    Browse to the Registry: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\CVirtA

     Select the DisplayName to modify, and remove the leading characters from the value data up to "%;" i.e. For x86, change the value data from the path similar to: "@oem8.inf,%CVirtA_Desc%;Cisco Systems VPN Adapter” to just "Cisco Systems VPN Adapter” For x64, change the value data from the path similar to: "@oem8.inf,%CVirtA_Desc%;Cisco Systems VPN Adapter for 64-bit Windows” to just "Cisco Systems VPN Adapter for 64-bit Windows”.

    Close the Registry Editor and try connecting again to Cisco VPN


    DWW

    Friday, June 28, 2013 1:07 AM
  • I am also having the same issue.
    Friday, June 28, 2013 9:36 AM
  • Me too. Since it wasn't working, I tried to reinstall it... and this actually disconnected all my network connexions. It looks like Cisco VPN regularly crashes after new release from MS. Currently I found a post about my specific issue that I will try tonight.

    http://social.technet.microsoft.com/Forums/windows/en-US/04c086d0-cce8-41d4-870c-efc63a2622ec/windows-8-64bit-cisco-vpn-50070440-disables-all-internet-after-installation

    But my advise is to search also for topics on Windows 8 and not only Windows 8.1 to find solutions. Good luck all.

    Friday, June 28, 2013 12:12 PM
  • This resolved it for me:

    Go to control panel > Device Manager > Network Adapters > Cisco AnyConnect......

    There were 2 adapters with the same name "Cisco AnyConnect Secure Mobility Client...."

    Removed one. If the other one is disabled, enable it.

    Try to connect and see if it works.

    Friday, June 28, 2013 12:48 PM
  • What version AnyConnect client are you using?
    Saturday, June 29, 2013 1:26 AM
  • I'm also having similar issues. I have the Cisco VPN client (5.0.07.0290) and it worked fine in Windows 8 WITH the registry fix. The display name fix worked fine before...

    After upgrading to Windows 8.1, the registry fix doesn't work anymore. I'm forced to boot into a VM every time.

    Saturday, June 29, 2013 1:01 PM
  • I'm having the same issue with Windows 8.1 and the cicso VPN (5.0.07.0440) with a strange twist.

    I could not connect, same as everyone else so I...

    Uninstalled.

    Reinstalled.

    Fixed the registry key.

    Rebooted.

    Removed the extra Cisco Systems VPN Adapter for Windows x64 in the device manager

    Rebooted.

    Then I was able to connect...Once!  I got connected, I could reach my work servers.  I disconnected, then tried to reconnect, Boom adapter error, ugh!

    Rebooted, still can't connect.

    Tried stopping and starting the Cisco VPN service, still nothing.

    Why is it that my android tablet has this VPN access built into it natively and Microsoft does not!!!  This would solve all of our issues with the Cisco VPN client every time a new version of Windows comes out.  Get on the ball Microsoft!  Group XAuth IPsec with PSK!

    Saturday, June 29, 2013 5:12 PM
  • also have the same issue with Cisco Anyconnect Mobility VPN as well as Cisco VPN Client.

    device manager shows a bunch of network devices with yellow exclamation marks, all basically indicating that windows was unable to load the driver.

    The only thing working there on this Surface Pro is the built in wifi network adapter and Bluetooth adapter

    All the adapters that end with "Deterministic Network Enhancer Miniport" are all broken.

    Saturday, June 29, 2013 11:53 PM
  • how are you even removing the network adapters? I keep trying to "uninstall" but nothing happens. it's still there. Also using an admin account.

    Sunday, June 30, 2013 1:13 AM
  • Once I reinstalled I had two adapters for Cisco.  One was enabled, the other was disabled.  I was able to uninstall the disabled one.

    I gave up and went back to Windows 8 on my Surface Pro.  Everything is working fine now.  I wish I would have looked this up BEFORE I went to 8.1.

    I restored from USB drive.  By the way, if you are planning to do that, make sure you take out your micro SD card first if you have one.  The restore would not work until I took it out.  Also, to restore from USB drive, turn off the computer, take out your micro SD if you have one, plug in you USB restore drive, hold down the volume down button, turn on the computer, follow the prompts. 

    Sunday, June 30, 2013 3:18 AM
  • I have done the exact same with the same results.
    Sunday, June 30, 2013 7:09 PM
  • I have achieved some consistency with the cisco vpn client version 5.0.07.0440 (x64) under Windows 8.1 by doing the following:

    1.  Navigate to the Cisco folder in Program Files and set Windows 7 compatibility for cvpnd.exe and vpngui.exe

    2.  Make sure that the Cisco VPN Adapter in Network Connections is disabled.

    3.  Reboot

    4.  Launch the Cisco VPN application from Program Files vpngui.exe

    5.  Success, VPN working as normal

    After a disconnect I have not been able to successfully connect again until I repeat steps 2 - 4

    Hope this helps everyone until we get an official fix.

    Tuesday, July 02, 2013 3:34 AM
  • Cisco Anyconnect Mobility VPN Client != Cisco VPN Client

    wanted to point out that these two client are completely different.

    Tuesday, July 02, 2013 9:14 PM
  • Teknarus' solution was the fix for me. Already had applied the registry fix in 8.0.

    Thank you!


    • Edited by nVinyl Wednesday, July 03, 2013 9:18 AM Adding username
    Wednesday, July 03, 2013 9:18 AM
  • This worked for me (AnyConnect Secure Mobility Client Version 3.101065)
    Thursday, July 04, 2013 6:49 PM
  • Teknarus's Solution also worked for me, albeit I too have to repeat steps 2-4 to achieve the desired state the adapter has to be in to actually connect to my company's VPN.
    Saturday, July 06, 2013 12:09 AM
  • I too am having a similar issue.

    Installing the Windows 8.1 Consumer Preview overwrote my network connections (along with my graphics card drivers). I figured a re-install of the Cisco IPSec VPN client would resolve the issue. 

    Instead, upon re-installing the Client, BOTH of my network adapters were really, really broken. Despite having a wired connection, my Local Area Connection wasn't showing up, along with the VPN adapter. The only connection I had was a Bluetooth connection.

    So, sometimes when your connection to the nearest hop is broken, the adapter will lease you a 169.254.x.x address. Not my PC. I get no lease. I cannot ping. I cannot tracert. No DNS, DHCP, TCPIP. Meanwhile, 'diagnosing' the issue using Windows' built-in tool identifies the issue as the NIC not being able to get a DHCP lease, but fails immediately and cannot rectify the issue.

    My only solution to getting a working network connection is to uninstall the Cisco VPN Client. I'm posting here because this is the first Google hit for "Windows 8.1 Cisco VPN client issues", and I'm clearly not the only person having an issue.

    If anyone has any ideas, they are much appreciated.

    CHECK THAT http://social.technet.microsoft.com/Forums/windows/en-US/90990c4c-52bc-4070-a212-6b8ff7e44bf7/cisco-vpn-no-longer-working-since-upgrade-to-81


    Gustavo

    Monday, July 08, 2013 2:07 AM
  • Check both links to have the solution

    http://social.technet.microsoft.com/Forums/windows/en-US/90990c4c-52bc-4070-a212-6b8ff7e44bf7/cisco-vpn-no-longer-working-since-upgrade-to-81

    http://answers.microsoft.com/pt-br/windows/forum/windows8_1_pr-networking/cisco-vpn-client-no-windows-81-preview-%C3%A9/c69424d3-98e0-42b4-b12f-f708449d944c


    Gustavo

    Monday, July 08, 2013 2:08 AM
  • This resolved it for me:

    Go to control panel > Device Manager > Network Adapters > Cisco AnyConnect......

    There were 2 adapters with the same name "Cisco AnyConnect Secure Mobility Client...."

    Removed one. If the other one is disabled, enable it.

    Try to connect and see if it works.


    Everything else didn't work - but this solution worked immediately for me!  Thanks!!
    Wednesday, July 10, 2013 10:22 AM
  • This one worked for me..

    Thanx!!! Cheers!!!

    Monday, July 15, 2013 8:38 AM
  • I had the same issue. I'd have to reboot every time the computer went to sleep because the network would stop working. Uninstalling, installing a new version of the deterministic network enhancer from the Citrix website and reinstalling the Cisco VPN worked (note not Cisco AnyConnect). Details are here,

    http://social.technet.microsoft.com/Forums/windows/en-US/ad556ff3-8d33-453e-8b16-71e36e23e2c6/cisco-vpn-client-and-windows-81-preview-determinist-network-enhancer-dilema

    Saturday, July 20, 2013 5:13 AM
  • I'm also facing the problem that my Cisco VPN Client isn't working anymore after
    upgrading Windows 8 Enterprise to Windows 8 Enterprise 8.1. Things I've tried so
    far:
    - Uninstalled Cisco VPN Client 64bit v5.0.07.0440-k9
    - Install Cisco VPN Client 64bit v5.0.07.0440-k9, but is failes during driver
    installation and device Manager is still showing two adapters, Cisco VPN Client
    Adapter 64bit and Cisco VPN Client Adapter 64bit Domestic Enhancer.

    - Manual driver removal using Device Manager is not possible
    - Removed the drivers using registry editor (using system privileges)
    - Install Cisco VPN Client 64bit v5.0.07.0440-k9, but fails at the same point
    mentioned above.

    Alternatively I've tried Screwsoft VPN, but this client install also fails during
    driver installation.
    At this time I’m trying to debug the installation process, hopefully it will lead to an
    answer.

    Wednesday, August 14, 2013 8:49 AM
  • Worked great on my fresh Windows 8.1 install.

    Monday, September 09, 2013 7:50 PM
  • I had the same problems after upgrading from Windows 8 tom 8.1.

    After Upgrade i was not able to establish an PPTP VPN connection.

    Also i had problems with my Cisco VPN Client. I could connect but i was not able to make a ping or anything else.

    So i uninstalled the Cisco vpn client and i also uninstalled all network adapters.

    After rebooting Windows my networkadapter came back.I installed the Cisco client again and all worked.

    Regards

    Michael

    Monday, October 07, 2013 9:45 AM