Juniper Network Connect fails to load

I was lucky enough today to be able to fix this twice with just loading this site (as in the previous poster).

http://javatester.org

Make the main window in Safari small enough to just see the center portion where the plugin info is - this makes seeing the popups easier.
Click the test and the "allow this app to run" popup(s) should appear. Click OK, and the "never ask again" portions and then reload the test page. You should see the correct running Java version and then be able to load the SSL gateway.

If this doesn't work, then utilize the previous steps which include the installers for 10.8.3 and both Java packages.

The Javatester thing worked here once I clicked the "inactive plugin" text. That seemed to enable Java in Safari again. I can't imagine re-installing 10.8.3 from scratch. The update also broke my Facetime settings (had to be logged in with password again). Who knows what else was altered.... I've seen no noticeable improvements with 10.8.3 yet either (I suppose it's nice that people can directly install Windows 8 now if needed with BootCamp).

Reinstalling the OS is simple, and does not make any changes to your data. The worst that happens is that you need to reinstall some updates again - like iTunes, Java, etc. It can also fix issues if you're having them - and it sounds like you are.

No, it's a waste of bandwidth and time in this case as there's a simple 5 second solution. It reminds me of the Windows re-install Win98 over top of itself all the time crap. This is UNIX. There are nearly always better solutions than start from scratch.

After running into this twice now, the only thing one needs to do is go to http://www.java.com/en/download/testjava.jsp and it will say "disabled plugin" where the Java test should show up in Safari. Clicking in preferences to disable and reenable Java, for example won't do a thing to enable it (although it does have to be "on" there regardless). Clicking on the words disabled plugin on that web page will make it work again. Simple problem solved with a simple 5 second solution.

The alternative here is potentially waiting an hour+ to download Mountain Lion again (which you cannot even do from the App store if you bought a new Mac with Mountain Lion already installed; the App store will not show it as purchased; you have to use the restore partition instead; I only have it purchased because I bought an upgrade later for my MBP; that one will allow it to be installed on any Mac). But WHY ON EARTH would you do that when it's just a disabled plugin??? It's like fixing a crack in a wall in a building by tearing the entire building down and re-building the entire thing rather than just fixing the crack. Even if that building can be rebuilt in an hour, I'd take a 5 second solution over that any day. This is a non-issue problem that has a simple solution and that is the ONLY solution that should be presented as brute force is just a waste of time and only further propagates operating system ignorance rather than finding the true cause of the problem (which is a small bug in Apple Safari's internal settings). Sure if that's the only tool in your toolbox and you have a problem it might fix it, but once a better solution has presented itself, that's the way to go.

Facetime resetting its password settings described above was probably due to an internal update of either it or keychain and it would do it again if I updated the whole thing from scratch. Once again, it doesn't call for starting over, just filling in the password again. The only thing that made it look weird is it was past that point when it started itself up. You have to click BACK to the previous page and enter the password and then forward. Otherwise, the "next" button won't do anything and it won't give any feedback as to why not. Once again, Apple has made a two-bit application with Facetime (other bugs include "sticking frames" with some web cameras, an inability to transmit many sounds other than voices over the Net like music which simply gets garbled or muted instead and no ability to do conference meetings, etc. I see no efforts on Apple's part to improve it either. They think it's good enough for iOS and the Mac version is just an apparent after-thought, it seems. There is no Windows or Linux version and so you're limited whom you can conference with anyway. Despite all Skype's problems, it's still the best choice between platforms and has none of those issues (although it does crash sometimes and uses a lot more CPU time for HD video).

Looks like this all broke CrashPlan. I fixed it easily on my rMBP but not my iMac. Errr!

This thread has been extremly helpful, but I am still not up and running.

I was working fine, until one day somethign updated and now network connect doesn't work at all.

I am running an iMac with Mountain Lion, and followed your advice to reinstall a full 10.0.8 and the 2 mentioned Java.

When i run Network Connect, it runs, but terminates with a nc.mac.app.1203.

I have searched the entire internet, and no one seems to know what to do.

Any thoughts?

I have this same problem. Simply does not work in Safari, starting with 10.8.3.

However, using Firefox it works fine for me (and connects faster than it ever did) under 10.8.3.

Do both version of Java need to show in Java tester? No matter what I do, 1.6 doesn't show.

I had problems with the lastest updates of OSX (I am currently using 10.8.3). After trying everything I have found a way to make Juniper network connect working. In my case the problem was that the language used on my Mac was set to Italian. I changed to english, logged out, logged in and, magically, everything worked again. Just as a test I have changed the language again to Italian, logged out and in and Network Connect did not load. So in my case setting to English the language for my Mac solved the problem.

In all of this anyone noticed that you were being served up the power pc version of NC on the Intel request?

How would you know the difference?

Switch on the Java console log you will this under, hmmm, safari vii, maverickz, hmmm..

Mind you it works under Firefox...

Let's all just agree that Juniper is a terrible company with no customer service. They should be on top of this, not making customers twist in the wind.

No, it does not.