Error 51 Os X Lion
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 os x mountain lion Mac Desktops MacBooks Displays Networking Storage Mac OS X Hints Boost your productivity
Os X Lion Download
with our Mac OS X tips and tricks Home Networking Fix an error 51 with the Cisco VPN Client Comments os x lion system requirements By Rob Griffiths, Macworld Oct 17, 2008 12:57 PM One of the most-used programs on my Mac is the Cisco VPN Client, which is what I use to connect to Macworld’s VPN when posting
Os X Lion Review
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 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 os x lion features 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. 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 T
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
Mac Os X Lion Bootable Vmdk
no issues using Cisco's VPN Client (4.9.01). With Lion, Error 51 is being returned
Os X Lion Server
stating it is unable to communication with the subsystem.Is there a known workaround for this?Thank you! Mac mini, Mac OS X reinstall mac os x lion (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 http://www.macworld.com/article/1136208/ciscovpn.html 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 https://discussions.apple.com/thread/3194876?start=0&tstart=0 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 wickdil
2 Guide List Of Mac OS X Error Codes Windows Server 2012 Xsan Apple Configurator 1 Guide Commands Amazon s3cmd Commands Crosh Commands Final Cut Server http://krypted.com/lists/comprehensive-list-of-mac-os-x-error-codes/ Commands FTP Commands Linux Bash Commands Mac Commands Podcast Producer Commands Powershell Commands Windows Commands Xsan Commands Reference Nike+ and NikeFuel Badge List Fitbit Badge List Foursquare Badge List Apple Watch Achievements List List of All Swarm Stickers HTML Encoding Reference CIDR Conversion Table Common Apple Ports List Of Mac OS X Error Codes Whoami whoami Legacy Mac Apps Books Dead Tech Books Clothes Apple Community Apple os x Admin Conferences MacAdmins Speaking Engagements My Bushel Blog Posts Glossary of Apple Terms Minneapolis Minneapolis Breweries and Distilleries List Of Mac OS X Error Codes General Errors paramErr = -50, /*error in user parameter list*/ noHardwareErr = -200, /*Sound Manager Error Returns*/ notEnoughHardwareErr = -201, /*Sound Manager Error Returns*/ userCanceledErr = -128, qErr = -1, /*queue element not found during deletion*/ vTypErr = -2, /*invalid queue os x lion element*/ corErr = -3, /*core routine number out of range*/ unimpErr = -4, /*unimplemented core routine*/ SlpTypeErr = -5, /*invalid queue element*/ seNoDB = -8, /*no debugger installed to handle debugger command*/ controlErr = -17, /*I/O System Errors*/ statusErr = -18, /*I/O System Errors*/ readErr = -19, /*I/O System Errors*/ writErr = -20, /*I/O System Errors*/ badUnitErr = -21, /*I/O System Errors*/ unitEmptyErr = -22, /*I/O System Errors*/ openErr = -23, /*I/O System Errors*/ closErr = -24, /*I/O System Errors*/ dRemovErr = -25, /*tried to remove an open driver*/ dInstErr = -26 /*DrvrInstall couldn't find driver in resources*/ abortErr = -27, /*IO call aborted by KillIO*/ iIOAbortErr = -27, /*IO abort error (Printing Manager)*/ notOpenErr = -28, /*Couldn't rd/wr/ctl/sts cause driver not opened*/ unitTblFullErr = -29, /*unit table has no more entries*/ dceExtErr = -30, /*dce extension error*/ slotNumErr = -360, /*invalid slot # error*/ gcrOnMFMErr = -400, /*gcr format on high density media error*/ dirFulErr = -33, /*Directory full*/ dskFulErr = -34, /*disk full*/ nsvErr = -35, /*no such volume*/ ioErr = -36, /*I/O error (bummers)*/ bdNamErr = -37, /* bad file name passed to routine; no bad names in the final system!*/ fnOpnErr = -38, /*