Solution to Reason 442: Failed to Enable Virtual Adapter with Cisco VPN Client on Vista x86

<< Using UK English Dictionary in Windows Live Mail Desktop | Home | Sky+ for single LNB Households >>

Jan 09 2008

Solution to Reason 442: Failed to Enable Virtual Adapter with Cisco VPN Client on Vista x86

Wednesday, January 09, 2008 12:37 AM

UPDATED July 2008 : Please see below for updated solution to this problem

Again and again I see people complain about this error message (e.g. CISCO VPN Client Software on Windows Vista)

This is actually a quite easy (but annoying) thing to fix. Here's the 100% reliable method I use to fix this.

In Network Connections, right-click your Cisco Systems VPN Adapter which should be disabled and enable it
Right-click your Cisco Systems VPN Adapter again, this time selecting "Diagnose", and you should get the following prompt (your adapter may be numbered different from Local Area Connection 3)
Select "Reset the network adapter ........ ", this will take a while (around 60 seconds on my laptop)
Windows will again prompt you saying the IP configuration is still invalid, ignore this and just press Cancel.
Go back to the Network Connections, right-click your VPN Virtual Adapter and Disable.
Now open Cisco VPN, and you should be able to connect without any issues.

The problem will reoccur every time the connection is not cleanly closed - i.e. suspend / hibernate / loss of signal. However all you need to do is follow the above steps and it'll reset itself.

Update: This problem has been fixed in Cisco VPN Client 5.0.03.0530. Please speak to your Cisco supplier to obtain this new version. When disconnecting from a VPN connection it appears the new client performs these actions for you automatically (it takes around 60 - 90 seconds now to disconnect from the VPN session). I am unable to redistribute the client from this site - please speak to your Cisco supplier / IT Team.

Comments on this entry:

Pavel Petrek at 1/15/2008 2:25 PM wrote:

Thanks. Workes perfectly.
stanley at 1/16/2008 2:37 PM wrote:

Thanks a lot! I tried it (only 1 time so far) and it worked! You don't know how much frustration this has caused me (and lost time).
Boopathi at 1/20/2008 3:50 PM wrote:

Failed to Enable Virtual Network
M at 1/23/2008 6:44 AM wrote:

Thanks.
Joeri Scholtens at 1/23/2008 5:13 PM wrote:

Hmm, it doesn't work. I get the same prompt, but rather than 'local network connection ... does not have a valid IP address' it states that the computer has limited or now connection (while actually their is no connection problem at all). Any idea how to fix this?
Thanks a lot!
Margaret at 1/24/2008 12:50 PM wrote:

Worked like a charm - thank you!
Martin Noordzij at 1/25/2008 7:58 PM wrote:

Thanks a lot. It worked immediately.
krishna at 1/30/2008 3:49 AM wrote:

i too experienced the same,

it doesn't work. I get the same prompt, but rather than 'local network connection ... does not have a valid IP address' it states that the computer has limited or now connection (while actually their is no connection problem at all). Any idea how to fix this?

any alternative to try for fixing this issue?

thanks a lot!
Leanne at 1/31/2008 8:45 PM wrote:

I got the same message as above does not have a valid IP address' it states that the computer has limited or now connection

Any ideas?
Thao at 2/5/2008 8:35 AM wrote:

Same here. I tried a number of times but didn't work. Any other suggestion will be appreciated?
Thanks,
Thao
Casper Bang at 2/6/2008 9:23 PM wrote:

