Now that Apple OSX Lion was release yesterday, Wednesday July 20th, 20011, does anyone know which SSL VPN code supports the Lion OS? I have users upgrading their Macs to this OS and are having issues installing the Network Connect client with Firefox. It seems that Safari is the only browser working so far.
Thanks,
John
It looks like Apple Lion is currently not supported in any of the SA OS versions. You could keep watch on KB20841 (http://kb.pulsesecure.net/InfoCenter/index?page=content&id=KB20841_) to track the progress on this support.
It worked for me with 7.1R3, but I had to install Java first after I did a clean install of Lion. Apple no longer includes the JRE in the OS, but it can be downloaded through the Java Preferences utility application.
While not officially supported, multiple reports on Twitter that it's working. YMMV
-Keith
p.s Cisco client...not so much
Safari is the only browser supported on the Mac; Firefox is not supported to use for launching clients, such as Network Connect (or Host Checker or Secure Meeting). If you saw this working before, you are one of maybe 2 or 3 individuals (including you) that have seen this work.
I am glad it was working for you before, but it is not expected nor designed to (which makes it hard when the expected behavior starts occurring).
For the balance of your question, there is no current OS that supports Lion; unofficially, testing looks positive for most items except presenting with secure meeting.
This (failure to launch JSAM) is occurring on Snow Leopard (10.6) as well.
We're seeing JSAM not loading on Snow Leopard 10.6.8 with the recently released Safari 5.1: "This browser does not use the Cocoa Java Plug-in. 1) Make sure that the JVM 1.4.1 or later is installed, 2) Check that this browser supports Java for Cocoa (such as Safari)"
I upgraded my home Mac to Lion (with Safari 5.1) and am getting the same results.
Thank you for the confirmation it is failing with Lion as well.
I have a case open with the Juniper development team to see if it is something we can resolve or if it is an item that Apple will need to fix.
For everyone seeing this issue: Have you opened cases with Apple for this?
I am having the same problem with OS X 10.6.8 and the recent safari 5.1 update from Apple. Who needs to correct this?