Yes. If Samba is installed running on the Linux/UNIX system, then our tools can access a share on this system using its UNC name, e.g. '\\ComputerName\ShareName'.
If the file system on the Linux/UNIX system is accessible through NFS, then it can be accessed if the NFS support for Windows is installed. Please go to the Control Panel and activate the 'Services for NFS' under 'Programs and Features > Turn Windows Features on or off'. Then you can mount an NFS share to a drive letter using this command:
mount \\ComputerName\ShareName N:
It might be necessary that you create the following registry values if you have trouble connecting the NFS drive:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ClientForNFS\CurrentVersion\Default\AnonymousUid as DWORD with the decimal value 10011.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ClientForNFS\CurrentVersion\Default\AnonymousGid as DWORD with the decimal value 10012.
SpaceObServer can also scan Linux and Unix shares using SSH.
Since Windows 2008 Server and Windows Vista, Microsoft uses 'Client Caches' in order to speed up the queries about gathering file and directory meta information on network drives. This approach also helps to utilize the available network bandwidth more efficiently. Anyway, these caches always return an incorrect value for the NTFS hardlinks (always shown as '1').
Caches can be disabled by the following steps:
1. Run 'regedit'
2. Open the path 'HKEY_LOCAL_MACHINE\System\CurrentControlSet\services\Lanmanworkstation\Parameters'.
3. Choose "New > DWORD value" in the right click menu and set the name to 'FileInfoCacheLifetime' and the value to '0'.
4. Save the registry and quit 'regedit'.
After these steps SpaceObServer should work properly with hardlinks. For further information about the subject please visit the Microsoft Website.
Note: In case a file has been recently opened, the number of hardlinks will be shown as 1. After a few seconds the value will be shown correctly again.
The problem is most likely the user account you are using for the 'SpaceObServer Service'. If you are trying to scan a Novell Netware server the user account of the scan service has to exists in both, the 'Microsoft Active Directory' and the 'iDirectory' (Novell Directory Services).