Juniper Network Connect on Mac OS Snow Leopard

UPDATE: The version 6.5 client seems to fix this problem. Update your SSL/VPN server if you’re having the problem described below.

The Juniper Network Connect app, used to create a VPN tunnel to a Juniper protected network, works fine with OS X 10.5, but doesn’t want to install in OS X 10.6.

This is a known problem, and there are knowledge base articles and blogs that address this one, but I couldn’t find any place that gathers the information in a way that addresses all of the associated problems.

First of all, there’s a problem with file rights and a missing directory if upgrading from Leopard to Snow Leopard. It is discussed, among other places, here.

The solution basically consists of two console commands:

sudo chmod 755 /usr/local/juniper/nc/[version number]/
sudo mkdir -p '/Applications/Network'

The other problem, is a question of the Network Connect web installer app not being able to install, quitting with an error message “An error occurred while extracting one of the Network Connect components.

This problem has to do with a change Sun did to a default password during one of the updates to Java, and is discussed in this knowledge base article.

Basically, the solution is to set this password to it’s old value with the following line (exclude the carriage return after keystore, since it’s only there to make the lines readable):

sudo keytool -storepasswd -new changeit -keystore 
/System/Library/Frameworks/JavaVM.framework/Resources/Deploy.bundle/Contents/Home/lib/security/cacerts -storepass changeme

The password can then be restored by reversing the command above.


2 thoughts on “Juniper Network Connect on Mac OS Snow Leopard”

  1. When I ran the command I got the following error:
    Permission denied
    sudo: no valid sudoers sources found, quitting

    1. Who is allowed to use the sudo command on a computer, is decided in the /etc/sudoers file. Based on your error message, I suspect the permissions are faulty on that file, so that the system can’t read it.

      Provided this isn’t locked down by your administrative staff (that is: if the computer is yours to handle), you should probably begin by opening Disk Utility and verifying + repairing disk permissions on your system disk.

      If this doesn’t solve the problem, a re-install of the operating system might be the quickest way to fix it, per the following article:

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s