While the Client is programed to release the session for the connection after each file is searched, some NAS devices do not release the sessions as instructed. With the version 10.5.2 and above Client and Console you can limit the number of sessions opened and force close all of them at the end of a search if you wish. The latest versions are now available in your customer portal.
Following are the new settings that require the latest Console and Client and the details of each of these settings:
When searching remote machines, the endpoint will create connections to those resources. If there is a sufficient connection available when the application is started, that connection will be used. By default, the application will not close that connection. To close existing connections, set the desired value:
0: Existing connections will not be closed
1: If the search is run as localsystem, close any existing connections used by the endpoint
2: If the search is run as a user, close any existing connections used by the endpoint
3: Close all existing connections used by the endpoint, regardless of user context
When remote file locations are searched, file handles are opened by the endpoint and after the text from the file has been extracted, the endpoint requests that the operating system release the file handle. If there are delays in closing file handles and new file handles continue to be opened, the remote system can become unresponsive. To enable tracking of remote sessions, set this to Enable (1)
As part of a search of remote machines specified in the Remote Computer List (RCL), connections are repeatedly opened and closed as necessary. Under normal circumstances, all connections will be closed by the operating system after a request from the endpoint. In certain circumstances, it is possible that the operating system will not close remote sessions in a timely manner. In these cases, it is possible to forcibly close each session when the endpoint application is closed. For each remote resource specified in the RCL, for the corresponding user specified for that connection - all sessions created by that user to that resource (including any connections for that user to the resource created outside of Spirion) will be termined.
When remote file locations are searched, file handles are opened by the endpoint and after the text from the file has been extracted, the endpoint requests that the operating system release the file handle. If there are delays in closing file handles and new file handles continue to be opened, the remote system can become unresponsive. By default, the maximum number of remote sessions that will be opened is 100. If the MaxSessionCount is reached, the endpoint will wait up to the SessionCloseDelay minutes for the number of sessions to decrease before opening new sessions. To allow a greater or fewer number of open handles, change this setting. To allow a longer or shorter delay, change the SessionCloseDelay setting.
When MaxSessionCount is reached, indicating that the maximum number of allowable concurrent sessions to a remote system have been opened, the endpoint will wait the specified number of minutes before moving on to the next file to search. If the SessionCloseDelay is reached 5 times without the session count dropping below MaxSessionCount, no additional files on that remote system will be searched. To allow a longer or shorter delay, change this setting to the desired number of minutes.
Searching DFS Shares:
How to Persistently Mount a FTP/SFTP folder in Linux for searching