Captain the warp subsystems are down what should we do?!!!   January 14th, 2008

Over the last two years I have become quite the Mac/OSX fan.  For years I was down on apple and to this day think I had every right to be.  But with OS 10.4 and now 10.5 they have created a powerful and flexible unix distribution for the general user and the power users.  However I have from time to time notices funky issues with software such as the Cisco IpSec VPN client.

Most recently in 10.5.1 I kept getting the VPN subsystem could not be contacted.  Well here is the fix from nate,

“If you are running Cisco’s VPNClient on Mac OSX, you might be familiar with (or tormented by) “Error 51: Unable to communicate with the VPN subsystem”. The simple fix is to quit VPNClient, open a Terminal window, (Applications -> Utilities -> Terminal) and type the following:
sudo /System/Library/StartupItems/CiscoVPN/CiscoVPN restart
and give your password when it asks. This will stop and start the “VPN Subsystem”, or in other words restart the CiscoVPN.kext extension.”

Thanks Nate and I hope this help everyone else out there keep their WARP core under control….later!

  • del.icio.us
  • NewsVine
  • Reddit
  • Digg
  • Slashdot
  • StumbleUpon
  • Technorati
  • email
  • Facebook
  • Google Bookmarks
  • LinkedIn
  • Live
  • TwitThis

If you're new here, you may want to subscribe to my RSS feed. Thanks for visiting!

No related posts.

Related posts brought to you by Yet Another Related Posts Plugin.

This entry was posted on Monday, January 14th, 2008 at 3:01 pm and is filed under *NIX, Apple, Cisco, PIX/ASA, Security. You can follow any responses to this entry through the RSS 2.0 feed.You can leave a response, or trackback from your own site.

One Response

December 30th, 2008 at 9:22 pm
gmsmith Says:

Yes, isn’t this a fabulous feature of the Cisco VPN Client for Mac?

Leave a Reply

You must be logged in to post a comment.