Reason 442 : Failed to enable Virtual Adapter

This Summer I had to go to my native place for some reason and I went home with my office laptop so that I can work remotely.After I reached home and tried to check my emails and some internal Sun sites, I could not connect to my VPN using Cisco VPN Client .So I immediately reached my PC Support guys and they could not help either.So I tried  googling for the problem,tweaked some settings in Symantec Endpoint Protection before getting to this link.This link has a very good desciption with nice screenshots.If you have also faced problem like me,you go ahead and visit this site.

After a quick restart, now I am able to connect to VPN and browse our local intranet sites.

In Summary(or for some reason the above link is broken) this worked for me,

  1. Start Menu
  2. Network
  3. Click on Network Sharing
  4. Click on Manage Networks in the new window opened
  5. Right Click on Cisco Adapter and click on Diaognise.
  6. Reset the Network adapter
  7. Now it says there is limited connectivity.Ignore it and restart the machine.
  8. Now try connecting to VPN.Thats all.Now you are connected.
  9. If you still unable to connect,Click here and search for the problem ;-).

Open VPN client, enable the log. Connect to the VPN, if the error comes check the logs. If the logs says something about this adapter not supported by Operating system. Then go to network connections, go to your "cisco vpn adapter" properties and check whether there is any other adapater installed and is used in "This connection uses the following" dialog. uncheck and press ok. Restart and connect to VPN.

OS: Windows XP SP3

Posted by Sezhiyan on April 29, 2010 at 11:51 AM IST #


Posted by guest on October 11, 2010 at 11:56 AM IST #


Posted by guest on October 11, 2010 at 11:56 AM IST #

I found a workaround for my issue which allowed your fix to work for me. I'm using version on Windows XP Home Edition, sp3 with McAfee antivirus. When I tried the fix that involved enabling vpn adaptor, setting tcp/ip to auto config, and then selecting repair, the message I would get is that it couldn't repair because tcp/ip wasn't enabled. I found out that by bridging the vpn with my hardware network adapter and then unbridging it, I was then able to do the repair on the vpn adaptor, and the connection now works again. Hope that helps.

Posted by kevin on August 04, 2011 at 01:31 AM IST #

services.msc -> disable ICS

works like a charm.

Posted by guest on November 29, 2011 at 08:00 AM IST #

services.msc -> disable ICS

works like a charm.

Posted by guest-123 on November 29, 2011 at 08:01 AM IST #

Done ThankX

Posted by guest on June 21, 2012 at 09:10 PM IST #

truly it works like a charm.

thanks a ton guys.

Posted by guest on November 17, 2012 at 07:51 AM IST #

Does not work for Windows 2008 x64. Tried both the 32 and 64 bit VPN client. No luck...

Posted by guest on June 06, 2013 at 02:13 PM IST #

This fix also works for me on Windows 8. Whenever there is a Windows update, my network goes out. Bridging the two networks and unbridging them does something which restores my local/internet network access.

Posted by kevin on June 09, 2013 at 01:01 PM IST #

whole day tried many option not done but ICD disable option worked well , thanks all , 2011 advised worked even in 2013 !thanks

Posted by guest on June 14, 2013 at 01:23 PM IST #

guest-123 - Thanks a lot. It really worked like a charm.

If still unable to fix, check this link out

Posted by Santhosh on September 18, 2013 at 11:40 AM IST #

services.msc -> disable ICS RULES!!!

Posted by guest on November 26, 2013 at 08:37 PM IST #

Big, big thanks! The option with disable ICS in services.msc solve the problem.
I think that source of the problem for me was enabled sharing internet connection in network card properties.

Posted by mickey on March 03, 2014 at 03:02 PM IST #

Post a Comment:
  • HTML Syntax: NOT allowed

This is my personal blog.All the information here reflects my own thoughts and feelings and should not be taken as official information from Oracle.


« April 2016