Skip to main content

winnate – using windows 8 with cisco vpn

are you having the same connection issue i was when trying to use the cisco vpn client? here’s what the message looks like:

SNAGHTML290ab301

the message states: Reason 442: Failed to enable Virtual Adapter.

this is the second time i’ve had to do this so i figured capture it. anyway, found the steps here: http://social.msdn.microsoft.com/Forums/en-US/windowsdeveloperpreviewgeneral/thread/6fe817f3-27fe-4068-995a-aced4508ee3e

anyway, it looks like the vpn client tries to enable the virtual adapter by its display name. the installation does some funky crap with the display name:
  • broke: @oem8.inf,%CVirtA_Desc%,Cisco Systems VPN Adapter for 64-bit Windows
  • good: Cisco Systems VPN Adapter for 64-bit Windows

once you remove the crud and try again, it works. here’s the actual steps that raman posted:
Open Registry editor by typing regedit in Run prompt
  • Browse to the Registry Key HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Services\\CVirtA
  • Select the DisplayName to modify, and remove the leading characters from the value data up to "%;" 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”
  • Try connecting again

    Comments

    1. This worked perfectly to resolve the issue I was having. Thanks heaps for posting it!

      ReplyDelete
    2. Hmm it appears like your website ate my first comment (it was extremely long) so I
      guess I'll just sum it up what I had written and say, I'm thoroughly enjoying your blog. I too am an aspiring blog writer but I'm still new to the whole thing. Do you have any suggestions for novice blog writers? I'd really appreciate it.
      My webpage tf2 hack

      ReplyDelete
    3. After 1.5 hours fighting the problem were solved. Thanks a lot.

      ReplyDelete
    4. Thank's! \o/

      ReplyDelete
    5. Thank you for the fix!!!!! Worked like a charm.

      ReplyDelete
    6. Worked PERFECTLY ! Thank you thank you thank you !!!!

      ReplyDelete
    7. That was the solution.
      Thx. :)

      ReplyDelete
    8. Fantastic... Thanks for this

      ReplyDelete
    9. thanks for the trick
      do guys have connection speed after connected with vpn?

      ReplyDelete
    10. Thanks for the solution.

      ReplyDelete
    11. worked perfectly

      ReplyDelete
    12. Reason 442!!!! Thanks a lot. That was the solution.

      ReplyDelete
    13. Thank you very much!

      ReplyDelete

    Post a Comment

    Popular posts from this blog

    using preloadpkgonsite.exe to stage compressed copies to child site distribution points

    UPDATE: john marcum sent me a kind email to let me know about a problem he ran into with preloadpkgonsite.exe in the new SCCM Toolkit V2 where under certain conditions, packages will not uncompress.  if you are using the v2 toolkit, PLEASE read this blog post before proceeding.   here’s a scenario that came up on the mssms@lists.myitforum.com mailing list. when confronted with a situation of large packages and wan links, it’s generally best to get the data to the other location without going over the wire. in this case, 75gb. :/ the “how” you get the files there is really not the most important thing to worry about. once they’re there and moved to the appropriate location, preloadpkgonsite.exe is required to install the compressed source files. once done, a status message goes back to the parent server which should stop the upstream server from copying the package source files over the wan to the child site. anyway, if it’s a relatively small amount of packages, you can

    How to Identify Applications Using Your Domain Controller

    Problem Everyone has been through it. We've all had to retire or replace a domain controller at some point in our checkered collective experiences. While AD provides very intelligent high availability, some applications are just plain dumb. They do not observe site awareness or participate in locating a domain controller. All they want is the name or IP of one domain controller which gets hardcoded in a configuration file somewhere, deeply embedded in some file folder or setting that you are never going to find. How do you look at a DC and decide which applications might be doing it? Packet trace? Logs? Shut it down and wait for screaming? It seems very tedious and nearly impossible. Potential Solution Obviously I wouldn't even bother posting this if I hadn't run across something interesting. :) I ran across something in draftcalled Domain Controller Isolation. Since it's in draft, I don't know that it's published yet. HOWEVER, the concept is based off

    sccm: content hash fails to match

    back in 2008, I wrote up a little thing about how distribution manager fails to send a package to a distribution point . even though a lot of what I wrote that for was the failure of packages to get delivered to child sites, the result was pretty much the same. when the client tries to run the advertisement with an old package, the result was a failure because of content mismatch. I went through an ordeal recently capturing these exact kinds of failures and corrected quite a number of problems with these packages. the resulting blog post is my effort to capture how these problems were resolved. if nothing else, it's a basic checklist of things you can use.   DETECTION status messages take a look at your status messages. this has to be the easiest way to determine where these problems exist. unfortunately, it requires that a client is already experiencing problems. there are client logs you can examine as well such as cas, but I wasn't even sure I was going to have enough m