Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[alexisdog]

Just rebuilt/upgraded the domain client who uses ICE.TCP.PLUS Version 7.10a/32, build 27. The domain has an auto setting to lock the workstation after x minutes of user inactivity (i.e. same user or administrator has to hit CTRL+ALT+DEL to login and unlock session). What is happening is that after the computer locks, when the user logs in again and unlocks the station any previous DejaWin or ICE.TCP client side windows that were open have disappeared. My suspicion is that there is a socket timeout, for the TCP/IP connection or within the client software which is dropping the connection in the within the inactivity time setting of the station locking.

Questions are as follows:

1) In looking at the options under ICE Configuration on the General Tab, under Miscellaneous, there is a Setting called Keep Alive Interval with a logic box following, then says (10 sec, intervals, 0=off). Will this function address this issue?

2) Does this function repeatedly send a keep alive packet after the stated interval or is this an inactivity timeout setting whereby if there is not connection activity during the keep alive interval the connection drops?

3) This option only seems configurable with administrator privileges. Does this have to be set for each user profile that exists on the machine independantly? Is there a central file or registry setting where this can be configured for all users?

[Bob]

Setting the keepalive will likely address your problem.

It's set in the ICETCPPLUS.INI file in the windows directory. If there is a separate windows directory for each user it will need to be added to each. You could just create one file for everyone and copy it to their windows directories if that is the case.

It sends a keepalive every interval you've selected whether there is activity or not.