|Subject||Connection timing out between iAgent to iServer or iManager to iServer|
|Rating||0% rating out of 0 vote(s).|
|Navigation||Previous - Next - iTivity Remote Support Software - DoubleVision TTY Terminal Remote Control|
Connection timing out between iAgent to iServer or iManager to iServer
Also for the mirror side of the connection, that is the iAgent, below are the contents of the FAQ which suggest how to better configure the iAgent to stay connected as best as possible. The general idea is to increase the keep alive packets so that the local firewall/router does not close the connection after a long period of inactivity.
Some iAgents unavailable, continually reconnect or disconnect after no activity
By default, the iTivity iAgents send a very small keep-alive packet every 90 seconds. This is very useful to prevent the local firewall/NAT device from timing out the permanent connection to the iServer. However, some firewalls have a session timeout that is even shorter than 90 seconds. If you experience an iAgent that continually connects and disconnects from your iServer, then likely that iAgent is behind a firewall with a very low session timeout.
You can set the iAgent keep-alive packet interval to a lower value of 15 seconds in the iAgent settings. This causes somewhat more network traffic, but resolves the continual connect and disconnect problem in almost all cases. As long as this change is applied selectively to iAgents that need a lower keep-alive interval, you are very unlikely to notice any issue with the extra bandwidth consumed.
Some suggested values are given here. The individual values are explained below.
iTivity Unattended iAgent on Unix and Linux
The linux/unix iAgent settings are found the configuration file.
Please insert or update these settings:
On a Windows iAgent, the corresponding registry settings are.
iTivity Unattended iAgent on Windows
iTivity Attended iAgent on Windows
Application Keep Alive Packets
The "iasVerifySessionTimeout" setting controls the application data keep alive resend period over the iAgent to iServer connection from the iAgent side. This value is specified in seconds. Application keep alive packets are not sent when session verification is disabled ("iasVerifySessionFlag" = 0). Otherwise a packet is sent after the specified timeout occurs with no other traffic on the connection.
The "directVerifySessionTimeout" setting controls the application data keep alive resend period over the iManager to iAgent connection from the iAgent side. This value is specified in seconds. Application keep alive packets are not sent when session verification is disabled ("directVerifySessionFlag" = 0). Otherwise a packet is sent after the specified timeout occurs with no other traffic on the connection.
These are the low-level TCP connection settings. The TCP network connection timeout, "transportTimeout", is configured in milliseconds. By default in the iAgent components, the TCP timeout defaults to 90000 or 90 seconds. The "endToEndKeepAlive" flags simply enables, "1", or disables, "0" the TCP connection level keep alive.
You may encounter the following error dialog in the iManager when keep alive activity is insufficient for the local firewall/NAT at the iAgent location.
(X) Failed to establish iTivity Unattended iAgent connection..
iTivity Unattended iAgent unrecoverable encryption error -1304, in tunnelOnceSSLClient.