I still get "Failed to Enable Virtual Network" :(
SM at 2/7/2008 10:41 AM wrote:

using cisco vnp 5.0.02.090
vista business
tried the tip
thanks, but it did not work
almost giving up cisco vpn on vista...
any other option to replace cisco vpn client... how can they be so incompetent - one of the leading companies in the sector, cannot create a simple vpn client that works!?
Navin Mohanta at 2/11/2008 12:33 AM wrote:

This is how you can get rid of this.

1. Launch the Task Manager. Go to Processes tab and select "Show processes from all users".
2. Locate cvpnd.exe and try the reseting of the Network Adapter associated with it.
3. If that doesn't fixes, then once again kill cvpnd.exe and try installing the client software once again in the same location.

Hope that helps.

Thanks,
Navin
Des Harrold at 2/15/2008 8:11 PM wrote:

The solution using "Reset the network adapter..." did not work.

This error first appeared on my system 2 days ago immediately after the last set of Vista updates. The VPN connection had been working perfectly for months up to that. I am going to back out all the updates to isolate the one that causes the problem.

I will let you know.
Des Harrold at 2/15/2008 9:28 PM wrote:

My problem is definitely caused by one of the updates - I had to use system restore to the day before to get the VPN to work.

There are 18 updates so it will take a while to figure out which one causes the problem.
Des Harrold at 2/16/2008 12:49 AM wrote:

My problem is solved - it appears to be the accumulation of updates. When I run them individually I don't now have the error. The VPN is connecting normally.
Milind at 4/4/2008 2:32 PM wrote:

The original solution worked for me only for a week or so.. Then I started getting the "limited connectivity" error message instead of "no IP address" message and it stopped working.
I have found a solution that may be useful to others.

I have marked the programs VPNGUI.exe and CVPND.exe to "Run as administrator" and to run in "compatibility mode for Windows XP". I have used both these settings and once it worked, not bothered to determine which one fixes the problem or whether both the settings are necessary.

Now, whenever I reboot my PC, I get a prompt about whether to allow VPNGUI to run (since it is marked to run as administrator). But the 442 error is gone!

Cheers..
CS Shyam Sundar at 4/11/2008 6:51 AM wrote:

Im using Windows Server 2008 as my primary Workstation OS!

I experience the same issue. Solution is both comment 21 [ change vpngui and cvpnd to be compatible with XP SP2 and works like a charm ]
tayyab at 5/4/2008 3:20 PM wrote:

Thx dear, works great from me :P
phlavius at 5/13/2008 8:08 PM wrote:

livesaver!!
vozuze at 5/16/2008 7:10 AM wrote:

Thx , you save me
Darryl at 5/22/2008 5:08 PM wrote:

Yes, resetting the connection didn't work for me either. This is on Vista Business.

However suggestion in comment #21 of setting compatibility mode on the 2 exe's to XP SP2 DID WORK! So thanks very much to Milind!
karthik at 5/23/2008 8:10 PM wrote:

Thank you it worked.
Dave at 5/29/2008 4:55 AM wrote:

Worked great. Thanks for taking the time to put this together in a user friendly format!!
Thomas at 6/1/2008 10:24 AM wrote:

Didnt work for me - instead I went to Control Panel, chose Repair, and then it worked again.
Murat Kebabci at 6/5/2008 1:22 PM wrote:

Thanks for the info ^^ After last Vista updates i got this error constantly and i couldn't find a good solution myself, then found this, tried every solution here and they just didnt work :) Only after i reinstalled the software, resetting the network adapter solution worked, at last i must say..

PS: I still have no idea which update caused this problem, they were like 14-15 updates so with the time i lost now i have none to backtrack the problem :(
Linda at 6/8/2008 4:37 PM wrote:

This is not working for me... I have tryed all of the suggestions above; however I keep getting the Failed to Enable Virtual Adapter error.
Satish at 6/9/2008 7:23 PM wrote:

Thanks man....this works great!
Danny at 6/10/2008 6:02 PM wrote:

This method did not work.
Dez at 6/11/2008 4:30 PM wrote:

Thanks for the advice. I tried the first solution but it never worked, I got the low network connectivity message. I tried the compatibility method but that also failed. I then uninstalled the windows updates that I installed today and after rebooting, the client worked again. I suspect that the update that caused the client to stop working is KB950759 which is a security update for IE7 in vista although I am yet to try re-installing them.
Bradg at 6/17/2008 2:22 PM wrote:

Great, works on Server 2008 also.
Chris at 6/24/2008 11:23 AM wrote:

still getting the issue here
vinhboy at 6/26/2008 4:38 AM wrote:

If it does not work the first time, keep doing it. Sometimes I have to enable/disable my VPN adapter several times before I can connect. Hopefully there will be a real fix for this soon.
Nice post!! at 7/1/2008 1:09 PM wrote:

Thanks, it's work #1 for me..
Jaykar at 7/2/2008 12:51 PM wrote:

I tried. Still not working . I continue to seek help desperately
David at 7/2/2008 10:57 PM wrote:

Duplicate IP Address Triggers Error 442 on Windows Vista

The following error "Reason 442: failed to enable virtual adapter" appears after Vista reports a duplicate IP address detected. Subsequent connections fail with same message, but Vista doesn't report a duplicate IP address detected

To work around error 442, do the following steps:

Step 1 Open "Network and Sharing Center".

Step 2 Select "Manage Network Connections".

Step 3 Enable the Virtual Adapter ("VA"—Cisco VPN Adapter).

Step 4 Right-click on Cisco VPN Adapter and select "Diagnose" from the context menu.

Step 5 Select "Reset the network adapter Local Area Connection X".

If this procedure does not work, run the following command from cmd:

reg add HLKM\System\CurrentControlSet\Services\Tcpip\Parameters /v ArpRetryCount /t REGDWORD /d 0 /f

Then reboot.

This resolves the issue until Vista reports a duplicate IP address again. Follow the preceding steps to resolve it again.

If that doesn't work, run the following from cmd.

Note If you have UAC enabled, you must run cmd as administrator:

reg add HKLM\System\CurrentControlSet\Services\Tcpip\Parameters /v ArpRetryCount /t REG_DWORD /d 0 /f

(CSCsi26106)
Cheesmanr at 7/10/2008 8:06 AM wrote:

I still get "Failed to Enable Virtual Network"
Kdub at 7/10/2008 2:55 PM wrote:

Entering reg add HKLM\System\CurrentControlSet\Services\Tcpip\Parameters /v ArpRetryCount /t REG_DWORD /d 0 /f
worked for a couple of days, then the error came back. So I used reg add HKLM\System\CurrentControlSet\Services\Tcpip\Parameters /v ArpRetryCount /t REG_DWORD /d 0 /f (CSCsi26106) and that worked for a couple of days. Now nothing works this is getting stupid....any ideas?
cjatfenway at 7/14/2008 5:30 PM wrote:

This is driving me insane. I tried the approach that the original article suggested and it did work, once. After 10-15 minutes it disconnected me from the VPN again. Then I tried it again and it hasn't worked. I then also tried to set the compatibility of the vpngui.exe and cvpnd.exe to Windows XP SP2 and that also hasn't worked.

This error is driving me insane as the only solution that has consistently worked for me is rebooting, but that's not going to work for me, especially when there are hard deadlines and/or I'm in front of clients. :(

For the record I'm running Vista Business. This was never a problem on my previous machine, running XP.
Smith at 7/16/2008 8:34 PM wrote:

That was all it took. Thanks for the fix.
Martin at 7/23/2008 5:15 PM wrote:

Yes! Worked like a charm - thank you!
Laurent at 7/24/2008 6:11 PM wrote:

Use the windows built-in VPN. it will ask for your credentials and stuff, but will tell you it could not conenct. select the "setup conenction anyway". once created, right click on the VPN connection, click properties and in the security tab, select advanced, then settings then select "allow these protocols" and slect all of them except "automatically use my windows logon..." click ok, then yes. then try to connect again and it should work. it worked like a champ for me. hopefully it will work for you now. cisco s*#ks
Yuri at 7/25/2008 2:47 PM wrote:

Running the following line in CMD window (As administrator) fixed the problem:

reg add HKLM\System\CurrentControlSet\Services\Tcpip\Parameters /v ArpRetryCount /t REG_DWORD /d 0 /f

VPN started working correctly after reboot (all other methods didn't work).
Edmund at 7/30/2008 6:54 PM wrote:

This steps works perfectly.
Thanks!
John at 8/1/2008 10:00 PM wrote:

I was getting errors and found that if I disabled some of the IPv6 stuff in the System Device Manager of Vista - it improved significantly. Note that you have to show hidden devices to see the teredo tunneling drivers.
Jamal at 8/15/2008 2:06 PM wrote:

What I did to get it to work is to just go to the cisco adapter and Enable it. Then try the Cisco VPN connection. Ours started up fine.

It seems that our client saw the adapter get disabled and then re-enabled in seconds. Try this and let me know how it goes.
Aaron at 8/18/2008 7:44 PM wrote:

Well, I just installed 5.0.03.0560 and it has the same problem...
DS-76 at 8/24/2008 10:43 AM wrote:

Worked amazing saved me a whole day working from home thanks.
Arash Ghavami at 8/26/2008 4:32 AM wrote:

I confirm Aron's comment. I have the same version (5.0.03.056) running on Vista and still the same problem. Your solution/work around is still valid though. Thanks for sharing it.
tustush at 8/31/2008 6:48 PM wrote:

all the above did NOT work for me

Solution (quite simple):

Services -> Internet Connection Sharing Service

Just stop it... de-selecting ICS on all connection did not work for me
gh kh at 9/17/2008 1:11 PM wrote:

doesnt work...
bd at 9/17/2008 4:51 PM wrote:

this solution did not work for me either. I finally got mine back after disconnecting from wireless connection and rebooting.
Jamie Rabenstein at 9/22/2008 8:43 PM wrote:

Did the "stop ICS in servies" and all is well. Thanks a ton!!!:)
meri at 9/22/2008 9:26 PM wrote:

Vista Home Premium - after installing Vista sp1, Cisco VPN has broken. Tried the solutions above, and the last thing I tried (which worked, indeed) was setting the compatibility mode (XP sp2) for the 2 exes. Before that, I even injected the mentioned registry key, which might have been also needed.

Thanks folks!
Paul at 9/26/2008 2:44 PM wrote:

This didn't work for me. I did hit upon something that did work though. I logged in as a Real Administrator in Vista and then I installed the Cisco VPN client. Now I can connect just fine EVERY TIME...man, this problem was a real PIA.
Ryan at 9/29/2008 5:48 AM wrote:

I have the same problem. Still cannot get connected.
M Donahue at 10/2/2008 7:38 PM wrote:

stopping ICS worked for me, but I want to know what that did on my computer and what potential changes it can cause on my computer?

Meghan
Oscar at 10/8/2008 1:39 AM wrote:

Running the following line in CMD window (As administrator) fixed the problem:

reg add HKLM\System\CurrentControlSet\Services\Tcpip\Parameters /v ArpRetryCount /t REG_DWORD /d 0 /f

Thanks Yuri... this worked for me on the 5.0.02.0090 Vista Business O/S
chrisbzd at 10/9/2008 1:31 AM wrote:

Resetting the connection didn't work for me. I'm using Vista Business. Simply stopping and starting the "Cisco Systems Inc." service worked for me.
Sarath at 10/9/2008 1:34 PM wrote:

Hi,

I tried this fix for this issue when this one was really pissing me off.

The VPN client provided by my company was and earlier version 5.0.00.0300. It was not possible to update it and also the settings (Profiles and Certificates) was automatically loaded whenever I install the VPN executable provide by my company.

So I installed with my company installer and made a copy of C:\Program Files\Cisco Systems\VPN Client\Profiles\
and C:\Program Files\Cisco Systems\VPN Client\Certificates

Then I downloaded the latest VPN client 5.0.04.0300 and installed it.
Then I copied the above directories into C:\Program Files\Cisco Systems\VPN Client\ and now it is working really good.

Hope this helps someone who has similar issue.
Sarath at 10/9/2008 1:38 PM wrote:

u can try downloading the VPN client using the torrents illegally
Kristoffer at 10/16/2008 8:26 AM wrote:

Worked like a charm, but remember to have patience, it might not connect on first try, but on second.
Joao Costa at 10/22/2008 6:27 PM wrote:

I have version 0560 and it goes on happening! I used to use the shortcut you indicate, it worked better in the previous version!
thanks for the help!
Rodah at 10/24/2008 8:48 AM wrote:

Stopping ICS worked for me. Thanks!! Problem is, I share the Cisco VPN Adapter for my VM computers.
scott at 11/18/2008 3:09 AM wrote:

awesome...thanks for saving me time!
Vijay at 11/20/2008 8:43 PM wrote:

Thank you so much... You have no idea how much trouble you have saved me... :)
Jez at 11/23/2008 10:10 AM wrote:

Brilliant.. This work around is working for me and Saved me so much pain
jiji at 12/1/2008 2:52 PM wrote:

I solved this problem by unchecking the sharing network connection setting.
gary_the_it_pro at 12/3/2008 4:39 AM wrote:

Reason 442 Error Fixed

Cisco VPN Client 5.0.04.0300
32-bit Vista Business SP1

Disabled IPV6 for Cisco VPN Network Adapter.
Clayton at 12/4/2008 8:20 PM wrote:

Fixed the problem after trying most of the solutions provided... :)

With me it was the Windows Security updates. I removed all of them... about 20 something, rebooted and the problem was solved. What a DAM mission.

Maybe its a good idea to take all the above solutions and put them together in point form.

PS.. Dont ask which update worked. I just smoked them all :)

