When you spend most of your time doing remote sessions into client environments using the Cisco VPN Client, I found it a bit troubling to find out that
Cisco announced their VPN Client End of Life. However, since I had the installation on a supported Windows 7 box, I was not too worried that Windows 8 would not be supported. Fast forward to August 8, 2012: my laptop died, all I had was a Windows 8 tablet to use as my defunct work computer, and I was no longer able to get to my clients...
To resolve this issue:
1) Open up the Registry Editor:
\HKLM\SYSTEM\CurrentControlSet\Services\vpnva\DisplayName
2) Edit the DisplayName, and clean out all of the junk (including the semi-colon) before the adapter name, leaving just the display name. For example:
"
@oem10.inf,%vpnva_Desc%;Cisco AnyConnect VPN Virtual Miniport Adapter for Windows x64"
becomes:
"Cisco AnyConnect VPN Virtual Miniport Adapter for Windows x64"
I'd definitely say it's worth researching a bit into the various private network solutions that are currently available on the market. A couple of affordable options that I've found recently are; 1) Hushtunnel 2) <a href="http://fireunblocker.info”>vpnreactor-review</a>
ReplyDeleteit worked with registry hack until this morning (latest Windows updates). No way to have it up&running again. I solved with www.shrew.net with Stable release 2.1.7 wich is a free VPN client with ability to import Cisco VPN .pcf profiles files. It works well (till now) without any trouble. I'm waiting news from Cisco support but I have no time to stay "disconnected".
ReplyDeleteRed.
Thanks for solution.Nice job.
ReplyDeletetop10-bestvpn.com
Thanks for good manual.
ReplyDeleteThis solution works good on Win8.
Nice VPN client for Win8.
10webhostingservice
Thanks for the post and great tips..even I also think that hard work is the most important aspect of getting success..
ReplyDeletehide my ass vpn service