Everyone has dealed with Cisco VPN Client on Vista probably knows the notorious Error 442 – Failed to enable virtual adapter. AFAIK this is a bug from Cisco that stays unfixed for at least 5 months (from the version 5.0.00.0340 released on May 2007 until now). Whether it is Cisco or Microsoft to point the finger at, i really don’t know.
So … you probably already tried this work-around suggestion from Cisco’s release notes:
Run cmd as Administrator and execute the following command:
reg add HKLM\System\CurrentControlSet\Services\Tcpip\Parameters /v ArpRetryCount /t REG_DWORD /d 0 /f
It just does not work ( at least every time i faced Error 442 ). What you should do is:
- Remove the client
- Activate the real Administrator account ( for detailed howto see this post )
- Restart, then log into the administrator account
- Install the file as normal ( right-click on it, choose “Run as Administrator”)
- After the installation finishes, restart again.
The client should work now. If not try to remove the Deterministic Network Enhancer protocol first, then reinstall VPN. Have patience, you will need to restart your computer sometimes.
Some people say the removal of Microsoft SQL do the trick (strange, erh ?), or simply turn on Media Sharing in the Network and Sharing Center. I haven’t tried this, so if it fixes your problem, then good for you.
If you could post your result here, then i am very appreciated 
Users’ comments:
From Nathan Le:
Under Services, I disabled Internet Connection Sharing (ICS) and then reboot. It then worked like a charm. By the way, I am using Windows Vista and Cisco VPN Client version 5.0.03.0560. Hope this helps.
From Chkrata:
The fix for 442 is simple – just tick ‘Allow Local LAN Access’ on the Transport tab of connection properties.
From fakh:
Many reasons that can cause this error, for instance if you have mcafee installed make sure you removed the NDIS filter under network, adaptors, choose the cicso vpn go to properties and uncheck NDIS.
From Chris:
The problem exists with MS Network Monitor and Vista. However, simply uninstalling NetMon will not solve the problem. Before uninstalling NetMon, run “nmconfig /uninstall” from the directory the application is installed. Once this is done you can uninstall Network Monitor. Reboot your system and all is right in the world!
From Tim:
I had this same problem start out of nowhere. After coming to this site and seeing some of the fixes, all I did was open C:\Program Files\Cisco Systems\VPN Client, right clicked on ipsecdialer.exe and vpngui.exe and clicked properties. I set both to run in xpSP2 compatibility mode and run as administrator. Problem was immediately fixed, no reinstallation was necessary and no DNE update was necessary. But yes I have to agree to let it run each time I start it.
Update: Updating DNE solves the problem indeed (uninstall VPN, get the latest DNE driver at deterministicnetworks.com, install it and then install VPN again). Deterministic Networks was acquired by Citrix, it’s site is redirected to Citrix’s
Update: If you happen to use the latest version (5.0.04.0300, as of Nov 2nd 2008) and still have this 442 error, uninstall the client and use an older version e.g. 5.0.03.0560
Update: In case the problem is stubborn and doesn’t want to go away, there is Shrewsoft VPN Client, which is compatible with many types of VPN gateway, and especially, free. It helped me many times when the Cisco client refused to run.
Related posts:
Comments 50
The problem exists with MS Network Monitor and Vista. However, simply uninstalling NetMon will not solve the problem. Before uninstalling NetMon, run “nmconfig /uninstall” from the directory the application is installed. Once this is done you can uninstall Network Monitor. Reboot your system and all is right in the world!
Posted 16 Jan 2008 at 3:14 am ¶Thanks for post. It`s help me in job. Sorry for my bad english
Posted 21 Feb 2008 at 1:19 pm ¶Excellent solution! Make sure that you first completely uninstall from the Control Panel – then do a restart! before installing “as administrator” Do not skip the restart.
Posted 05 Apr 2008 at 8:11 pm ¶The link to the latest driver on deterministicnetworks.com has a message saying their products are retired from commerical sale. How can one get the latest driver?
Posted 25 Apr 2008 at 6:51 pm ¶There is a link to “DNE Support” at the top left corner:
http://www.deterministicnetworks.com/support/dnesupport.asp
Posted 27 Apr 2008 at 10:05 am ¶Thanks for the direction.
The following procedure worked perfectly for me.
-Uninstall VPN client.
-Restart
-Install DNE Update.
-Restart
-Log on as administrator
-Install VPN client (Right click “run as admin”)
-Restart
-Log in as standard user
-Open VPN client
-Open task manager
-Click “show process from all users”
-Set both cvpnd.exe and vpngui.exe for XP SP2 Compadibility mode, and check the “run as administrator” box
-Restart
You will have to clic the UAC prompt when starting windows, and when opening the client UI. But it finally works!!!!!
This working setup is on a Vista Enterprise SP1 and Cisco VPN Client v5.0.03.0530.
Hope it helps!
Posted 18 May 2008 at 5:02 pm ¶Thank you for the guide, Jomo.
Posted 20 May 2008 at 10:04 pm ¶I just want to add one quick not. If you still have issues after trying the above workarounds. Try installing ccleaner (free) to clean your registry. Also use it to make sure the VPN client doesn’t start along with windows.
I haven’t had a single problem since I used ccleaner. Hope this helps someone…
Posted 07 Jun 2008 at 1:26 am ¶I had this same problem start out of nowhere. After coming to this site and seeing some of the fixes, all I did was open C:\Program Files\Cisco Systems\VPN Client, right clicked on ipsecdialer.exe and vpngui.exe and clicked properties. I set both to run in xpSP2 compatibility mode and run as administrator. Problem was immediately fixed, no reinstallation was necessary and no DNE update was necessary. But yes I have to agree to let it run each time I start it.
Posted 21 Aug 2008 at 11:08 pm ¶Thanks for the ideas, I have an KB article with some other ideas how to solve this problem:
Posted 02 Sep 2008 at 8:46 pm ¶http://john.bryntze.net/jbkb/index.php?title=Vista-kb18_Cisco_VPN_%22Reason_442:_Failed_to_enable_Virtual_Adapter%22
I have try al the things but nothing helps. At least I try the solution of Tim (9) and now it works! I work with Vista. Thanks!
Posted 07 Sep 2008 at 2:31 pm ¶I found the answer. Log in as administrator, and remove and reinstall as administrator. On Vista you need to enbale adminintrator account. There is info on the web how to do that.
Posted 13 Sep 2008 at 11:20 pm ¶This fixed my problem — download and install the latest version of DNE then restart and open vpnclient. If it does not work reinstall the vpnclient.
http://www.deterministicnetworks.com/Downloads/dneupdate.asp
Posted 02 Oct 2008 at 9:31 pm ¶Thanks from Brazil.
Posted 12 Nov 2008 at 11:59 am ¶I’ve found s.th. which worked with me:
Posted 13 Nov 2008 at 10:34 am ¶http://forums.techarena.in/windows-vista-network/694666.htm
20-03-2007
rawel
Re: Cisco VPN Reason 442
Hey guys
The fix for 442 is simple – just tick ‘Allow Local LAN Access’ on the
Transport tab of connection properties.
Good luck!
–
rawel
I tried everything on here from updating Cisco VPN client to reinstalling DNE. Nothing worked. Finally, I found a solution.
Under Services, I disabled Internet Connection Sharing (ICS) and then reboot. It then worked like a charm. By the way, I am using Windows Vista and Cisco VPN Client version 5.0.03.0560. Hope this helps.
Nathan
Posted 29 Jan 2009 at 6:37 pm ¶Under Services, I disabled Internet Connection Sharing (ICS) and then rebooted, as Nathan said.
Worked perfectly and in a snap. I also have Vista and same version VPN. Thanks N!
Posted 05 Feb 2009 at 4:01 pm ¶Disable Internet Connection Sharing works well
Cisco VPN Client is a piece of crap… I’ll never buy cisco product!
Posted 10 Feb 2009 at 8:15 pm ¶OMG, I’ve been beating my head against the wall. Thank you Nathan (16) & Steve (17)! Disabling Internet Connection Sharing Service worked, didn’t have to reboot either, just worked instantly. Thank goodness, I usually just lurk, but I felt quite compelled to add something as I was about to pull out my hair.
Posted 16 Feb 2009 at 6:19 am ¶After updating to latest CISCO VPN and running determinaistic fix I still received 442 error. I noticed that my laptop had 2 LAN connections. LAN was a disconnected cable connetcion and LAN2 was CISCO VPN. Disabling LAN solved my 442 error problem.
Posted 16 Feb 2009 at 6:16 pm ¶Thanks for the help! Your post was the only one I found which actually helped me correct the problem. Thank you!
Posted 05 Mar 2009 at 2:30 am ¶Thank you Thank you Thank you.
I’ve been struglin with this problem for quite some time, found many different sites with may different ideas but non worked. Finaly i came here, followed your instructions and WOW.
If i knew where you where i would buy you a beer.
Posted 22 Apr 2009 at 5:24 am ¶Many reasons that can cause this error, for instance if you have mcafee installed make sure you removed the NDIS filter under network, adaptors, choose the cicso vpn go to properties and uncheck NDIS.
Posted 28 Apr 2009 at 11:43 am ¶Thanks fakh, that is interesting to know
Posted 01 May 2009 at 7:04 pm ¶Stopping the ICS service on Vista Ultimate SP2 resolved the Cisco VPN 442 Error. Version 5.0.03.0500
Posted 05 Jun 2009 at 12:08 am ¶i just installed Vista SP2 and the Cisco VPN stopped working with similar errors, i un-installed the VPN client and re-installed it under Administrator account via Runas cmd (since i had here and there 442 errors and i saw on a blog to install under admin account only).
Posted 10 Jun 2009 at 2:08 am ¶Thanks to Tim & Mo Jo. I tried your suggestion and worked perfectly. I dealt with this problem Since a year ago. God Bless!
Shame on Cisco and Microsoft. They did not do anything to help. Thanks again.
Posted 06 Aug 2009 at 7:29 pm ¶@Nathan: disabling ICS in Services worked like a charm. Let’s see how stable this one is.
Posted 21 Aug 2009 at 6:46 am ¶I had the same problem on my Vista home basic OS
Posted 12 Oct 2009 at 1:33 am ¶TIMs suggestion solved my issue.
Now running both the EXEs in XP-sp2 compatibility with administrator permission.
Thanks guys.
I tried to upgrade the VPN client to 5.0. All it did was mess up my network. Now I cannot access the internet at all. Tried uninstalling it and still have no luck getting online. I am running a vistas operating system. Any help???
Posted 20 Oct 2009 at 9:14 pm ¶Finally Solved – OMG!!! I'd been dealing with this forever and have tried every solution / suggestion out there and finally this one worked for me. Thank you Thank you Thank you.
From Nathan Le:
Under Services, I disabled Internet Connection Sharing (ICS) and then reboot. It then worked like a charm. By the way, I am using Windows Vista and Cisco VPN Client version 5.0.03.0560. Hope this helps.
Posted 26 Oct 2009 at 3:52 pm ¶Thanks for post. It`s help me in job
Posted 03 Dec 2009 at 12:36 pm ¶For more jobs visit http://www.staffingpower.com
Disabling Internet Connection Sharing did the job for me (although I checked “Allow local LAN access” as well, and never unchecked it afterwards). Cisco VPN Client version 5.0.06.0160
Posted 20 Dec 2009 at 10:35 am ¶Hi, it’s a so nice and good site ever. It’s a really great and fantastic post here in this site. Thank you for the sharing of your ideas and information to all of us.free scripts.Thanks Regard.
Posted 23 Dec 2009 at 5:14 am ¶Hi, it’s a so nice and good site ever. It’s a really great and fantastic post here in this site. Thank you for the sharing of your ideas and information to all of us.[url=http://www.needscripts.com]free scripts[/url]
Posted 23 Dec 2009 at 5:15 am ¶Hi, it’s a so nice and good site ever. It’s a really great and fantastic post here in this site. Thank you for the sharing of your ideas and information to all of us.
Posted 23 Dec 2009 at 5:15 am ¶It works now, thanks for sharing the trick. on Vista Home Premium and SP2 needs to uninstall the DNE and reinstall the vpn client using the real administrator.
Regards,
Posted 23 Dec 2009 at 9:10 am ¶It works now, thanks for sharing the trick. on Vista Home Premium and SP2 needs to uninstall the DNE and reinstall the vpn client using the real administrator.
Regards,
Posted 23 Dec 2009 at 5:10 pm ¶don't uninstall just run in xp sp2 mode
Posted 09 Jan 2010 at 2:07 am ¶Can you elaborate more on that ?
Posted 09 Jan 2010 at 2:46 am ¶Thank you everyone. I disabled the file sharing and internet sharing service and it worked.
Posted 28 Jan 2010 at 11:36 pm ¶THANK YOU Chkrata!
Posted 06 Feb 2010 at 1:51 am ¶I tried some of the first suggestions with no luck, then I saw Tim's suggestion and it worked great. I recommend everyone try this first,
Posted 03 Mar 2010 at 7:37 pm ¶I had this same problem start out of nowhere. After coming to this site and seeing some of the fixes, all I did was open C:Program FilesCisco SystemsVPN Client, right clicked on ipsecdialer.exe and vpngui.exe and clicked properties. I set both to run in xpSP2 compatibility mode and run as administrator. Problem was immediately fixed, no reinstallation was necessary and no DNE update was necessary. But yes I have to agree to let it run each time I start it.
Bill
Might I say that this forum is extensively helpful. But I suggest that maybe a good Registry Cleaner could help too. The thing about Registry Cleaners is that they constantly scan and clean your PC, preventing these and future errors like these from ever happening. I love them, and I strongly reccomend them.
Posted 27 Mar 2010 at 9:25 pm ¶turning off ICS did the trick for me (Windows 7) … tried almost all the other suggestions first with no luck. I guess error 442 is pretty generalized
Posted 27 May 2010 at 1:17 pm ¶issue is becoz of the protocol crated in network connections
Posted 13 Jun 2010 at 7:03 pm ¶disable cisco vpn adaptor in network connections and u will be fine
Thanks for your fix method. It's helpful:)
Posted 20 Jun 2010 at 1:00 pm ¶Disabling ICS as described by Nathan Le worked for me in Vista. No need to reboot.
Posted 24 Jun 2010 at 1:59 pm ¶I got the 442 error when I was trying to use the vpn client through my wireless connection. Try plugging into the LAN line. Worked for me
Posted 01 Jul 2010 at 10:02 pm ¶Man, thanks for your sharing! I learn a lot from you.
Posted 08 Jul 2010 at 10:21 am ¶Post a Comment