hahahah
Pat Bailey at 12/5/2008 11:14 PM wrote:

SOLUTION!!

First enable the Cisco Vpn Adapter in Network Connections

Then right click and repair

You should get an error saying that TCP/IP is not enabled

Then right click-> Properties
UN-check TCP/IP and the click ok

Then right click again -> properties
and RE-check properties

right click Cisco VPN Adapter and repair again, it will fail

right click Cisco VPN Adapter and disable

goto START->RUN: type in services.msc

find Cisco System, Inc. VPN Services and right click ->restart (or start if it is not running)

This should fix your issue
It seems as though the binding of TCP/IP to the Cisco VPN Adapter gets corrupted

Thanks,

Pat B
Michael at 12/9/2008 11:12 PM wrote:

I tried the solution described above several times and still have the same issue. Are there setting on the vpn adapter than need to be set under different configurations? For example, I have a home server and have tired several options for "sharing" connections with the host computer that also do not seem to work. I think I am selecting the wrong options for the adapters??
b doggy at 12/10/2008 4:35 AM wrote:

yeah, i used this trick for about 4 months and it worked great. i was so happy and i loved you for it. now it doesn't work anymore but i still love you. i do however hate vista and cisco. there are so many compatability issues!!! or we have a lousy comp tech dept at work.
Joseph Poirier at 12/11/2008 5:26 PM wrote:

