10.4: A fix for the Cisco VPN Client 4.6.03
Jun 13, '05 08:53:00AM
Contributed by: sxdxoutlaw
After 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.
- 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
- 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/
- 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
Comments (18)
Mac OS X Hints
http://hints.macworld.com/article.php?story=20050525204044989