Some of our end users are complaining that they canÕt reconnect to SA-6500 Gateways when their laptops wake up from Sleep modeÓ or Hibernation mode"; the only way to reconnect is to reboot their PC. Users are stating that our old VPNRemote fat client (non-Juniper) seems to work fine when the PC/laptop wakes up, but not the Juniper Network Connect client. Has anyone else run across this problem. This is starting to become a major issue for us. The SA-6500 active/passive cluster is running 6.5R3.1 currently. Thank you for the help.
I've not encountered this specific problem, but my Win7 (x86-32) system often crashes rather hard when waking up from standby/hibernation. It looks like it's depending on where I've started (HW button or system menu) this mode but I haven't researched this yet. As a workaround, I quit the client (both WSAM and NC have this problem) before putting the system to sleep. What OS are your clients running?
What you might try is forcing one of the two available modes for NC:
- ESP (=IPSEC)
- or NCP/oNCP (=SSL)
for the clients, maybe the problem exists with only one of them. These settings can be found in the NC connection profile. Also, when you use NCP/oNCP for transport, you might try forcing NCP if you are still experiencing problems.
By the way: you really should contact JTAC on this as well (as should I )
Thanks for the help. We always force the user to use ESP mode with the NC client and NC is set to always auto-launch. I have contacted JTAC and cannot get pass tier 1 with this problem. They keep telling me that it is a PC driver issue and that the users need to update their power drivers. The users have done this, but the NC client still seems to fail; however, when they use our older non-Juniper fat VPN client, this client works for them without a problem. I would like to get this in the hands of JTAC tier 2, but JTAC tier 1 has closed my ticket on it. That is why I am wondering if anyone else has seen these similar issues.
my pleasure! I wonder: did you try forcing (o)NCP on these users? If so, did it make any difference?
And are all of them running the same OS? Same build, same x86-32 or x86-64?
You might as well look at the drivers for the network card, maybe all these users are running a specific build that has power handling issues - so, the power component drivers may work fine, but the nic drivers aren't.
Best of luck!
I haven't had any problems with 6.5R3.1 with Windows 7 64-bit and "sleep". I am able to launch Network Connect after coming out of sleep.
I currently have one user who is repoprting this issue. He hibernates his machine after logging out of the Junuper page and Network Connect closes. The next time he tries to connect it failsd, but it does not occur all of the time. Do you happen to know ofa fix?