The solution described in the Comments section posted by "Pat Bailey" on 12/5/2008 11:14 PM worked for me. BTW, I am running Windows XP Service Pack 3. Thanks!!!
Sunil at 12/13/2008 4:32 AM wrote:

I still cannot get it to work. I have internet connectivity but the VPN adapter thinks the computer only has limited or no connectivity. I've tried reset etc and nothing works. I am using vista ultimate. However, it works fine on vista home premium where the setup is the same as the vista ultimate.
Ram at 12/16/2008 1:16 AM wrote:

I have tried all the fix that was give but still I am geting the error. Can you please advice
kiran patel at 12/19/2008 1:06 AM wrote:

Thanks It worked but remember everybody if you have checked allow others to connect in properties' sharing tab then first uncheck it then try the above solution.
Paul at 12/19/2008 6:09 AM wrote:

Yes, Great this works!
Maria at 12/30/2008 6:11 PM wrote:

Thanks a lot!
Yaroslav at 1/5/2009 11:18 AM wrote:

Tried everything, this problem is making me scream! after lot of tries and failures, disconnecting ICS, restarting and executing as administrator worked for me... let's see if still works the next 2 days...thanks a lot
RK at 1/9/2009 12:58 AM wrote:

I made the cvpnd.exe and vpngui.exe compatible to Win XP SP2. By default, the network connection for Cisco VPN is disabled. The VPN client tried to enable it when you try to connect. Instead, have this network connection enabled before you try to connect using the VPN client. This made it work for me... at least for the time being :)
Jonathan Beauchamp at 1/12/2009 7:15 PM wrote:

