Looking for recent stable IVE firmware for Network Connect

[Ken-J_]

I'm trying to pick our next upgrade for the IVE firmware. We are currently on 6.0R2.

Network Connect is the only feature we use, so stability for loading and launching NC is paramount.

I'm unclear on the distinction between the 6.0 train, the 6.1 train and the 6.2 train. (We'd probably avoid 6.3 as Too New, and we don't need the new management features.)

I note message #7352 contained a report of a site that backed out of 6.2R2.1 back to a 6.1 version where they had been stable.

Suggestions welcomed, thanks!

[ScottW_]

Well, are you having issues with NC now? If not, I don't see any real reason to upgrade until 6.0R2 becomes EOS. I'd suggest having your Juniper SE go over the changes and benefits of moving to a different service package. Just remember, if it ain't broke, dont fix it!

[ssl_boy_]

Hi,

We're using 6.2r2.1 for network connect with no ill-effects at several sites, however no matter how much opinion you garner, it'll never be a substitute for testing it in your environment with your PCs. Bearing in mind that the 2000-6500 (at the moment!) all run the same code and Juniper do special "lab unit" pricing which means that you can get a test setup for not much at all. This is the only way you're ever gonna reliable and relevant information about how it's gonna work in your environment, anything else is going to be 2nd hand guess work. If you're that worried, talk to your reseller and get a quote!

HTH

Kendal

Message Edited by KendalBeefcake on 09-26-2008 03:34 AM

[Ken-J_]

scott w: the issue, only mildly annoying but we want to fix it, is the hang on launching NC from Firefox, where the user has to back up and enter credentials a second time.

kendall: we have a lab unit, thanks, I'm trying to get a handle on what to load into it. Unfortunately, "testing with our own PCs" is only going to give us a partial answer, because our users are an exceptionally heterogenous bunch -- we don't control the end user computers. (University environment.)

Thanks guys, I will also approach the SE and ask for input.

[ScottW_]

---

@ken-J wrote:

scott w: the issue, only mildly annoying but we want to fix it, is the hang on launching NC from Firefox, where the user has to back up and enter credentials a second time.

---

Ken,

We are also experiencing that same issue. I'm assuming they are mostly Firefox 3.0 users. Firefox 3.0 isn't supported until 6.2R2 or 6.3R1. We're holding off on upgrading until we get the cycles to do so. Until then, we told our users to either not upgrade to Firefox 3 or just use IE.

[Ken-J_]

Scott -- relying on our trouble ticket log, it records that we started encountering the "hang-after-signon" problem with Firefox 2.0.0.10 in Dec. 2007, well before Firefox 3 was available. Firefox pushed out a security fix involving Java Archives, and that's what tripped up the Network Connect launch process.

I just got crabbed at in the hall today about the Firefox/Network Connect problem, so we really ought to roll out the fix. Again, in our site we do not get to control our user machines, so we kinda have to stay fairly current with the product.