Categories
How-To

Mount NFS Share in Windows 10

Where is a need, there is a how-to do it for my friends.  Today it’s mounting of a NFS Share via Windows 10

Install the NFS Client (Services for NFS)
The first thing we need to do is install the NFS Client which can be done by following the steps below:

Step 1: Open Programs and Features.

Step 2: Click Turn Windows features on or off.

Step 3: Scroll down and check the option Services for NFS, then click OK

Step 4: Once installed, click Close and exit back to the desktop.

How to Mount an NFS Share
From the Windows Machine, Open the Command Prompt or Power Shell Prompt type the following command:

mount -o anon \\host-ip\nfs-share-name drive-letter:

The share is now mounted and we can access the data by navigating to the X: drive.
To validate your successful mount you can use the following command “mount” to review your connected mount points

 

5 replies on “Mount NFS Share in Windows 10”

Well, there is a little mistake with the command:

There is:
mount -o anon \\host-ip\nfs-share-name drive-letter:

Should be URI with single backslash on the beginning:
mount -o anon \host-ip\nfs-share-name drive-letter:

Otherwise we will get error message:
C:\>mount -o anon \\192.168.0.1\nfs S:
Network Error – 53

Type ‘NET HELPMSG 53’ for more information.

@dawciobiel actually the \\host-ip is correct (double backslash).

mount /?
Usage: mount [-o options] [-u:username] [-p:]

The error 53 means ‘path not found’ which can occur if the hostname isn’t registered in DNS, or in the case of using an IP address, if the NFS server isn’t set up properly or is unreachable.

“mount -o anon \\host\sharename t:” is just fine, but note:
1. Must be issued in cmd.exe (Powershell chokes on “-o” param)
2. Target share must be valid — I saw the error #53 on attempting to mount an SMB share (oops)

Most likely the NFS host is a Linux computer somewhere. Make sure its firewall allows for NFS clients from the subnet containing the Windows 10 machines, which could be either in the internal IP address range, the WiFi address range, or the VPN address range. Otherwise you’ll see the error #53.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.