Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!

10.4: A fix for the Cisco VPN Client 4.6.03 Network
Tiger only hintAfter digging around on the Internet for quite some time, I came across this hint on a German website. I used an online translation site to translate the text to a rough English version. Wish Cisco could be as helpful as the Germans...

You will need to use the Terminal to perform this modification. What you need to do is replace the cvpnd file in /opt/cisco-vpnclient/bin with an extracted version from the installer disk image. Once you have replaced the cvpnd file, you should verify the proper permissions have been set on the file once it has been replaced. Here is a cleaned up version for your digestion.

  1. Mount the vpnclient disk image, then create a directory on your desktop, and extract the file from the disk image to that directory. Now Open the Terminal and perform the following commands:
    $cd ~/Desktop
    mkdir Cisco_tmp
    cd Cisco_tmp
    gzcat /Volumes/CiscoVPNClient/Cisco VPN Client.mpkg/vpnclient-bin.pkg/
    Contents/Resources/vpnclient-bin.pax.gz"| pax -r
    
  2. Copy the extracted cvpnd file to the default installation directory for by using the following commmand in the Terminal:
    sudo cp /Users/local_admin/Desktop/Cisco_tmp/opt/
    cisco-vpnclient/bin/cvpnd /opt/cisco-vpnclient/bin/
    
  3. Finally, you must set the correct permissions of the cvpnd file using the following command in the Terminal:
    sudo chmod 4711 /opt/cisco-vpnclient/bin/cvpnd
    Issue the following to verify the permissions took and that they look like this: rws--x--x:
    ls -al /opt/cisco-vpnclient/bin/cvpnd
Use the Cisco VPN client and see if it works. If anything, it fixed a few of the major bugs hindering the client's functionality. For me, the most important, allowing me to use the VPN client to connect to resources on our network remotely.

Note: You will need to use the IP address (192.168.50.100) rather than the DNS name (myserver.mydomain.com) to connect to any resources. For some reason, connecting to resources using the DNS name fails. Personally, I use the nslookup utility in the Terminal to verify the resource's IP address, and then mount the resource using Go -> Connect to Server in the Finder in the following manner: smb://192.168.50.100/share or afp://192.168.50.100/share
    •    
  • Currently 1.50 / 5
  You rated: 2 / 5 (4 votes cast)
 
[22,487 views]  

10.4: A fix for the Cisco VPN Client 4.6.03 | 17 comments | Create New Account
Click here to return to the '10.4: A fix for the Cisco VPN Client 4.6.03' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
10.4: A fix for the Cisco VPN Client 4.6.03
Authored by: bvdecicco on Jun 13, '05 10:06:14AM

Does this fix the dual processor issue?