I tried the above steps and I still had the same problem as before, with the same error message (Reason 442, etc). This is getting quite frustrating and is costing me way too much time. Please tell me if there are other ways to solve this problem. Thanks.
Ben Dover at 1/12/2009 7:44 PM wrote:

win2k8, followed the above steps. didnt work. tried settings compatibility XP, didnt work. tryed the above steps again. worked! :)
William at 1/13/2009 7:45 PM wrote:

I am aged, dumb with computers, abroad where nobody can help me, badly needing to connect with my University ... and none of the solutions have helped! (I run Windows XP SP3). This is becase:1.The Cisco solution, because when I right click trhere is no "diagnose" window; 2. Same for David's; 3. I tried Pat's and nothing; 4. I went to "services" " and didn't see ICS; 5. And to "proceses" and found cvpnd, but don't know how to reset the network adapter (no command in sight); and 6. the advice to run CMD and Reg I don't have the faitest idea how to do it. So PLEASE help! Thanks in advance.
William at 1/14/2009 4:38 PM wrote:

Hello again: I found in Services he ACN and stopped; it didn't work. I found through system files/hidden files the device manager IPv6 and it is not there.
Any advice please?
William at 1/15/2009 2:06 PM wrote:

Somebody can help me? Please see the two messages above. Thanks so much in advance to a good and knowledgeable soul!
J-Marc at 1/16/2009 12:13 AM wrote:

Great ! I was in a little bit different situation : connecting perfectly well (as the 5.0.03.0090 client said), but no ping no connection at all (Vista 32b). It worked ver very well for days before, no new installation or anything changed.

This repair operation did the job !

THANK YOU SO MUCH !
cpalmer9 at 1/17/2009 12:39 AM wrote:

I had the same problem on ver 5.0.02.0090 (on Vista 32bit), however no workaround worked for me.
I removed the client and installed ver 5.0.04.0300 and the problem appears to have gone away.
freeman at 1/25/2009 4:48 AM wrote:

It'work like this solution :
- enable the Cisco Vpn Adapter in Network Connections
- right click -> Properties
- click Internet Protocol Version 4
- click Properties
- check "Obtain an IP address automaticaly"
- click OK

Enjoy.
cranky at 1/30/2009 9:47 PM wrote:

How is this a solution...it appears to be a workaround...The question remains: why do vista users still get 442 messages and when connection occurs it seems random?
John L at 2/20/2009 3:32 AM wrote:

It worked. Thanks.
dan at 2/21/2009 2:11 AM wrote:

Worked great for me! Thank you!
Omar at 2/24/2009 1:58 PM wrote:

it works, Verier for President
Mat at 2/26/2009 12:11 AM wrote:

yes Thank so much
Scott at 3/1/2009 4:05 PM wrote:

Worked great. Thanks so much. I have Vista Ultimate 32 bit.
Frank at 3/9/2009 3:11 PM wrote:

I had my connection working for many months (Vista business) and suddenly I have this problem too. Tried everything, including with the ver 5.0.04.0300 and still not working.
Jan at 3/11/2009 8:43 AM wrote:

No 96: The same happend to me. The solution did not work for me
Scott at 3/13/2009 10:28 PM wrote:

Stopping the ICS service is all it takes.
miss jones at 3/20/2009 2:22 PM wrote:

perfect solution. Thnx a lot
Paul Charette at 3/26/2009 10:24 AM wrote:

