Network and Storage Protocols

How do I mount an NFS share on Windows 2008 R2




I am attempting to mount an NFS share on a Windows machine.  As I understand it, Win2k8 supports NFS.  Based on a post from 2008, it seems I somehow need to map a user to root, howerver, it does not appear that the username mapping service is supported anylonger.  I followed the instructions in this post  "NFS Mounts with Windows hosts" however, I'm not sure the instructions "Services for NFS Step-by-Step Guide for Windows Server 2008" apply as it seems to want an entirely different NFS client to be installed, also in step 4 of the section "Configuration for Anonymous NFS access:" the policy "access: Let Everyone permissions apply to anonymous users." does not exist, so I'm unable to follow these instructions.  This article indicates you can configure user mapping, if your NFS server is connected to AD (it is not and we do not have any plans to hook our NetApp device up to AD).  The Windows server is connected to our AD infrastructure.


I have exported the share to the full /24.


I do know that the share is active and mountable from a linux server:


[root@foobar ~]# mount on /netappshare type nfs (rw,addr=
[root@showmount ~]# showmount -e
Export list for
/ (everyone)

(interestingly, showmount doesn't show any exports... but it does mount so I'm not sure if that means anything...)


However, when I attempt to mount the same share on my windows server, I get the everhelpful "network path was not found":


C:\Users\domainadmin>showmount -e
Exports list on
/                                  All Machines
C:\Users\domainadmin>mount *
Network Error - 53

Type 'NET HELPMSG 53' for more information.

C:\Users\domainadmin>net helpmsg 53

The network path was not found.

I'm sure it's a PEBCK error, but I'm just not sure where to go from here... it seems like mounting an NFS share should be relatively straightforward so I'm probably missing something obvious.


I'd appreciate any ideas as I'm stumped.





I assume you are using C-Mode. Windows NFSv3 clients are supported starting with cDOT 8.2.3 and require explicit SVM configuration. See 8.2.3 release notes for details.


I believe this is the document being referred to


Is there no way to enable NFS via ONCOMMAND?


What do these commands do?  What is ejukebox and what are the implications of disabling connection drop?


These instructions are concerning without any kind of explanation as to what these commands do.


How did you know NFS instructions were buried in the Release notes?  Seems like a rather obscure place to hide information like this.  Thanks for the tip!


EDIT:  The Documentation for the vserver nfs modify command does not clear this up at all either:


[-enable-ejukebox {true|false}] - Enable NFSv3 EJUKEBOX error (privilege: advanced)

This optional parameter specifies whether EJUKEBOX errors are enabled for NFSv3. The default setting is true at the time of creation.

[-v3-connection-drop {enabled|disabled}] - Enable the Dropping of a Connection When an NFSv3 Request is Dropped (privilege: advanced)

This optional parameter specifies whether NFS v3 connection drop is enabled. The default setting is enabled at the time of creation.
Unfortunately it seems these instructions don't work either:
nacluster::> vserver nfs modify -vserver WinNFSTestSVM -v3-ms-dos-client enabled

Error: invalid argument "-v3-ms-dos-client"

nacluster::> vserver nfs modify -vserver WinNFSTestSVM -enable-ejukebox false -v3-connection-drop disabled

Error: invalid argument "-enable-ejukebox"

So I guess the answer is NetApp doesn't support NFS on windows?  (Admittedly I don't know what version of cDOT I'm on, so maybe it's just too old...  but based on the posts from 2008 and 2010 I would think I should be able to get NFS working...)


These are advanced level options. You need "set -privilege advanced" before.





If you can post an update will be really helpful.




>> Hello 










Thanks jon_.


I guess I will have to wait for 8.2.3 to do some tests also.


Any updates on this?

In the meantime 8.3.1 is out and there NFS mounts with Windows are supported.