Support Center > Search Results > SecureKnowledge Details
TCP sessions freeze/disconnect after one hour
Symptoms
  • The below article provides a solution for two different scenarios, one with Remote Access Client and another one with Mobile Access. See the symptoms below and download Take 117 (resolves both scenarios).

  • Remote Access Client connecting over Visitor Mode (443) and not NAT-T (4500) disconnects from site after one hour.

    Help Desk logs from the client show:
    [Date 1:00] Connection was successfully established (1)
    [Date 2:00] No reply from the gw ip=X.X.X.X for tunnel test packet. Office Mode IP=X.X.X.X, source port=18XXX.
    [Date Time] No reply from the gw ip=X.X.X.X for tunnel test packet. Office Mode IP=X.X.X.X, source port=18XXX.
    [Date Time] No reply from the gw ip=X.X.X.X for tunnel test packet. Office Mode IP=X.X.X.X, source port=18XXX.
    [Date Time] No reply from the gw ip=X.X.X.X for tunnel test packet. Office Mode IP=X.X.X.X, source port=18XXX.
    [Date Time] No reply from the gw ip=X.X.X.X for tunnel test packet. Office Mode IP=X.X.X.X, source port=18XXX.
    [Date Time] No reply from the gw ip=X.X.X.X for tunnel test packet. Office Mode IP=X.X.X.X, source port=18XXX.
    [Date Time] IKE tunnel disconnected, error code=-1000. Reason: Site is not responding.
    [Date Time] Client state is connected
    [Date Time] Tunnel (1) disconnected. State is connected. Trying to reconnect.
    [Date Time] Client state is reconnecting
    [Date Time] Reconnect finished successfully (1)
  • TCP sessions such as Remote Desktop Protocol (RDP) freeze and disconnect completely after exactly 60 minutes from the moment they are established, but only via a Web Application or a Citrix Application in Mobile Access Portal.

    Unexpectedly, the time it takes the connection to freeze is affected by the TCP session value at 'Global Properties -> Stateful Inspection -> TCP Session timeout'.
Solution
Note: To view this solution you need to Sign In .