That’s simply not how our system is set up so that script won’t work for me at all.įortunately after a little more digging I found the makefile blog post. All the examples of juniper vpn setups that use a securID token that I could find used a pin+token in a single field. My work uses an Active Directory user/pass with a securID token. The thing is, both of those only take in a user and a single password. Unfortunately for me he (quite reasonably) uses the NC.jar or ncsvc executable. From everything else I read Mad Scientist’s page is the go-to solution for getting Juniper’s Network Connect to work on linux, even on 64 bit. Mad Scientist’s and a blog from 2009 on makefile. Poking around a little bit I discovered two very informative pages.

Whew, that doc was updated in June, but the Ubuntu they support is from 2009? And only 32 bit? Oh my! Both need to be 32 bit only and Firefox 3.6 and Sun JRE 6 are required. The officially supported Linux platforms as of June 2011 are OpenSuse 11 and Ubuntu 9.10. So, I took a look to see what it would take to get my Arch Linux box on the vpn. We recently changed our network setup so that I would be required to log into the vpn while at work.

My automated command line solution to connecting to a juniper networks vpn that takes a password *and* a securID token on 64 bit Linux.

Juniper network connect software