Network Connect 6.5R1 vs Apple Java Upgrade 1.6.0_17

[Ken-J_]

Our site migrated to IVE code version 6.5R1 in mid-November. This week, two Mac 10.6 (Snow Leopard) users are reporting that they cannot install Network Connect. One of these users is a competent Help Desk staffer who swears that he was able to install Network Connect 6.5R1 after we did our upgrade. Installation terminates with a message "Error occurred while extracting one of the Network Connect components."

Current thought is that Apple upgraded their Java to version 1.6.0_17 on December 3, and this may have broken something in the Network Connect install process. But we are grasping at straws here.

[Mrkool_]

is the user trying to do the installtion using SAfari or do they have the installer and trying to install it as a standalone package?

[EdgeTech_ · Accepted solution]

Same issue. I'm running a pair of Juniper SA 4000 with on firmware 6.5R2. My Mac is running the latest Java Update on Apple Snow Leopard. I had to download the .DMG file from the Juniper appliance and manually install it. The manual install went smoothly and now Network connect works fine.

[Ken-J_]

EdgeTech: Thanks for the confirmation that you have also seen this issue. I can confirm that, for one of our two users at least, the standalone .dmg installer works around the problem.

MrKool: our Mac 10.6 users are failing with browser-based installations. The standalone installer, as mentioned above, works fine.

General whining: To our managers, we look bad. Our shop just installed 6.5R1 in mid-November to support Mac OS 10.6 users, and ONE MONTH LATER we have to tell Mac users that it's back to work-around land again.

I recognize that the product model for Juniper SSL VPN requires that we control the software on our user's PCs. However, this is a political impossibility. Bottom line is that this product is somewhat iffy in our VERY heterogenous and uncontrollable environment. At any time, the OS makers, the browser makers, or the Java folks can roll out a change, and *pfft* there goes the critical SSL VPN tool people are relying on to get their jobs done.

</general whining>

[kohster_]

http://kb.pulsesecure.net/index?page=content&id=kb16134&smlogin=true has the known bug on this.

[kohster_]

JTAC told me that they're putting in new logic to check the JVM version and use the appropriate password in 6.5R3 and 6.4R5.