05-16-2012 07:10 PM
Ingers wrote:
We have a number of mac OS/X Lion 10.7.4 user complaining that when asked to upgrade Netconnect by IVE 7.1R9 they gets an error: "An error occurred while extracting one of the Network Connect Components".
Is this a known issue, does anyone know of a fix?
is this happening only for users with the latest updates? we have seen in the past Safari updates cause failures.
on the see-thru login detail, as kita said, we are working with apple on this. we have seen some reports that users can tab through the fields successfully (ymmv)
05-16-2012 11:30 PM
05-17-2012 03:02 AM
We're seeing the exact same thing here. I don't think it's confined to a safari only thing. Downgrading 7.1R8 did fix our issues so it does appear to be a R9 issue only.
05-17-2012 12:52 PM
JTAC has reproduced it in house. We're sending as many logs from our users as we can (~/Library/Logs/Juniper Networks/Network Connect and ~/Library/Logs/Java Console.log) so they can confirm a solution.
We also rolled back to 7.1R8 on production since so many people had trouble, but it is looking like this will be licked soon.
Thanks everyone for your help!
05-18-2012 12:13 AM
Many users complaing the same on 10.6:
- Even before and after upgrading to latest software updates
I had to rollback to 7.1r7 to fix this issue.
05-20-2012 01:55 PM
Just noticed the transparancy issue on my OSX and NC. Anyone found a solution ?
05-21-2012 08:47 AM
imanenvoy wrote:
Just noticed the transparancy issue on my OSX and NC. Anyone found a solution ?
Not yet; we are working with Apple on it to determine if it is on the Network Connect-side or Apple-side. (Looks like a good chance on the Apple side as the behavior occurs on both 10.6 and 10.7 clients against multiple versions of the SA software.)
05-23-2012 09:23 AM
Any update on this?
05-23-2012 09:26 AM
The behavior has been identified internally and we are working on a solution.
This impacts only 7.1R9.
For further updates, please open a case with JTAC
05-23-2012 09:31 AM
I'm on 7.1R1.1 and NC 7.1.0(17943) on Mac OSX 10.7.4 Safari 5.1.7.
And I'm seeing the issue.