Cisco Vpn Client Mac Error 51 Snow Leopard
Contents |
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 cisco vpn client for mac 10.6 download running Cisco's VPNClient on Mac OSX, you might be familiar with (or tormented
Cisco Vpn Client Windows 64 Bit
by) "Error 51: Unable to communicate with the VPN subsystem". The simple fix is to quit VPNClient, open a Terminal window,
Download Cisco Ipsec Vpn Client
(Applications -> Utilities -> Terminal) and type one of the following: (for older versions) sudo /System/Library/StartupItems/CiscoVPN/CiscoVPN restart (for newer versions) sudo kextload /System/Library/Extensions/CiscoVPN.kext and give your password when it asks. This will stop
Cisco Vpn Linux
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, 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 vpn tamu mac 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 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
Twitter Google + LinkedIn Newsletter Instagram YouTube DirectoryNetwork InfrastructureWAN, Routing and Switching LAN, Switching and Routing Network Management Remote Access Optical Networking Getting Started with LANs IPv6 Integration cisco anyconnect vpn client mac and Transition EEM Scripting Other Subjects SecurityVPN Security Management Firewalling Intrusion error 51 unable to communicate with the vpn subsystem windows 7 Prevention Systems/IDS AAA, Identity and NAC Physical Security MARS Email Security Web Security Other Subjects Service ProvidersMetro vpn client for mac MPLS Voice Over IP XR OS and Platforms Video Other Subjects Collaboration, Voice and VideoIP Telephony Video Over IP Jabber Clients Unified Communications Applications TelePresence Digital Media http://www.anders.com/cms/192/CiscoVPN/Error.51:.Unable.to.communicate.with.the.VPN.subsystem System Contact Center Conferencing UC Migrations Other Subjects Wireless - MobilitySecurity and Network Management Wireless IP Voice and Video Getting Started with Wireless WLCCA Other Subjects ServicesCisco ServiceGrid Connected Analytics Smart Call Home Smart Net Total Care Operations Exchange Mobile ApplicationsCisco Proximity Cisco Technical Support Online Tools and ResourcesCisco Bug Discussions Technical Documentation Ideas Cisco https://supportforums.cisco.com/document/18796/cisco-ipsec-vpn-client-mac-os-x-generates-error-error-51-unable-communicate-vpn CLI Analyzer Support Community Help Data CenterApplication Centric Infrastructure Application Networking Intelligent Automation Server Networking Storage Networking Unified Computing Wide Area Application Services (WAAS) Other Subjects Small BusinessNetwork Storage Routers Security Surveillance Switches Voice and Conferencing Wireless Solutions and ArchitecturesBorderless Networks Collaboration Cisco User GroupsSeattle Cisco User Group (SEACUG) Silicon Valley Cisco User Group (SVCUG) Southern California Cisco User Group (SCCUG) Cisco Certifications Cisco.com Idea Center Cisco Cafe Expert CornerTop Contributors Leaderboards Cisco Live! Events Events Community CornerAwards & Recognition Behind the Scenes Feedback Forum Cisco Certifications Cisco Press Café Cisco On Demand Support & Downloads Community Resources Security Alerts Security Alerts News News Video Cisco Support YouTube Cisco YouTube Blogs Technical Documentation Cisco Products Products Services Services Solutions Solutions Global Support Numbers Cisco Support Community Directory Network Infrastructure WAN, Routing and Switching LAN, Switching and Routing Network Management Remote Access Optical Networking Getting Started with LANs IPv6 Integration and Transition EEM Scripting Other Subjects Security VPN Security Management Firewalling Intrusion Prevention Systems/IDS AA
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 http://www.macworld.com/article/1136208/ciscovpn.html OS X Printers Networking Productivity Software Smartwatches Storage Styluses Mac Desktops https://discussions.apple.com/thread/3194876?start=0&tstart=0 MacBooks Displays Networking Storage Mac OS X Hints Boost your productivity with our Mac OS X tips and tricks Home Networking Fix an 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 vpn client 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 then back into iChat every time I connect or disconnect from the VPN. The Cisco VPN Client doesn’t have this cisco vpn client 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 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
enter a title. You can not post a blank message. Please type your message and try again. lgldsr712 Level 1 (4 points) iPod Q: Cisco VPN and Lion - Error 51 Prior to upgrading to Lion there were no issues using Cisco's VPN Client (4.9.01). With Lion, Error 51 is being returned stating it is unable to communication with the subsystem.Is there a known workaround for this?Thank you! Mac mini, Mac OS X (10.6.8) Posted on Jul 21, 2011 9:17 AM I have this question too by wickdillon,Solvedanswer wickdillon Level 1 (10 points) A: 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 things in a while, and they will be end of support from Cisco next year.The OS VPN can be configured in your network properties, and you get to stay in 64 bit mode. Posted on Jul 30, 2011 1:44 PM See the answer in context Close Q: Cisco VPN and Lion - Error 51 All replies Helpful answers by Warren Lin,★Helpful Warren Lin Jul 21, 2011 4:30 PM in response to lgldsr712 Level 1 (30 points) Jul 21, 2011 4:30 PM in response to lgldsr712 I had the same issue. Someone suggested I hold down the 2 and 3 keys when I restart so that the system will revert back to 32 bit (whatever that means). It worked after I did that. I just need to remember to hold it down whenever I turn the computer on. Or else, I'll have to restart to access the VPN.I'm not sure what gets affected when you do this though. But, I seem to be able to carry on very well. Helpful (1) Reply options Link to this post by lgldsr712, lgldsr712 Jul 21, 2011 6:13 PM in response to Warren Lin Level 1 (4 points) iPod Jul 21, 2011 6:13 PM in response to Warren Lin Many thanks - that did in fact work but as you know it's a bandaid patch.Does anyone know if Cisco is addressing this issue?Thanks! Helpful (0) Reply options Link to this post by wickdillon,Solvedanswer wickdillon Jul 30, 2011 1:44 PM in response to lgldsr712 Level 1 (10 points) Jul 30, 2011 1:44 PM in response to lgldsr712 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 updat