Setting Inactivity Timeouts on a Remote Server Connection

The D3 Windows File System Interface allows setting inactivity timeouts on remote server connections. When a timeout is set, the client disconnects after being inactive for the designated period of time. Timeouts are set from the D3 Connect tab of the D3 Device Manager (see the D3 System Administration Guide for more information). To suppress the timeout feature, deselect the RPC Inactivity Timeout check box.

NOTE

The disconnection caused by the timeout is transparent to the application. On the client side, the files remain opened. If the file is used after the timeout, the connection is automatically re-established.
When the timeout expires, the file on the remote server is actually closed. This invokes the close trigger if it exists and aborts any pending transactions (on systems that support transactions). Furthermore, if a SELECT is in process on a file when a timeout occurs, the SELECT restarts at the beginning of the file when re-invoked. Therefore, we suggest that you don't use timeouts in situations where transactions or SELECT operations are occurring over extended periods of time.
If your connection is over TCP/IP, the NETSTAT Windows command displays the state as TIME_WAIT for a few minutes after the timeout has expired. This is incidental and should not cause any problems.