Juniper Network Connect fails to load

PS

as a test, I'll try RE-applying the combo 10.8.3 to one of the systems and see if it breaks it again....

Good news Dan. This one kicked my backside, and I was so very upset we didn't see in testing, but the methods just didn't show it until the release delta on one of my systems.

I am going to test more as well to get followup info to Apple. But for now, I'm going out to see some daylight. :)

have a good weekend 🙂

Yuo too. And, if you get the chance, mark as helpful or solved so people can find this more easily. I see other Java related issues too, so hopefully this gets some traction.

Is there an option aside from reinstalling Mountain Lion? If not, after the install are you just staying away from 10.8.3 or does the reinstall do something to make it ok for you to then upgrade to 10.8.3 again? I hope Juniper or Apple step up and fix this.

Hi,

you don't need to re-install Mountain Lion!

It appears it MAY be enough to just re-install - in that order - the Apple Java 6, then the Oracle Java 7 install (as A A P L details in his post!). After that, make sure to renable the plugin (easily done via the javatester he also posted a link to). I was able to recover without re-installing the 10.8.3. update. And, after that, re-applying 10.8.3 did not disable it again.

But, even if you were to do the whole combo update http://support.apple.com/kb/DL1640 - that is NOT re-installing ML -just re-applying the combo (vs delta) update. But again, it seems ok - for me at least - to cut that step completely, and just re-apply java and enable the plugin.

Best

Dan

Will do - and thanks again.

BTW - I tried it a few more times - your instructions are still on the money, but I was able to cut out the re-apply of the 10.8.3 updater, at least on 2 systems, but doing all the other steps. After that, even re-applying 10.8.3 (combo!) did not cause the problem to re-appear.

D

Following the previous page's instructions, you're installing 10.8.3. It works fine, but it's just quirky until you finish the steps. It works great now on all Macs. Must be something about the update, not 10.8.3 itself as I've been testing a long time. None of my test machines exhibited this as I used Juniper almost daily.

So, if you need your Macs fixed, that's it for the moment. Worth the time if you need SSL access, and the update works great otherwise.

Good luck.

Thanks Dan. On two of the instances, I had to do the full install, so I figured as the go-to way to fix, it's worth doing. And a mostly clean OS install never hurts.

I'm sure a better/easier way will be found - ill pick back up Monday. But for now, at least we have options.

Enjoy the rest of the weekend all.

Hi all,

It seems to be enough to go to javatester.org and let it activate java for you 🙂

At least it worked on my wifes machine

Network Connect - the full story?

• Network Connect does use Java for the (optional) Host Checker phase.
• Network Connect (the application) is only 32-bit.
• Java 1.6 is available in both 32-bit and 64-bit versions.
• Java 1.7 for Mac is only available in a 64-bit version.

Therefore if you use Host Checker in Network Connect with Java 1.7 installed it will fail. I have had this confirmed by Juniper, they have no plans to update Network Connect for Mac to be 64-bit compatible.

Safari in Mountain Lion is 64-bit, therefore if you have Java 1.7 installed it can still run the Host Checker successfully, once Host Checker has passed Safari launches Network Connect to make the SSL VPN connection.

I have not yet tried this with 10.8.3, all the above would still apply to 10.8.3 but there may be new issues of course. We are planning to move away from Network Connect - probably to Pulse. Due to the above with Network Connect you have to use and have enabled the web-browser Java plugin in Safari which is the area of greatest concern for potential malware which is why Apple have disabled it a couple of times this year already.

PS. After installing 10.8.3 it might be a good idea to reinstall the latest Oracle Java 1.7 version in case Apple 'downgrade' any of the Java components.

Well, well 😉

To be honest, when we started regression testing I slowly went backwards (first cutting out hte combo 10.8.3 upater re-apply), but haven't had a chance to 'go back' further over the weekend. Interesting!

I wonder then if the glitch is 'simply' disabling the plugin but in a way that turning it on via the browser setting doesn't have the desired effect.

I'll give that a try.

Still veyr thankful for A A P L's posts- rather done a bit more but with perfect results, than not - but in any case, that would be great news.

Cheers

Hi there,

this doesn't sound like a related issue....

Has this been working fine before 10.8.3 or has that been a problem longer?

It almost sounds like you have an issue with split tunnelling, rather than the VPN itself. If your company has split tunneling disabled, and they have restricted outbound routing within the tunnel, you could be limited to your internal network (or even just a vlan). But I am guessing here; There could also be a resolution issue (can you get to google via IP vs name?). If this is happening on more than 1 system I would check with your IT guys just to rule that out.

Best

Yes, I believe that this is on the client side, not related to this udpate.

Before I went the "full Monty" route, I did the other things (obviously, I don't like doing all that to fix a Java plugin) but none of those methods were successful here. So, the way I went was brute-force, "I gotta get this working" route. And that it does. I have bug reports in, and will work that in the background. Other gltiches relating to Java have also been discussed, so hopefully a better, more streamlined fix will be forthcoming.

In the world of Sears, there's Good, Better, and Best. This one is Good, working on finding Best.