java update breaks network connect
The latest Java update has broken my junipe netwrok connect, anyone got any ideas?
iMac, Mac OS X (10.7.3)
The latest Java update has broken my junipe netwrok connect, anyone got any ideas?
iMac, Mac OS X (10.7.3)
Thanks Linc, I have already had a trawl through some of this, but there is very little relating to the very latest update. Given that we are forced to take this update due to the flashback trojan, i can only hope others experience the same problem and a fix can be indetified.
I have tried removing java and starting again etc, but no luck, unfortunately I did not to back up before this.
Thanks
Have you checked that Java is enabled in your browser?
If only it was that easy.....it is enabled
dbrown507 wrote:
The latest Java update has broken my junipe netwrok connect, anyone got any ideas?
Yes. That is a known problem. It has been broken for some time. That last Java version that worked was 1.6.0_26. It is Juniper's bug to fix.
It still works if launched from your VPN web page, if you have such a thing.
great, back to virtualbox. Unless there is a way to roll back java to 1.6.0.26, without a time machine back up...
Unless there is a way to roll back java to 1.6.0.26, without a time machine back up...
Register for a free developer account and then you may be able to get it under Developer Tools. Go to Downloads and Developer Tools. I know I got the 1.6.0.26 this way last fall when there was a conflict with Firefox and the .29.
This worked for me:
http://groups.google.com/group/macenterprise/browse_thread/thread/6368431a9c273a 53
The key is:
"This update also configures the Java web plug-in to disable the automatic
execution of Java applets. Users may re-enable automatic execution of Java
applets using the Java Preferences application. If the Java web plug-in
detects that no applets have been run for an extended period of time it will
again disable Java applets."
AppleInTheD wrote:
This worked for me:
What version of Network Connect do you have? I have heard from some that the most recent version of Network Connect has fixed this bug. I can't verify that because Network Connect is tied very tightly with the gateway. You can't upgrade your client until the gateway upgrades.
7.1.0 (18671)
java update breaks network connect