Hi all, I'm using Client Version 5.0.04.0300 on Vista 32bits with all the updates. I read through the entire post, tried everything , such as obtaining IP address automatically, repairing the interface, etc. The only thing that (finally) worked for me is disabling the ICS (Internet Connection Sharing) service: start the ICS service, get the "Failed to enable virtual adapter" error - stop the ICS service, the Cisco Client connects and everything's cool. Thanks so much for the solution.

Paul.
Bobby at 3/31/2009 9:57 PM wrote:

Worked like a charm. Thank you so much for posting this resolution.
Rob Staveley at 4/6/2009 9:34 AM wrote:

Worked nicely. I'll try to get a new version of the client though to avoid this in future.
Venkat Reddy at 4/8/2009 3:30 AM wrote:

It works fine.

Thanks a lot.
Robson at 4/16/2009 10:05 PM wrote:

Cisco 5.0.00.0340 on Vista Business. I've got this problem (442) if I've turned on both WiFi and LAN connection. After turning off LAN (working on WiFi) problem disapired.
scott at 4/20/2009 10:47 PM wrote:

Running as admin and in compatibility mode works!
Vista ultimate

TY
cengiz at 4/23/2009 1:03 PM wrote:

freemans solution worked for me...
Thank you freeman
freeman at 1/25/2009 4:48 AM wrote:

It'work like this solution :
- enable the Cisco Vpn Adapter in Network Connections
- right click -> Properties
- click Internet Protocol Version 4
- click Properties
- check "Obtain an IP address automaticaly"
- click OK

Enjoy.
Lada at 5/8/2009 2:57 PM wrote:

It doesnt work. My problem is that the first attempt to connect fails and the second one (and the next ones) is successful. After reset my computer the problem is here again. Generally speaking, I always have to carry out two attemps to connect. Do anybody else have the same experience?
ignas81 at 5/10/2009 11:57 AM wrote:

Thanks man - this helped a lot...
Chris Newell at 5/11/2009 11:14 AM wrote:

I've the same issue as you Lada running 0560 build.
Pungitight at 5/11/2009 7:27 PM wrote:

Thanks! It worked. I was pretty skeptical in the beginning 'cos most such solutions don't work - but this one actually did. So I had to post a note. :)
Claudio Oliveira at 5/21/2009 1:07 PM wrote:

Thanks man!! Works fine!!
HO at 5/26/2009 7:34 PM wrote:

...this really helped... Since 3 years using Cisco VPN I had nothing but problems... really rotten software!
David Kossoglyad at 5/27/2009 9:51 AM wrote:

Unfortunately, it doesn't work. I have tried all the options including to install the new version. It's seems strange! It was always good. I got this really randomly in past and last weak I don't able to connect absolutely. Can anyone help me please?
Matt at 5/27/2009 11:02 AM wrote:

It really is ridiculous that this problem still comes up. Thanks for the help (disabling ICS worked for me).
Borisov at 6/4/2009 9:09 PM wrote:

Stopping ICS is a solution for me, VPN Client 5.0.01.0600
Juan at 6/10/2009 12:14 AM wrote:

Thanks a lot!
Restarting the ICS service worked for me too!
I have Vista with VPN Client 5.0.00.0090
Shanmuga at 6/15/2009 6:35 AM wrote:

This error may occur even if you allow other network users to connect through this computer’s network connection. Refer the following link for further information.
http://www.john.bryntze.net/jbkb/index.php?title=Vista-kb18_Cisco_VPN_%22Reason_442:_Failed_to_enable_Virtual_Adapter%22
John at 6/25/2009 2:42 PM wrote:

Well done and clear. This saved my butt big time. Thanks.
JJ at 7/2/2009 10:25 AM wrote:

Nothing is working for me I have windows xp sp 3
Fahd Ajmal at 7/2/2009 9:07 PM wrote:

none of the above works for me...
rebooting the PC is the only solution so far... i'm using Cisco VPN Client version 5.0.05.0280 on Vista ultimate...
JJ at 7/3/2009 7:40 PM wrote:

It is just so weird, the only thing I did was moving to a new place.