Error 51 Mac Cisco Vpn Client
Contents |
Subscribe Resources Macs MacBooks Mac Desktops iPhones Blogs iPads Accessories Apps Audio Business Cameras Components Development software Displays E-readers Home Theater iOS iPhone Accessories iPad Accessories iPods OS X Printers Networking Productivity Software Smartwatches Storage Styluses Mac Desktops MacBooks Displays Networking Storage Mac OS X Hints cisco vpn client mac error 51 snow leopard Boost your productivity with our Mac OS X tips and tricks Home Networking Fix an cisco mac vpn client error 51 lion error 51 with the Cisco VPN Client Comments By Rob Griffiths, Macworld Oct 17, 2008 12:57 PM One of the most-used programs on my
Cisco Vpn Client Mac Download
Mac is the Cisco VPN Client, which is what I use to connect to Macworld’s VPN when posting articles such as this one. (OS X’s built-in VPN client also works, but it also logs me out of and
Cisco Vpn Client Mac Error 51 Unable Communicate Vpn Subsystem
then back into iChat every time I connect or disconnect from the VPN. The Cisco VPN Client doesn’t have this annoying problem, so I use it instead.) While the Cisco VPN Client works well most of the time, sometimes when I try to launch the application, I’m greeted with this error message in place of the usual connection dialog: Error 51: Unable to communicate with the VPN subsystem. Please make sure that you have at least one cisco vpn client osx network interface that is currently active and has an IP address and start this application again. The error is clearly incorrect, because my machine’s networking capabilities are otherwise fine—I can browse the net, send and receive e-mail, and connect to other machines in the house. I don’t get the error message all the time, and I don’t really know what causes it. It does seem to happen more often if I’ve slept and woke the machine, or moved it from one defined location to another, but even then, it’s not predictable. All I know for sure is that it’s annoying, because (until recently) the only fix I was aware of was to reboot the machine. One day, after probably the second or third time I’d restarted my machine, I decided there must be a better solution, so I went digging to see if anyone else had already found one—and they had. As detailed on the linked site, the solution is a relatively simple command that you execute in Terminal (found in Applications -> Utilities). After discussing the Terminal command with a friend, he came up with an even simpler version that works just as well: sudo SystemStarter restart CiscoVPN You’ll need to be an administrative user to run this command, and provide your admin password when asked. You won’t see any output from the command; the Terminal prompt will ret
in Mac OS X instead of the CiscoVPN software. Here's a guide that tells you how to convert from CiscoVPN to the native OS X client. If you are running Cisco's VPNClient on Mac OSX, you might be familiar with (or
Cisco Vpn Client Linux
tormented by) "Error 51: Unable to communicate with the VPN subsystem". The simple fix is to cisco vpn client ubuntu quit VPNClient, open a Terminal window, (Applications -> Utilities -> Terminal) and type one of the following: (for older versions) sudo /System/Library/StartupItems/CiscoVPN/CiscoVPN restart (for cisco vpn client windows 64 bit newer versions) sudo kextload /System/Library/Extensions/CiscoVPN.kext and give your password when it asks. This will stop and start the "VPN Subsystem", or in other words restart the CiscoVPN.kext extension. Cisco seems to have problems when network adapters disappear and reappear, http://www.macworld.com/article/1136208/ciscovpn.html something that happens commonly in Wireless or Dial-up scenerios. Sometimes putting a system to sleep, disconnecting an Ethernet cable or simply reconnecting your wireless will cause CiscoVPN to loose track of the network adapters on the system. Considering that CiscoVPN is typically used by telecommuters, this is an astonishing oversight on Cisco's part. The above hack should side-step all of these issues by causing the CiscoVPN to re-initialize. It makes one ask, why couldn't Cisco have just put the restart http://www.anders.com/cms/192/CiscoVPN/Error.51:.Unable.to.communicate.with.the.VPN.subsystem into their client? Or a better idea would be to not reinvent the wheel and use the existing IPSec VPN support in OSX! Am I missing something? EDIT: The MacWorld guys came up with a simpler way to do the same thing: sudo SystemStarter restart CiscoVPN Posted by Anders Brownworth Monday, November 13, 2006 7:25 PM Tweet Comments (269) Jeff from Chicago #1 | Friday, March 23, 2007 6:53 AM Thanks for the tip - this worked like a charm. todd from boston #2 | Thursday, March 29, 2007 10:29 AM you the man - thanks! Tony from Carmel from Carmel #3 | Friday, March 30, 2007 6:49 PM Didn't work but rebooted my computer and the problem went away. Steve from Minneapolis #4 | Friday, May 4, 2007 5:30 PM Nice - works to correct the same issue when running Windows on a Mac (restart the Cisco VPN Service). Jason McCarty from Canada #5 | Monday, May 7, 2007 11:08 PM This did not work for me. I've gotten this error ever since I installed the VPN from cisco. I have the 4.9 version as well. What else might I need to do? Anders from RTP #6 | Tuesday, May 8, 2007 9:50 AM Yep, a friend of mine pointed that out and I have since confirmed it. Apple's new security update kills CiscoVPN when using dialup adapters. I don't yet have a work-around tho
enter a title. You can not post a blank message. Please type your message and try again. buzz8976 Level 1 (0 points) Q: Cisco VPN Client Error 51 message since upgrade to Lion Since upgrading to OS X Lion I can no https://discussions.apple.com/thread/3195725?start=0&tstart=0 longer use Cisco VPN Client, I keep getting the following error message:Error 51: Unable to communicate with the VPN subsystem. Please make sure that you have at least one network interface that is currently active and has https://www.bol.ucla.edu/alert/20110722.html an IP address and start this application again.Please help I need remote desk top for work. MacBook Pro, Mac OS X (10.6.4) Posted on Jul 21, 2011 12:12 PM I have this question too Close Q: Cisco vpn client VPN Client Error 51 message since upgrade to Lion All replies Helpful answers by Asatoran, Asatoran Jul 21, 2011 2:00 PM in response to buzz8976 Level 4 (2,525 points) Jul 21, 2011 2:00 PM in response to buzz8976 Are you using the software client from Cisco, or OSX's built-in VPN? In my experience, almost every operating system upgrade has needed a update to the VPN client software. Have you checked if there's a newer Cisco cisco vpn client client for your office?That said, have you tried uninstalling and reinstalling the Cisco software? Also, OSX's built-in VPN client works for many Cisco implementations, so works for a lot of people. If possible, I recommend uninstalling Cisco's software an see if you can configure OSX's VPN. I'm currently using OSX's VPN to a Cisco ASA 5510 with SecureID authentication. With OSX 10.6.8 and 10.7. (And on my iPad as well. ) Helpful (0) Reply options Link to this post by buzz8976, buzz8976 Jul 21, 2011 2:12 PM in response to Asatoran Level 1 (0 points) Jul 21, 2011 2:12 PM in response to Asatoran Hi AsatoranI did as you suggested I uninstalled it downloaded this version: VPN Client 4.9 for Mac from this site: http://www.helpdesk.ugent.be/vpn/en/akkoord.phpAnd it seems to be working perfectly now.Thanks Helpful (0) Reply options Link to this post by wickdillon, wickdillon Jul 30, 2011 1:43 PM in response to buzz8976 Level 1 (10 points) Jul 30, 2011 1:43 PM in response to buzz8976 Check out this link: When going to a 64 bit OS (For me, it broke with Lion) the Cisco VPN no longer works because it is a 32 bit application. http://jmilbery.wordpress.com/2011/07/26/cisco-vpn-with-macos-lion/The native OS VPN works fine for me connecting to an ASA. Conencting to a VPN 3k concentrator can have mixed results, because they haven't updated those th
on 6/30 News archive rss BOL Webmail Have a question? Click here to search our knowledge base. © Bruin OnLine 7/22/2011: Cisco VPN Client compatibility with Mac OS 10.7/Lion The current version of the Cisco VPN Client does not appear to run properly if Mac OS is running the 64-bit kernel. Mac OS 10.7/Lion runs the 64-bit kernel by default. Users will see the error "Error 51: Unable to communicate with the VPN subsystem" when starting the VPN. Until Cisco releases a compatible client, there are a few workarounds available: Set Mac OS X to boot using the 32-bit kernel according to the instructions in Apple's support article Configure the Mac OS X built-in VPN client to connect to the UCLA VPN using any one of the following protocols: PPTP Cisco IPSEC Please note that this issue is not specific to Mac OS 10.7/Lion. Apple has a list of Macs that use the 64-bit kernel by default as well as instructions to find out if you're using 64-bit mode. If you have any questions, please contact the BOL Help Desk at (310)267-4357 or at consult@ucla.edu. UCLA Home | UCLA Directory | URSA | MyUCLA | Library | BruinCard | Sitemap Last Updated Fri Jul 22 12:46:58 PDT 2011 'tk' consult@ucla.edu