How to Monitor NFS Shares from Windows Server

Many monitoring systems cannot observe NFS storage properly from Windows environments. This guide shows how to monitor NFS shares with NetCrunch using Windows NFS client integration so storage availability and folder activity become visible alongside your infrastructure monitoring.

What is NFS Monitoring?

NFS monitoring is the process of verifying that network file system exports remain accessible and that files within those shares update as expected. Monitoring typically checks share availability, folder growth, file timestamps, and access latency to detect storage outages or stalled processes.

How NFS Monitoring Works in NetCrunch

Many infrastructure environments expose storage through NFS - often from Linux or NAS systems - while monitoring platforms run on Windows. This creates a common visibility gap: Windows-based monitoring tools cannot easily check the availability of NFS shares or the state of folders without additional configuration.

In this architecture, the Windows NFS client acts as a translation layer between the Linux-based NFS server and the Windows monitoring platform.

NetCrunch can monitor NFS shares from a Windows Server using the Windows NFS client and Folder sensors, so storage availability becomes part of your infrastructure monitoring and alerting.

Prerequisites

To monitor NFS shares from a Windows-based monitoring server, Windows must be able to access the NFS export. NetCrunch uses the Windows NFS client to read folder data, which allows the Folder sensor to monitor availability and file activity:

• Windows Server hosting NetCrunch Server.
• Client for NFS feature installed on the Windows Server.
• Network connectivity between the Windows Server and the NFS server.
• NFS share information, including the server's hostname or IP address and the exported share path (e.g., nfs-server:/shared).

Why Monitor NFS Shares

NFS is widely used by NAS systems, Linux servers, and backup appliances to expose shared storage across the network. When these shares become unavailable or stop updating, backup jobs, log pipelines, and data ingestion processes often fail silently. Monitoring NFS shares allows operations teams to detect storage outages, permission problems, and stalled workflows before they impact applications. By integrating NFS monitoring into NetCrunch, storage availability becomes visible alongside the rest of the infrastructure.

Step 1: Install Client for NFS on Windows Server

The Client for NFS feature is essential for enabling NetCrunch to communicate directly with NFS shares. You can install it using either Server Manager or PowerShell.

Option A: Install via Server Manager

1. Open Server Manager by clicking on the Start menu and selecting Server Manager.

2. Add Roles and Features: in Server Manager, click on Add roles and features.

3. Select Installation Type: choose Role-based or feature-based installation and click Next.

4. Select Destination Server: ensure your local server is selected and click Next.

5. Skip Server Roles: click Next without making changes on the Server Roles page.

6. Add Features: scroll through the list of features and check the Client for NFS.

7. Install: click Next, then Install. Wait for the installation to complete and click Close.

Option B: Install via PowerShell

1. Run PowerShell as Administrator: Click Start, type PowerShell. Right-click Windows PowerShell and select Run as administrator.

2. Execute Installation Command: powershell Install-WindowsFeature NFS-Client

3. Verify Installation: After completion, you should see a success message. You can verify by running: powershell Get-WindowsFeature NFS-Client

Step 2: Start and Configure NFS Services

The Windows NFS client relies on the RPC port mapper and NFS client services to communicate with Unix-based NFS servers.

1. Open Services Manager: Press Windows Key + R, type services.msc, and press Enter.

2. Start Required Services: find Client for NFS and RPC Port Mapper. Then, right-click each service and select Start.

3. Set Services to Start Automatically: right-click Client for NFS, select Properties. Then, set Startup type to Automatic, and repeat for RPC Port Mapper.

Step 3: Configure NetCrunch to Monitor the NFS Share

Now that the Client for NFS is installed and running, you can configure NetCrunch to monitor your NFS share. NetCrunch monitors NFS shares using the Folder sensor. When Windows can access the NFS export through the NFS client, the Folder sensor can check folder availability, file count, size changes, and access latency just like it does with SMB shares.

The Folder sensor is commonly used for monitoring backup directories, file ingestion pipelines, and shared storage availability across infrastructure environments.

1. Launch the NetCrunch Console.
2. Add the NFS Server as a Node (if not already added): Click Add Node in the NetCrunch Console. Enter the IP address or hostname of your NFS server. Finally, follow the prompts to add the NFS server to the NetCrunch Network Atlas Tree.
3. Open Node Settings by right-clicking on the NFS server node, select Node Settings.
4. Configure Monitoring Settings: in the Monitoring Settings for the node, go to the Sensors tab, click Add and search for the Folder in the list of sensors.
5. Set Up the Folder Sensor: in the Protocol select Windows.
6. Enter the share using the Windows-accessible path created by the NFS client (for example, \nfs-server\shared). The Windows NFS client exposes the NFS export via a Windows-accessible path, allowing NetCrunch sensors to access it as a network share.
7. Specify the Folder Path to the folder you want to monitor within the share.
8. Save Configuration by clicking Save to apply the sensor settings and clicking OK in the Node Settings window.

Example Monitoring Scenario

A common use case is monitoring backup repositories stored on NFS shares. If the folder size stops growing or the latest file timestamp stops updating, NetCrunch can alert administrators that backups are no longer being written. This often detects backup failures earlier than application-level alerts.

Monitoring Best Practices

Monitor Share Availability

The Folder sensor can alert when the NFS share becomes unavailable or when access fails. This allows storage outages to be detected even when the storage system itself is not directly monitored.

Monitor Folder Growth

Monitoring folder size or file count is useful for detecting backup failures, stalled ingestion pipelines, or log storage growth.

NFS Permission Issues

If the folder sensor cannot read the share, verify that the NFS export allows access from the Windows server IP address. Many NFS servers restrict clients using export rules.

UID Mapping Problems

Some NFS servers rely on UID/GID identity mapping for access control. If the Windows NFS client cannot map identities correctly, folder access may fail even when the share is reachable.

Configuration tips

• Test Access Outside NetCrunch: Before relying on NetCrunch for monitoring, ensure you can access the NFS share from Windows Explorer. Use the format \nfs-server\shared to navigate to the share. If accessible, NetCrunch should also be able to monitor it.

• Check Logs for Errors: If you encounter issues, check the NetCrunch logs for sensor-related errors. Additionally, use the Windows Server Event Viewer to identify any system-level issues.

Troubleshooting

Sensor Errors in NetCrunch

• Verify Sensor Configuration: Ensure that the Share Name and Folder Path are correctly entered in the sensor settings, and that the Protocol is set to Windows.

• Check Network Connectivity: Use ping or Test-NetConnection in PowerShell to verify connectivity to the NFS server.

• Firewall Settings: Make sure that firewalls on both the Windows Server and NFS server allow necessary traffic.

Conclusion

Once configured, NetCrunch treats NFS storage like any other monitored resource — enabling alerts when storage becomes unavailable, folders stop updating, or unexpected growth occurs. This allows NFS-based storage systems to be monitored alongside the rest of the infrastructure, rather than remaining a blind spot. This approach can also be used to monitor NAS shares, Linux file servers, and other storage systems that expose data through NFS.