I found this while trying to get a Cisco ASA vpn tunnel up. For some reason the secure mobility anyconnect tunnel would not encapsulate dns or dhcp traffic. This prevented me from being able to access my domain. I figured I’d give the 64-bit legacy client a try and after the fix below, it worked fine. Here is what you need to do after you install the legacy client to get it to work.
Reposted from: http://social.msdn.microsoft.com/Forums/en-US/windowsdeveloperpreviewgeneral/thread/6fe817f3-27fe-4068-995a-aced4508ee3e/
Hi Everyone,
Just to update, the legacy Cisco VPN client (5.0.07.0440 for x64, 5.0.07.0410 for x86) is working for some people. You need to apply a small workaround as explained below –
· Open Registry editor by typingregedit in Run prompt
· Browse to the Registry Key HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Services\\CVirtA
· Select the DisplayName to modify, and remove the leading characters from the value data upto “%;” i.e.
o For x86, change the value data from something like “@oem8.inf,%CVirtA_Desc%;Cisco Systems VPN Adapter” to “Cisco Systems VPN Adapter”
o For x64, change the value data from something like “@oem8.inf,%CVirtA_Desc%;Cisco Systems VPN Adapter for 64-bit Windows” to “Cisco Systems VPN Adapter for 64-bit Windows”
· Try connecting again
Please do revert back if this solution does not work.
Regards,
Raman
- Edited by Raman-MSFT Tuesday, December 13, 2011 1:30 PM
- Proposed As Answer by Kamil Gozdek Tuesday, December 13, 2011 10:52 PM
- Marked As Answer by Marilyn-Support EngineerMicrosoft Support, Moderator Wednesday, December 14, 2011 12:51 AM
