I've tested both with 7.1R1.1 and 7.1R4 and cannot replicate the issue. I did notice the one of the users experiencing the issue was using a 64-bit version of the Java client. Can you please clarify if you are using a 32-bit or 64-bit version? My test were completed with a 32-bit version.
I've got 7.1R4.1 on an SA6000 cluster, and I've got a couple Mac OS X 10.6.x users reporting this problem after updating Java. Haven't fully characterized the issue yet though.
I've opened case 2011-1116-0448 with JTAC.
Our failure modes are as follows:
1.) Directly launching the Network Connect client results in a crash after login
2.) Firefox users seem to be able to launch Network Connect from the SSL VPN web proxy start page, but then Firefox itself crashes. Some users are also saying that Network Connect doesn't even launch completely.
3.) Safari users seem to generally be able to launch Network Connect from the SSL VPN web proxy start page, but others are also reporting a failure there.
Restoring the following files/directories from backup will fix things:
/System/Library/CoreServices/Java Web Start.app
I've tested the same with a 64-bit Java update 29 and did not have any issues launching from the stand alone nc client. Please start posting if you are seeing the issue with 32-bit or 64-bit Java, version of OS X and NC version.
Our users were by default using 64-bit Java, but I tried 32-bit with no change on my machine.
I've uploaded all the standard Tier 1 log requests to the JTAC case as well.
Can everyone clarify if they are using Host Checker when this issue occurs? I believe I was able to replicate it with host checker enabled. It seems this does not effect end users that do not require a host checker policy.
In either case, the user access log state I pass host checker, but when I launch from the stand alone nc client, it sends me back to the log in page.
Yes, we are using Host Checker for all users. Well, not all users have anything done with the Host Checker results, but since everyone is in the same realm, they all have to run Host Checker.
I believe I have enough information to reproduce the issue easily here. RIght now, it will only effect users who are running host checker and launching from the stand alone client.
If anyone is seeing anything different, please update the thread.