FAQ and Troubleshooting the Nodinite File folder Monitoring Agent
This page provides answers and troubleshooting steps for common issues with the Nodinite File folder Monitoring Agent. Learn how to resolve DFS and NFS errors, configure monitoring, and get expert support for seamless integration monitoring.
✅ Step-by-step troubleshooting for DFS and NFS
✅ PowerShell scripts for quick diagnostics and setup
✅ Clear guidance for configuration and access rights
✅ Direct support options for fast resolution
If you have any issues that you cannot solve, contact our Support or send us an email at support@nodinite.com
How do I add File folders to monitor with Nodinite?
Adding any number of File folders to monitor with Nodinite is simple and requires only the proper access rights. Follow the steps detailed in the Configuration user guide.
Info
You must be part of the Administrators Role.
DFS Troubleshooting
If you encounter 2662 error status, you are likely not specifying the DFS root path in the folder Configuration.
Verify DFS Share
Use the PowerShell script below as a template to test the availability and configuration of your DFS Share:
Get-DfsnRoot
Get-DfsnFolder -Path "\\$env:COMPUTERNAME\PublicDFS\SharedDocs"
Install/Setup DFS Share
Use the PowerShell script below as a template to set up a DFS Share on a Windows Server host.
# 1. Install DFS Namespace feature
Install-WindowsFeature FS-DFS-Namespace -IncludeManagementTools
# 2. Create the namespace root folder
$namespaceRootFolder = "C:\DFSRoots\PublicDFS"
New-Item -Path $namespaceRootFolder -ItemType Directory -Force
# 3. SHARE the namespace root folder as "PublicDFS"
New-SmbShare -Name "PublicDFS" -Path $namespaceRootFolder -FullAccess "Everyone"
# 4. Create the DFS namespace (Standalone)
New-DfsnRoot -Path "\\$env:COMPUTERNAME\PublicDFS" -TargetPath $namespaceRootFolder -Type Standalone
# 5. Create a folder inside the namespace target folder
$dfsFolderPath = "$namespaceRootFolder\SharedDocs"
New-Item -Path $dfsFolderPath -ItemType Directory -Force
# 6. Share that folder as well
New-SmbShare -Name "SharedDocs" -Path $dfsFolderPath -FullAccess "Everyone"
# 7. Add DFS folder to the namespace
New-DfsnFolder -Path "\\$env:COMPUTERNAME\PublicDFS\SharedDocs" -TargetPath "\\$env:COMPUTERNAME\SharedDocs"
Your DFS namespace is now available at: \
The physical target is \NODINITE01\SharedDocs
Remove DFS Share
Use the PowerShell script below as a template to remove the DFS Share previously installed:
# Remove DFS Folder
Remove-DfsnFolder -Path "\\$env:COMPUTERNAME\PublicDFS\SharedDocs" -Force -ErrorAction SilentlyContinue
# Remove DFS Namespace
Remove-DfsnRoot -Path "\\$env:COMPUTERNAME\PublicDFS" -Force -ErrorAction SilentlyContinue
# Remove SMB Shares
Remove-SmbShare -Name "SharedDocs" -Force -ErrorAction SilentlyContinue
Remove-SmbShare -Name "PublicDFS" -Force -ErrorAction SilentlyContinue
# Delete all folders
Remove-Item -Path "C:\DFSRoots" -Recurse -Force -ErrorAction SilentlyContinue
NFS Troubleshooting
Note
Usually, this is a problem related to the firewall. Please review the Prerequisites.
For NFS related issues, read more here
If you have problems connecting to the NFS area, follow the steps below to troubleshoot the problem.
Common errors:
Could not connect to NFS, error: ONC/RPC portmap failure
Additional reading: NFS Overview
If possible, install the NFS Client feature:
The NFS Client feature must be installed for NFS monitoring.
Use the sample RPCINFO command (replace sample IP-address as appropriate):
rpcinfo /p 10.0.1.135
If the connection is successful, you should have the nfs entries listed; otherwise, there is probably an error in the output:
RPCINFO output showing NFS entries if successful.