How to use dirscan to monitor a shared file system or path
search cancel

How to use dirscan to monitor a shared file system or path


Article ID: 209921


Updated On:


DX Unified Infrastructure Management (Nimsoft / UIM) Unified Infrastructure Management for Mainframe CA Unified Infrastructure Management SaaS (Nimsoft / UIM)


We need to monitor a shared file system\location on the server, can you please let me know if it is possible?

For example-> \\\SXXXXDATA\XYZProfile\"


Release : 9.2.0

Component : UIM - DIRSCAN

dirscan probe - any version


- network share monitoring


It is possible to monitor a shared drive, but on Windows only. Non-Windows remote directories cannot be monitored.

The dirscan probe can successfully monitor shared file systems with the following exceptions:

- You cannot run batch files from a mapped drive using the dirscan probe
- Non-Windows remote directories cannot be monitored

The underlying storage device where the file system is hosted does not matter to the probe.  As long as the probe can access the desired directories/files to be monitored on the shared file system, then it will be able to monitor them.

As long as the dirscan probe is installed on a Windows robot where you can access for example, the "\\Windows_Robot_Server.fully.qualified.domain\XXXX_ACL_NNNNNN\M_TEST\INT\ICC\ABC" shared directory, you should be able to monitor the directory using the dirscan probe.

When you create the dirscan profile and enter the shared directory name in the Directory field on the Scan Directory tab of the New Profile dialogue, you will also be asked to provide the username and password that has the access/permissions required to access the network drive.  Once the correct information is provided and the profile is created, the probe will be able to monitor the network drive.

Fir example, the userid could be the administrator, domain administrator or a service account.

Additional Information

Unable to open network share with dirscan

Note on intermittent alarms being thrown for network shares not found-> Please check network connectivity / latency / DNS timeouts. In the case of DNS timeouts you could try adding an entry for the destination hostname on the source server in the /etc/hosts file.