On our SA-6500 gateways, many of our users are complaining about sporadic disconnects when using the Windows and Mac NC client; our environment is composed of Win XP and Snow Leopard. The usersÕ NC tunnels do not show an error message when the tunnel disconnect happens, the NC client just states reconnecting and then after a minute or two the NC client reconnects. We have 1gb/s Internet links (utilization is currently at 140Mb/s), no network errors on the SA-6500sÕ or switchesÕ interfaces, the max session on the user role is set to 8000 and the idle time is set to 7000, we have roaming turned on and we have the session counters disabled (JTAC Tier 2 states enabling sessions counters on a role is a problem in 6.5Rx code). I have a ticket in for this issue, but tier 2 support is scratching their head over this. I have also upgraded our SA-6000 test units to 6.5R2 and 6.5R3.1, but I, along with other users, still see the same problem. I was wondering if anyone else has run across this problem and might know how to fix it. Thank you.
We are observing the same issue in our infrastructure as well. Would be great if JTAC finds a quick fix.
..we have the same problem. The NC disconnects after (about) 51 secondes. The users are getting no error messages and in the juniper log we also can«t find any hint for this problem (only the message: Closed connection to TUN-VPN port 443 after 51 seconds, with 196 bytes read (in 1 chunks) and 2318 bytes written (in 23 chunks). But some users can work in this role. Now we use the version 6.5R3.1. With 6.4R2 we don«t have this problem, have any one a fix for this problem?
We're having a disconnect issue as well, but we are currently in an Active/Active deployment with load balancing in front of SA6500's. We're on 6.5r3.1, and are using Radware load balancers to NAT traffic into our network. So this may or may not be related.
We see disconnections after one minute when using ESP, pure SSL is fine. Network Traces show a FIN-ACK being sent from the client address to the IVE, and the session will disconnect and fail to reconnect.
Are you doing split tunneling? We had the same issue(s) and it was related to no split tunneling.
The first user stated he think there's a problem with Session Counter enable but waiting for TAC to update him.
I am ttryin to find out from the Support Account Manager what kind of problem this coudl cause. Could it caused the NC to disconnect. I have Session Counter enalbed. maybe i need to turn it off. Some of my user disconnect after a few minutes with similar syslog messages as other person added.
Juniper employees: Could you guys find out about the Session Counter potential problem? What are the problems?
Do you guys also see a message " System Process detect a Host Checker time out on host xx.x.x..x for user "xyz" ?
This message is before the Close connection message.
We finally got our issue resolved. We had tweaked our NCP for the 6.1 code. JTAC tier two stated that engineering recommended using NCP at 120 minutes for the idle timeout and set the IKE lifetime in the NC Connection Profile to 110 minutes. Since doing this we no longer have disconnects.
...thank you for the hint with no split tunneling, we changed the role settings from "disable split tunneling" to "allow access to local subnet" and now it seems to work for all our users without disconnects.