error 51 unable to to communicate with the vpn subsystem

Question

error 51 unable to to communicate with the vpn subsystem

I am having trouble connecting through the Cisco VPN Client on my MacBook Pro. Strangely, the same program works fine on my iMac.

I receive this error:

Error 51: Unable to communicate withg the VPN subsystem. Please make sure that you ahve at least one network interface that is currently active and has an IP address and start this application again.

I have tried several of the work arounds using the terminal "restart" fix that has been suggested but that does not work either.

Any ideas?

Thanks!

Wendy

MacBook Pro, Mac OS X (10.6.7)

Posted on Apr 27, 2011 12:53 PM

Reply

Answer 1

Apr 27, 2011 12:56 PM in response to wendyfromtampa

are your certificates in system and not user??

I'm interested in this solution as I use vyper to watch netflix..

Reply

Answer 2

Apr 27, 2011 1:25 PM in response to Germany_chris

I'm not really sure as I got the software download from the Dept of Vet Affairs. After doing some digging I saw that someone suggested booting up in 32-bit and that worked!

I have no idea why booting in 32 bit works and the 64 bit does not but at least now I can access my work email!

Reply

Answer 3

Apr 27, 2011 1:33 PM in response to wendyfromtampa

really they allow that!! DA no longer allows VPN's to access outlook or anything else for that matter..wiki leaks was the straw that broke the camels back..speaking of VA can you double my disability check..not only will my ankle need replaced, but my hearing is getting worse 😁 I receive compensation for both 😁)

Reply

Answer 4

Jul 30, 2011 1:41 PM in response to wendyfromtampa

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. It can be configured in your network properties, and you get to stay in 64 bit mode.

Reply

Answer 5

Aug 16, 2011 11:52 AM in response to wendyfromtampa

Here's what I used to fix this problem, worked like magic bit.ly/lfLcF4

Reply