Network Connect 6.2.0 - many problems

[cpg118_]

Where do I start!? Upgraded SA2000 OS to 6.2R1 and the Network Connect is very unstable.

1. Several users are getting this error when trying to connect to Network Connect. "nc.windows.app.23791 - The secure gateway denied the connection request from this client." I can log on as a different user on the same PC and it works.

2. Many users are complaining that their sessions keep getting frozen up or disconnected.

3. GINA plug-in was made useless! The NC login screen now comes up AFTER the Windows login screen instead of BEFORE it. The whole reason we implemented the GINA plug-in was to fix password problems for remote users.

Sometimes #1 and #2 are resolvable by uninstalled NC 6.0.0 and NC 6.2.0 clients and then letting NC 6.2.0 reinstall. But sometimes they are not.

Any suggestions? Anyone else have this problem? Should I rollback? Help! Thanks!

[ben_]

Have you got a lab unit or one spare? In this case I'd roll back, and reproduce and fix those issues on a labunit with the JTAC Support, especially because of the GINA problem. But this may also depend of the number of users and their "importance".

Then you could also verify that the automatic update of NC from 6.0R5 to 6.2R1 is working fine.

[jamesdev_]

Likewise we found significant new issues with 6.2R1 - the NC client often freezes when trying to reconnect (eg after an IP change or brief discon), client has to be manually exited and restarted to reestablish the tunnel. We're also still looking in to a new Hostchecker issue where Windows Firewall isn't recognised as active on Vista sp1. No experience with the Gina plugin, we don't use it.

JD.

[flei_]

hallo,

we are also using network connect 6.2 and all our mac users have big problems - sometimes it runes fine, the mac lose his routes (but we are NOT using split tunneling with route change monitor). do you have any ideas? we cannot step back because we use the new citrix feature

thx brgs flei

[RobertN_]

We are having issues also... When users first boot a cold machine and then launch NC, the NC session times out on initiation and we get a "Network Connect session terminated. Do you want to reconnect? error 23712"... The user answers "Yes" and the NC session starts, as expected...

If the user disconnects the NC session and does not reboot the machine, and then relaunches NC...no error is seen...and the connection happens as expected.

Is anyone else seeing this activity? I am not seeing this issue in 6.0r4.

[jamesdev_]

Hmm - I fought with an issue last night on 6.0R3.1 that might be related, also caused a fail to connect, fail to reconnect issue within a few seconds. We were using split tunneling, and one of the networks I identified to tunnel via the VPN (10.6.8/24) was an exact match for the network and mask of the NC IP address provided from a local pool on the IVE - I found an error adding the routes deep in the NC logs. I modified the split tunneling routes to use a supernet that didn't exactly match (eg 10.0.0.0/8) and it all started working fine. Clients were both Vista.

[Touch_]

I am using IVE 6.2R1 on a SA700, it has a problem with Juniper Network Connect too. The Verizon wireless card EV-DO connection get dropped every single time once Network connect launched, after around from 5-30 seconds. SSL VPN authentication is fine, but as long as network connect is launched and stated "connected", the internet connection is dropped. I have tested with other types of connection such as LAN, Wi-Fi, DSL, IVE 6.2R1 works fine.

I am not sure previous IVE is working with Verizon EV-DO. I have been contacting with Juniper, Dell (interface software to use with Verizon built-in card), Verison, but none has a clue.

Juniper should have a lab case to test this out since nowadays people use Verizon EVDO a lot. My company relies on this remote connection for travelling and working at home. I have read Juniper network connect has the same problem with Sprint, AT&T wireless cards as well.

[fresco_]

I was thinking of upgrading from 6.0R6 to 6.2R2.1 since I am having lots of problems with Verizon EDVO cards and Network connect. NC break the Verizon internet connection and wind up with a 23792 error. What is up with that???

[otherold_]

On the Sprint side, this is fixed in the Sprint Smartview app.

Tools->Settings->Rules Engine->Connection Maintenance->Change to Maintain established connection regardless of other network availability.

Verizon may have this too somewhere in setup.

[Cliff_]

Regarding the AirCard issue:

We have discovered that if you turn off the compression used by the Aircard's connection manager software - Network Connect stabilizes.

Sprint was a little different and you will need to use the method the previous posted submitted.

These changes corrected the issue for ATT, Sprint and Verizon cards.

Good luck...

Message Edited by Cliff on 01-30-2009 10:41 AM