Fixing Cisco's VPN Client Error on Windows 8

Today, working on my Windows 8 machine, I found that Cisco's VPN client was giving me "Error:442" and was unable to connect to VPN. After trying a lot and searching on web, I found the solution to the problem. Here are the steps mentioned below to get it working.

Step 1:-
Goto Run by pressing "Windows + R" and type "regedit". It will open the registry editor.

Step 2:-
Navigate to the following key: "HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Services\\CVirtA"

Step 3:-
Here you will find that "DisplayName" key has some garbage value followed by VPN client name. You need to modify it.

Select the DisplayName to modify, and remove the leading characters from the value data upto "%;" i.e.

• For x86, change the value data from something like "@oem8.inf,%CVirtA_Desc%;Cisco Systems VPN Adapter” to "Cisco Systems VPN Adapter”

• 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"  Once this is done, you will be able to connect to VPN using VPN Client.

Other Errors which might also lead to Error 442:-
If you have enabled "Internet Connection Sharing", even then you will find this error. For this, you need to open "services.msc", navigate to "Internet Connection Sharing" and disable it.

Some interesting facts about windows 8

To understand this article, you first need to know few things…..

First one is about UEFI(Unified Extensible Firmware Interface) which is nothing but the replacement to the traditional BIOS which has started to occur.

One can have a good knowledge about it from the following link…. It’s a good link to know about UEFI.

http://www.howtogeek.com/56958/htg-explains-how-uefi-will-replace-the-bios/

Important Point:-

One feature of UEFI is that it allows firmware to implement Security Policies.

Now why is this UEFI important???

UEFI secure boot is part of Windows 8 secured boot architecture

So, when windows 8 will be launched, the laptops which will be coming with pre-installed Windows 8 will have UEFI instead of traditional BIOS.

Here is a nice article about the boot process of win8:-

http://blogs.msdn.com/b/b8/archive/2011/09/22/protecting-the-pre-os-environment-with-uefi.aspx

So why to be concerned??

·          

      Windows 8 utilizes secure boot to ensure that the pre-OS environment is secure

·         Secure boot doesn’t “lock out” operating system loaders, but is a policy that allows firmware to validate authenticity of components

Usually if we have a laptop with windows installed on it and want to install Linux on it, then we simply either format or create new drive and install Linux onto that. And then it modifies the Boot Loader/System Loader and we get both the OS working.

But with PC’s having Windows 8 installed, if you have UEFI instead of BIOS, you won’t be able to do so. As it now uses UEFI and it has security policies configured which will prevent you from booting any other OS than the authorized ones.

Microsoft can require that hardware vendors include their keys (for secure booting). Their competition can't. A system that ships with Microsoft's signing keys and no others will be unable to perform secure boot of any operating system other than Microsoft's. No other vendor has the same position of power over the hardware vendors. Red Hat is unable to ensure that every OEM carries their signing key. Nor is Canonical. Nor is Nvidia, or AMD or any other PC component manufacturer. Microsoft's influence here is greater than even Intel's.

Linux has no support for UEFI by now and it would be an issue for linux to add support for it as soon as possible and also make vendors to add their certificates in the authorized list.

Here is a nice article on this topic:-

http://www.osnews.com/story/25185/Microsoft_Responds_to_Secure_Boot_Story_Doesn_t_Address_Issue