Support for scanning of network shares?
Hi there. Thank you for your amazing software.
I was trying to use your FIM software on my Windows 10 computer to scan a local network share (my NAS). But somehow I can't get it to work. The share is accessible in Windows via file explorer, net use and drive mappings.
I read your documentation and didn't find anything on this topic. So my first question would be;
- Does your software supports scanning/monitoring files on a network share?
I tried many configurations, but everytime I got the following errors in the log file:
- Could not monitor given path '\192.167.2.6\data\movies\ , description: Input watch path is neither a file nor a directory.
- 2025-10-05T17:46:07.7839 [ERROR] thread 'FIM_HashScanner' panicked at 'called
Result::unwrap()on anErrvalue: Error { depth: 0, inner: Io { path: Some(\192.167.2.6\data\movies\ "), err: Os { code: 1326, kind: Uncategorized, message: "The user name or password is incorrect." } } }': src\hashscanner.rs:44
In the config file I tried the following (everytime restarting the FIMservice after I made the changes):
- Using an UNC path (with and without quotes/escaping slashes): - path: \\192.167.2.6\data\movies\
- Using a driveletter mapping: - path: Z:\data\movies\
- Using Windows symlink from a local folder to the NAS: -path: D:\NasLink\
- Tried using parameters: 'User', 'Username', 'pass', 'password',
- Tried using a username with "domainname\user"
- Tried using quotes around my password since it holds special characters, but also without.
If network drives are supported, what would the config file look like in terms of the path, username and password? I tried many combinations of the above. I could attach the full log file and config file if needed.
I hope to hear from you. Thanks in advance!
Best regards, Timon
Hello @Randaraar
Thanks for reaching us, FIM is not firstly intended for network devices but NAS attached as NFS is a common way of drive so probably it works with minor adjustments. Let me check which kind of changes are required and I will comment here.
Thank you for your quick reply. Amazing if you could take a look if this could be implemented! thank you so much for all your effort!
Hello @Randaraar
Thanks for your patience I set up a full Windows 11 environment with a NFS and SAMBA disks to check each behavior and come with an answer.
Firstly, to scan network storage devices you will need to swap the watcher option from the default one RecommendedWatcher to the PollWatcher you have more information about that here https://documentation.achiefs.com/docs/configuration-file.html#watcher
If you use a simple NFS attached to Windows it won't present any friction to monitor this disk. On the other hand, monitoring SAMBA/SMB disks will present some challenge. It is related to permissions, currently, FIM doesn't implement SAMBA authentication so the way to allow FIM to monitor SMB disk is to remove authentication (It could be done in private and closed environments but not recommended for public ones) After authentication removal I managed to get some events like this:
{"checksum":"033dc562602df38deec6772e9b3c75e3ff58213b0f8573bc238037b43a017c36","detailed_operation":"MODIFY_ANY","file":"\\\\192.168.21.245\\storage\\test.txt.txt","file_size":93,"fpid":6728,"hostname":"DESKTOP-OGSOSI1","id":"3edfdddf-627a-4e69-b9a5-bbf36af00e1f","labels":["Program Files","windows"],"node":"FIM","operation":"WRITE","system":"windows","timestamp":"1760223963593","version":"0.6.1"}
Example path (Not authentication required to browse the folder):
- path: \\192.168.21.245\storage
In some implementations the RecommendedWatcher could work under SMB devices so if Poll doesn't work try to swap to the default one.
From my part I will keep researching on how to include an authentication procedure for SMB devices, thanks for your feedback and stay tuned!
Hi @okynos. Thank you so much for your quick reply! This helps a lot! I will test both methods next week and see how it goes. Thanks!!