[ Reply to This | # ]
10.4: A fix for the Cisco VPN Client 4.6.03
Authored by: tinpan on Jun 13, '05 10:19:08AM
Cisco VPN Client 4.6.04 is out:
http://www.versiontracker.com/dyn/moreinfo/macosx/12696

Has anyone tried it?

[ Reply to This | # ]
10.4: A fix for the Cisco VPN Client 4.6.03
Authored by: Reggaefire on Jun 13, '05 10:27:36AM

The newest VPN (4.6.04.0061) works on my dual processor and single processor 10.4 machines, so for me at least, it looks like they've got their problems sorted out.



[ Reply to This | # ]
10.4: A fix for the Cisco VPN Client 4.6.03
Authored by: jyu on Jun 13, '05 10:31:18AM

Yes, for some reason, the DNS lookup doesn't use the remote -- company network's DNS server. I, too, have to use the IP addresses to connect to the server. DNS works in 10.3, but not in 10.4.



[ Reply to This | # ]
10.4: A fix for the Cisco VPN Client 4.6.03
Authored by: jyu on Jun 13, '05 10:40:13AM

Here is the release note for 4.6.04.0061:

Resolved Issues

CSCeh90822 unity mac dual proc panic in 10.4
CSCeh92574 unity mac 10.4 afp panics kernel
CSCeh93569 unity mac will not quit or disconnect on 10.4 no traffic
CSCeh93719 unity mac profile name rejects spaces
CSCeh95185 unity mac help file not found
CSCeh96683 unity mac 10.4 quit disconnect with no default domain name


Unresolved Issues

CSCeh90939 unity mac rekey failure with 10.4
CSCei00630 unity mac switching networks prevents client connect 10.4
CSCei11378 unity mac error 47: failed to load ipseclog.exe
CSCeh93891 unity mac gui many split tunnels will not pass traffic 10.4



[ Reply to This | # ]
10.4: A fix for the Cisco VPN Client 4.6.03
Authored by: Han Solo on Jun 13, '05 12:24:27PM

Thanks for that updated info! Can anyone confirm that remote AFP connections now work correctly with the latest client?



[ Reply to This | # ]
10.4: A fix for the Cisco VPN Client 4.6.03
Authored by: erikwb on Jun 13, '05 03:44:39PM

Yes, it works.



[ Reply to This | # ]
Just released client works without modification
Authored by: sjonke on Jun 13, '05 11:48:54PM

At least that has been my experience in limited testing. Yes, I have mounted file servers, both afp and smb. No problems. telnet, ssh, sftp and ftp all work as well.

---
--- What?



[ Reply to This | # ]
10.4: A fix for the Cisco VPN Client 4.6.03
Authored by: Schwie on Jun 14, '05 07:55:24PM
10.4: A fix for the Cisco VPN Client 4.6.03
Authored by: Schwie on Jun 14, '05 09:08:50PM

Has anyone seen the following error message? I tried uninstalling, reinstalling, and restarting, and nothing seems to get the VPN Client to launch. Help!

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

My AirPort Card is receiving an IP address, I have connectivity to the internet, and I even tried turning IPv6 off in in favor of IPv4. Nothing seems to help. Help!



[ Reply to This | # ]
10.4: A fix for the Cisco VPN Client 4.6.03
Authored by: Schwie on Jun 14, '05 09:59:51PM

I figured it out!

Over the weekend, I transferred some files over to an iMac that didn't have AirPort and its ethernet port was fried. So, I set up Internet Sharing using Firewire between the iMac and my TiBook.

After I finished transferring the files over, I disconnected the Firewire and disabled the Firewire port on my TiBook in the Network preferences, but I never turned off Internet Sharing. This is kind of a bug in Mac OS X, because while the Macs were disconnected, I went back into Internet Sharing, and the buttons were grayed out - so, I assumed that Internet Sharing was off, but the Cisco VPN Client still didn't work...

Low and behold, when I went into Network Preferences on the TiBook, turned the Firewire port back on, and then checked Internet Sharing tab under Sharing, the buttons were lit up again, and it revealed to me that Internet Sharing was on! After I clicked stop, and then disabled the Firewire port again, the Cisco VPN Client connected again!!! Woohoo!



[ Reply to This | # ]
10.4: A fix for the Cisco VPN Client 4.6.03
Authored by: Anonymous on Jun 18, '05 12:44:25AM

THERE IS A BUG!!!!!! (I think!)

I was getting the same error you were, Error 51:Unable to connect the VPN Subsystem...

I did NOT have Internet Sharing via Firewire turned on (I have had no reason to even use it) but...when I looked, it was ON!

I think something in the installation is turning Internet Sharing via Firewire "on".

Turned it off, and the VPN client works great! Works with Internet Sharing over Airport or Ethernet on, but not Firewire.

---
"The cemeteries of the world are full of indispensable men"
Charles de Gaulle



[ Reply to This | # ]
10.4: A fix for the Cisco VPN Client 4.6.03
Authored by: ogunasek on Jun 26, '05 08:17:14PM

I also have this problem. (Error 51)

Oliver



[ Reply to This | # ]
10.4: A fix for the Cisco VPN Client 4.6.03
Authored by: ogunasek on Jun 26, '05 08:23:11PM

I found the following:

Macintosh OS X 10.4 (Tiger) users may receive the following error message:

Error 51: IPC socket allocation failed with error fffffffffffffffch. This is most likely due to the Cisco Systems, Inc. VPN service not being started. Please start this service and try again.

To correct this problem, open a terminal window and type:
sudo /System/Library/StartupItems/CiscoVPN/CiscoVPN restart

If this does not correct the problem, try rebooting your system.



[ Reply to This | # ]
10.4: A fix for the Cisco VPN Client 4.6.03
Authored by: giantmike on Jun 28, '05 08:37:27AM

Thanks a ton ogunasek!

I didn't have firewire sharing on like those other people, so I was kind of scared there would not be an answer for me. But your suggestion worked perfectly.

---
Giantmike's Website - http://www.giantmike.com



[ Reply to This | # ]
10.4: A fix for the Cisco VPN Client 4.6.03
Authored by: sjha on Jul 13, '05 02:59:36PM

I was surprised to find that when I installed Cisco VPN Client 4.6 it created a VISIBLE 'opt' directory at the highest level (the one that shows Applications, System etc) on my Mac. Is this what shoud happen? I would have thought that the directory should either be invisible or nested somewhere lower in the directory hierarchy. Any advice would be appreciated.

---
Steve Ashcroft



[ Reply to This | # ]
10.4: A fix for the Cisco VPN Client 4.6.03
Authored by: jollyroger on Aug 09, '05 06:45:30PM

I have exactly the same problem: Even the latest release (4.7.00) of the client installs a /opt file that cannot be hiddden. : (

I've tried to force this file to be hidden in numerous ways without success. Here's what I've tried:

1. This is a symbolic link to the /private/opt/directory. You cannot delete this symbolic link without rendering the VPN client inoperative.

2. Adding a "/opt" entry in /.hidden does not hide the file.

3. Issuing a "sudo /Developer/Tools/SetFile -a v /opt" command does not hide the file.

There seems to be little we can do about this problem until Cisco fixes it from their end, unfortunately. : ( If someone else knows different, please share it here!

-mono

---
-monoclast



[ Reply to This | # ]