locked
Windows Server 2012 and NFSv4 RRS feed

  • Question

  • Hello,

    I'm trying to run NFS services on Windows Server 2012 with support for version 4 (NFS4), everything I read says 2012 supports v4, however I cannot find anywhere to set the version except for 2 or 3, no options for 4.

    Is it NFS client that only supports v4, and nfs server is only v3?

    Thanks,

    Tom

    Wednesday, September 5, 2012 8:52 PM

Answers

  • Yes, see included image

    • Marked as answer by TJK_VA Monday, September 10, 2012 1:40 PM
    Monday, September 10, 2012 1:20 PM

All replies

  • Hello,

    Thank you for your question.

    I am trying to involve someone familiar with this topic to further look at this issue.

    Regards,


    Arthur Li

    TechNet Community Support

    Monday, September 10, 2012 6:18 AM
  • Hi been there also, seems they have gone to some effort to hide thoose settings.

    Under File and Storage Services -> Service

    Right click the server and choose NFS Settings

    There you can choose what version of nfs to support.


    • Edited by Zaxmy Monday, September 10, 2012 8:18 AM spelling
    Monday, September 10, 2012 8:17 AM
  • Hi,

    I have completed the test on the Windows 2012 server with NPFS.

    You are correct, the NFS client can support not v4 while the server can only support for v2 or v3. This performance is by-design.

    If you have any concern about the design of server 2012, please refer to the explanation article from Microsoft:

    http://technet.microsoft.com/en-us/library/jj592688

    Thanks for your understanding.

    Best Regards,

    Annie

    Monday, September 10, 2012 9:40 AM
  • AnnieGu,

    Thank you, so to confirm, NFSv4 is only supported on the CLIENT SIDE, NFSv4 is NOT SUPPORTED as a server on Windows 2012?

    BTW, the article you linked to says nothing about NFSv4.

    Tom

    Monday, September 10, 2012 12:22 PM
  • Zaxmy,

    Thanks, however have you tried your suggestion, and can you see version 4 as an option, or just 2 and 3?

    Tom

    Monday, September 10, 2012 12:23 PM
  • Yes, see included image

    • Marked as answer by TJK_VA Monday, September 10, 2012 1:40 PM
    Monday, September 10, 2012 1:20 PM
  • Zaxmy,

    You are the MAN!  Thanks!  Another quick question, if I may:

    Can you get a 4.1 mount working from Linux?  I get the below error on latest 6.3 CentOS:

    # mount -t nfs4 -o rw,soft,noatime,nodiratime,intr,tcp 172.16.1.200:/testing /mnt/testing
    mount.nfs4: Protocol not supported

    Not sure if there is something else I need to do to enable 4.1 support on the Linux client?

    Thanks!

    Tom

    Monday, September 10, 2012 1:37 PM
  • Zaxmy,

    I think I answered my own question on 4.1, see below:

    mount -t nfs4 -o rw,soft,noatime,nodiratime,intr,tcp -o minorversion=1 172.16.1.200:/testing /mnt/testing

    172.16.1.200:/testing/ /mnt/testing nfs4 rw,noatime,nodiratime,vers=4,rsize=1048576,wsize=1048576,namlen=255,soft,proto=tcp,port=0,timeo=600,retrans=2,sec=sys,clientaddr=172.16.1.106,minorversion=1,local_lock=none,addr=172.16.1.200 0 0

    Thanks again for your help!

    Tom

    Monday, September 10, 2012 1:40 PM
  • Congrats TJK_VA

    Now if only I can get Ubuntu 12.04 to accept minorversion=1 when mounting i would be a happy bunny also. Dont get it Ubuntu 12.04 ships with nfs-utils-1.2.5 but reading the ubuntu src code now, and cant find that option mentioned anywhere in the source package.

    What version of nfs-utils does CentOS 6.3 ship with ?

    Tuesday, September 11, 2012 2:07 PM
  •  # rpm -qa|grep nfs
    nfs-utils-lib-1.1.5-4.el6.x86_64
    nfs4-acl-tools-0.3.3-6.el6.x86_64
    nfs-utils-1.2.3-26.el6.x86_64

    What error are you seeing in messages or dmesg when the mount fails?

    Tom

    Tuesday, September 11, 2012 3:06 PM
  • Looking for a solution to mount NFS4.1 share created on Windows 2012 System on to Ubuntu 12.04 Client. Getting the below error while mounting. Was also getting the same error on RedHat 6.2, but finally could able to mount successfully with “-o minorversion=1” option. But this option is invalid for Ubuntu. However I am able to mount using NFSv3 , i.e. with “-o vers=3”. Any idea how to mount using NFSv4.1


    # showmount -e 10.1.6.84
    Export list for 10.1.6.84:
    /nfsdata (everyone)
    #
    # mount -t nfs4 10.1.6.84:/nfsdata /nas1 –v
    mount.nfs4: timeout set for Mon Aug 27 16:21:23 2012
    mount.nfs4: trying text-based options 'addr=10.1.6.84,clientaddr=10.1.9.1'
    mount.nfs4: mount(2): Input/output error
    mount.nfs4: mount system call failed
    #
    # mount -t nfs -o vers=3 10.1.6.84:/nfsdata /nas1 -v
    mount.nfs: timeout set for Tue Aug 28 23:50:28 2012
    mount.nfs: trying text-based options 'vers=3,addr=10.1.6.84'
    mount.nfs: prog 100003, trying vers=3, prot=6
    mount.nfs: trying 10.1.6.84 prog 100003 vers 3 prot TCP port 2049
    mount.nfs: prog 100005, trying vers=3, prot=17
    mount.nfs: trying 10.1.6.84 prog 100005 vers 3 prot UDP port 2049
    10.1.6.84:/nfsdata on /nas1 type nfs (rw,vers=3)
    #

    Friday, September 14, 2012 12:20 PM
  • I managed to get NFS 4.1 to work on Ubuntu 12.04, turns out they they have disabled NFS 4.1 kernel support out of the box so had to rebuild the kernel. (Kinda funny when they claimed they supported 4.1 allready in  KarmicKoala 9.10 https://wiki.ubuntu.com/KarmicKoala/HumanReleaseNotes#NFS_4.1_client_support )

    Stock kernel:

    bla@host:/> grep CONFIG_NFS_V4_1 /boot/config-3.2.0-29-generic

    # CONFIG_NFS_V4_1 is not set

    After rebuild:

    bla@host:/> grep CONFIG_NFS_V4_1 /boot/config-3.2.0-29-generic

    CONFIG_NFS_V4_1=y

    After that mount accepts minorversion=1

    SusantaDutta the Input/Output error you see is the server telling you it doesnt support plain version nfs4, if you trace the traffic with tcpdump you will se that the server returns 10021 ( NFS4ERR_MINOR_VERS_MISMATCH | 10021 | Section 15.1.3.2 )

    Tuesday, September 18, 2012 11:59 AM
  • Zaxmy,

    Awesome, thanks for the update.  Let me know how your performance is, mine is horrible.  I'm using 72 SATA HDD's in a mirror with Storage Spaces, mounted to a VMware 5.1 farm - and the best I can get is about 40-45 Mbs on a gig-e.

    If I test Windows 2012 to Windows 2012 file transfers, I can easily fill a gig-e.  I think because VMware is forcing sync-writes, and you can't override that, at least from the VMware side.

    So much for all the hype of Windows 2012 now being a decent platform for VMware using NFS - the performance makes it non-usable.

    Tom

    Tuesday, September 18, 2012 12:02 PM
  • TJK_VA what nfs client version are you using from the VMware side 2,3 or 4.1 ?

    I have no problems filling an gig-e with linear read/write from an Ubuntu 12.04 client to the server running in a vmware esx 5 environment. (nfs v4.1)

    Havent tried random write/read, unpacked the linux-kernel which contains a lot of small files and it used about 25% cpu on the server.

    Johan

    Tuesday, September 18, 2012 2:05 PM
  • Johan,

    I'm using/testing Win2012 as an NFS datastore for VMware, which only supports NFSv3 right now.  So not within a VM Guest, rather at the hypervisor level to store VM's on etc.

    Tom

    Tuesday, September 18, 2012 2:13 PM
  • Johan,

    I'm using/testing Win2012 as an NFS datastore for VMware, which only supports NFSv3 right now.  So not within a VM Guest, rather at the hypervisor level to store VM's on etc.

    Yes understood that, wasnt up-to-date with which nfs version the vmware datastore supported.
    Tuesday, September 18, 2012 2:19 PM
  • Hi Zaxmy,

    Yes, I could able to mount NFS4.1 on Ubuntu Client. after rebuilding the Kernel with “CONFIG_NFS_V4_1=y”, by default this was turned off.

    root@Test-Ubuntu:~# grep _NFS_V4 /boot/config-`uname -r`

    CONFIG_NFS_V4=y

    CONFIG_NFS_V4_1=y

    root@Test-Ubuntu:~#

    root@Test-Ubuntu:~# df -k

    Filesystem     1K-blocks     Used Available Use% Mounted on

    /dev/sda1       45765656 12913472  30527400  30% /

    udev            12264232        4  12264228   1% /dev

    tmpfs            4909876      740   4909136   1% /run

    none                5120        0      5120   0% /run/lock

    none            12274688      144  12274544   1% /run/shm

    root@Test-Ubuntu:~#

    root@Test-Ubuntu:~# showmount -e 10.1.8.34

    Export list for 10.1.8.34:

    /nfstest (everyone)

    root@Test-Ubuntu:~#

    root@Test-Ubuntu:~# mount -t nfs4 -o minorversion=1 10.1.8.34:/nfstest /nas -v

    mount.nfs4: timeout set for Wed Sep 19 10:03:31 2012

    mount.nfs4: trying text-based options 'minorversion=1,addr=10.1.8.34,clientaddr=10.1.10.72'

    10.1.8.34:/nfstest on /nas type nfs4 (rw,minorversion=1)

    root@Test-Ubuntu:~# mount | grep nas

    10.1.8.34:/nfstest on /nas type nfs4 (rw,minorversion=1,addr=10.1.8.34,clientaddr=10.1.10.72)

    root@Test-Ubuntu:~#

    root@Test-Ubuntu:~# df -k

    Filesystem         1K-blocks     Used Available Use% Mounted on

    /dev/sda1           45765656 12913444  30527428  30% /

    udev                12264232        4  12264228   1% /dev

    tmpfs                4909876      740   4909136   1% /run

    none                    5120        0      5120   0% /run/lock

    none                12274688      144  12274544   1% /run/shm

    10.1.8.34:/nfstest 104727552  1156096 103571456   2% /nas

    root@Test-Ubuntu:~#

    root@Test-Ubuntu:~# touch /nas/testfile

    root@Test-Ubuntu:~# ls -l /nas/testfile

    -rw-r--r-- 1 root root 0 Sep 19 10:00 /nas/testfile

    root@Test-Ubuntu:~#

    Commands used to rebuild the Kernel:

    root@Test-Ubuntu:~# sudo apt-get install fakeroot kernel-wedge build-essential makedumpfile kernel-package libncurses5 libncurses5-dev

    root@Test-Ubuntu:~# sudo apt-get build-dep --no-install-recommends linux-image-$(uname -r)

    root@Test-Ubuntu:~# mkdir ~/src

    root@Test-Ubuntu:~# cd ~/src

    root@Test-Ubuntu:~# apt-get source linux-image-$(uname -r)

    root@Test-Ubuntu:~# cd linux-3.2.0

    root@Test-Ubuntu:~# cp -vi /boot/config-`uname -r` .config

    root@Test-Ubuntu:~# vi .config

    Modified the .config file to say "CONFIG_NFS_V4_1=y"

    root@Test-Ubuntu:~# make menuconfig

    root@Test-Ubuntu:~# make-kpkg clean

    root@Test-Ubuntu:~# fakeroot make-kpkg --initrd --append-to-version=-custom kernel-image kernel-headers

    The kernel packages are created in ~/src

    root@Test-Ubuntu:~# cd ~/src

    root@Test-Ubuntu:~# sudo dpkg -i linux-image-3.2.27-custom_3.2.27-custom-10.00.Custom_amd64.deb

    root@Test-Ubuntu:~# sudo dpkg -i linux-headers-3.2.27-custom_3.2.27-custom-10.00.Custom_amd64.deb

    root@Test-Ubuntu:~# sudo update-initramfs -c -k 3.2.27-custom

    root@Test-Ubuntu:~# sudo update-grub

    root@Test-Ubuntu:~# shutdown -r now

    Regards

    Susanta

    • Proposed as answer by Johan Cardel Tuesday, September 25, 2012 3:26 PM
    Wednesday, September 19, 2012 4:53 AM
  • Susanta

    Have you been able to read the ACL (ACE?) entries on files from the Ubuntu client ?

    Tried nfs4_getfacl but with no success, tried mounting with acl option on and off.

    Wednesday, September 19, 2012 5:33 AM
  • I would like to report that this works, after successfully building a new image with the instructions Susanta posted, this is the result:

    jc@reaper:~$ grep _NFS_V4 /boot/config-`uname -r`
    CONFIG_NFS_V4=y
    CONFIG_NFS_V4_1=y

    Now onto testing nfs possibilities.

    Thanks for posting.

    Regards
    Johan C


    jc

    Tuesday, September 25, 2012 3:26 PM
  • I was trying to configure Kerberos authentications for NFS4.1 shares on Ubuntu 12.04.  krb5 and krb5i authentications work fine, but not krb5p. I enabled all three authentications while creating the NFS share on Windows 2012. Am I missing something.

    root@ubuntu:~# cat /etc/*release

    DISTRIB_ID=Ubuntu

    DISTRIB_RELEASE=12.04

    DISTRIB_CODENAME=precise

    DISTRIB_DESCRIPTION="Ubuntu 12.04.1 LTS"

    root@ubuntu:~# uname -a

    Linux ubuntu 3.2.27-custom #1 SMP Wed Sep 19 08:06:30 IST 2012 x86_64 x86_64 x86_64 GNU/Linux

    root@ubuntu:~#

    root@ubuntu:~# mount -t nfs -o minorversion=1,sec=krb5p,proto=tcp NEEL-UPGFS1.cnas.com:/nfsdata /data2 -v

    mount.nfs: timeout set for Sun Sep 30 12:11:17 2012

    mount.nfs: trying text-based options 'minorversion=1,sec=krb5p,proto=tcp,vers=4,addr=10.1.1.20,clientaddr=10.1.10.72'

    mount.nfs: mount(2): Protocol not supported

    mount.nfs: trying text-based options 'minorversion=1,sec=krb5p,proto=tcp,addr=10.1.1.20'

    mount.nfs: prog 100003, trying vers=3, prot=6

    mount.nfs: trying 10.1.1.20 prog 100003 vers 3 prot TCP port 2049

    mount.nfs: prog 100005, trying vers=3, prot=6

    mount.nfs: trying 10.1.1.20 prog 100005 vers 3 prot TCP port 2049

    mount.nfs: mount(2): Input/output error

    mount.nfs: mount system call failed

    root@ubuntu:~#

    root@ubuntu:~#

    root@ubuntu:~# mount -t nfs -o vers=3,sec=krb5p,proto=tcp NEEL-UPGFS1.cnas.com:/nfsdata /data2 -v

    mount.nfs: timeout set for Sun Sep 30 12:12:06 2012

    mount.nfs: trying text-based options 'vers=3,sec=krb5p,proto=tcp,addr=10.1.1.20'

    mount.nfs: prog 100003, trying vers=3, prot=6

    mount.nfs: trying 10.1.1.20 prog 100003 vers 3 prot TCP port 2049

    mount.nfs: prog 100005, trying vers=3, prot=6

    mount.nfs: trying 10.1.1.20 prog 100005 vers 3 prot TCP port 2049

    mount.nfs: mount(2): Input/output error

    mount.nfs: mount system call failed

    root@ubuntu:~#

    root@ubuntu:~#

    root@ubuntu:~# mount -t nfs -o vers=3,sec=krb5i,proto=tcp NEEL-UPGFS1.cnas.com:/nfsdata /data2 -v

    mount.nfs: timeout set for Sun Sep 30 12:13:05 2012

    mount.nfs: trying text-based options 'vers=3,sec=krb5i,proto=tcp,addr=10.1.1.20'

    mount.nfs: prog 100003, trying vers=3, prot=6

    mount.nfs: trying 10.1.1.20 prog 100003 vers 3 prot TCP port 2049

    mount.nfs: prog 100005, trying vers=3, prot=6

    mount.nfs: trying 10.1.1.20 prog 100005 vers 3 prot TCP port 2049

    NEEL-UPGFS1.cnas.com:/nfsdata on /data2 type nfs (rw,vers=3,sec=krb5i,proto=tcp)

    root@ubuntu:~#

    root@ubuntu:~# umount /data2

    root@ubuntu:~#

    root@ubuntu:~# mount -t nfs -o minorversion=1,sec=krb5i,proto=tcp NEEL-UPGFS1.cnas.com:/nfsdata /data2 -v

    mount.nfs: timeout set for Sun Sep 30 12:14:41 2012

    mount.nfs: trying text-based options 'minorversion=1,sec=krb5i,proto=tcp,vers=4,addr=10.1.1.20,clientaddr=10.1.10.72'

    NEEL-UPGFS1.cnas.com:/nfsdata on /data2 type nfs (rw,minorversion=1,sec=krb5i,proto=tcp)

    root@ubuntu:~#

    root@ubuntu:~# umount /data2

    root@ubuntu:~#

    root@ubuntu:~#

    root@ubuntu:~# mount -t nfs4 -o minorversion=1,sec=krb5p,proto=tcp NEEL-UPGFS1.cnas.com:/nfsdata /data2 -v

    mount.nfs4: timeout set for Sun Sep 30 12:11:33 2012

    mount.nfs4: trying text-based options 'minorversion=1,sec=krb5p,proto=tcp,addr=10.1.1.20,clientaddr=10.1.10.72'

    mount.nfs4: mount(2): Protocol not supported

    mount.nfs4: Protocol not supported

    root@ubuntu:~#

    root@ubuntu:~# mount -t nfs4 -o minorversion=1,sec=krb5i,proto=tcp NEEL-UPGFS1.cnas.com:/nfsdata /data2 -v

    mount.nfs4: timeout set for Sun Sep 30 12:12:29 2012

    mount.nfs4: trying text-based options 'minorversion=1,sec=krb5i,proto=tcp,addr=10.1.1.20,clientaddr=10.1.10.72'

    NEEL-UPGFS1.cnas.com:/nfsdata on /data2 type nfs4 (rw,minorversion=1,sec=krb5i,proto=tcp)

    root@ubuntu:~#


    Sunday, September 30, 2012 2:45 PM
  • Sorry to resurrect a old thread, I've been trying to mount in Ubuntu 12.04 a Windows Server 2012 NFS share, so far I'm just making tests and learning what I can.

    These are the config options of the share:
    Remote path: winserv2012:/tstnfs (IP: 192.168.1.101)
    Authentication: Kerberos v5: Krb5, Krb5i, Krb5p ; No server authentication: Allow anonymous access.
    Share Permissions: Host 192.168.1.121, Read/Write, RootAccess Allowed, ANSI encoding.
    NTFS Permissions: All default, except one I added: Everyone, Full Control.
    Management Properties: None enabled.


    root@vm-ub-tst:/home/tst# showmount -e 192.168.1.101 Export list for 192.168.1.101: /tstnfs (everyone)

    root@vm-ub-tst:/home/tst# mount -t nfs -o vers=3,sec=krb5i,proto=tcp 192.168.1.101:/tstnfs nfs -v
    mount.nfs: timeout set for Fri Feb  1 06:14:48 2013
    mount.nfs: trying text-based options 'vers=3,sec=krb5i,proto=tcp,addr=192.168.1.101'
    mount.nfs: prog 100003, trying vers=3, prot=6
    mount.nfs: trying 192.168.1.101 prog 100003 vers 3 prot TCP port 2049
    mount.nfs: prog 100005, trying vers=3, prot=6
    mount.nfs: trying 192.168.1.101 prog 100005 vers 3 prot TCP port 2049
    mount.nfs: mount(2): Permission denied
    mount.nfs: access denied by server while mounting 192.168.1.101:/tstnfs


    Expected, must be something about kerberos, but in the Server logs there's: Mount operation succeeded, Address: 192.168.1.121, Share: /tstnfs

    Alright.


    root@vm-ub-tst:/home/tst# mount -t nfs -o vers=3 192.168.1.101:/tstnfs nfs -v
    mount.nfs: timeout set for Fri Feb  1 06:24:24 2013
    mount.nfs: trying text-based options 'vers=3,addr=192.168.1.101'
    mount.nfs: prog 100003, trying vers=3, prot=6
    mount.nfs: trying 192.168.1.101 prog 100003 vers 3 prot TCP port 2049
    mount.nfs: prog 100005, trying vers=3, prot=17
    mount.nfs: trying 192.168.1.101 prog 100005 vers 3 prot UDP port 2049
    192.168.1.101:/tstnfs on /home/apoc/nfs type nfs (rw,vers=3)
    


    The Server logs the same: Mount operation succeeded. But I still can't access the share:

    root@vm-ub-tst:/home/tst# cd nfs bash: cd: nfs: Permission denied


    So far I'm stumped, and since there's almost no documentation or forum posts about this kind of issue (accessing a Windows server 2012 nfs share in Ubuntu), I'm posting this hoping for some help.


    • Edited by somtaaw Friday, February 1, 2013 6:43 AM
    Friday, February 1, 2013 6:37 AM
  • Sorry to resurrect a old thread, I've been trying to mount in Ubuntu 12.04 a Windows Server 2012 NFS share, so far I'm just making tests and learning what I can.

    These are the config options of the share:
    Remote path: winserv2012:/tstnfs (IP: 192.168.1.101)
    Authentication: Kerberos v5: Krb5, Krb5i, Krb5p ; No server authentication: Allow anonymous access.
    Share Permissions: Host 192.168.1.121, Read/Write, RootAccess Allowed, ANSI encoding.
    NTFS Permissions: All default, except one I added: Everyone, Full Control.
    Management Properties: None enabled.


    root@vm-ub-tst:/home/tst# showmount -e 192.168.1.101 Export list for 192.168.1.101: /tstnfs (everyone)

    root@vm-ub-tst:/home/tst# mount -t nfs -o vers=3,sec=krb5i,proto=tcp 192.168.1.101:/tstnfs nfs -v
    mount.nfs: timeout set for Fri Feb  1 06:14:48 2013
    mount.nfs: trying text-based options 'vers=3,sec=krb5i,proto=tcp,addr=192.168.1.101'
    mount.nfs: prog 100003, trying vers=3, prot=6
    mount.nfs: trying 192.168.1.101 prog 100003 vers 3 prot TCP port 2049
    mount.nfs: prog 100005, trying vers=3, prot=6
    mount.nfs: trying 192.168.1.101 prog 100005 vers 3 prot TCP port 2049
    mount.nfs: mount(2): Permission denied
    mount.nfs: access denied by server while mounting 192.168.1.101:/tstnfs


    Expected, must be something about kerberos, but in the Server logs there's: Mount operation succeeded, Address: 192.168.1.121, Share: /tstnfs

    Alright.


    root@vm-ub-tst:/home/tst# mount -t nfs -o vers=3 192.168.1.101:/tstnfs nfs -v
    mount.nfs: timeout set for Fri Feb  1 06:24:24 2013
    mount.nfs: trying text-based options 'vers=3,addr=192.168.1.101'
    mount.nfs: prog 100003, trying vers=3, prot=6
    mount.nfs: trying 192.168.1.101 prog 100003 vers 3 prot TCP port 2049
    mount.nfs: prog 100005, trying vers=3, prot=17
    mount.nfs: trying 192.168.1.101 prog 100005 vers 3 prot UDP port 2049
    192.168.1.101:/tstnfs on /home/apoc/nfs type nfs (rw,vers=3)
    


    The Server logs the same: Mount operation succeeded. But I still can't access the share:

    root@vm-ub-tst:/home/tst# cd nfs bash: cd: nfs: Permission denied


    So far I'm stumped, and since there's almost no documentation or forum posts about this kind of issue (accessing a Windows server 2012 nfs share in Ubuntu), I'm posting this hoping for some help.


    Using anonymous access like explained above no other setting.

    Error is below:

    SMSuse11VM2:~ # mount -t nfs 10.154.50.18:/testnfs /root/pop
    SMSuse11VM2:~ # cd pop
    SMSuse11VM2:~/pop # ls
    SMSuse11VM2:~/pop # mkdir lllsds
    mkdir: cannot create directory `lllsds': Permission denied

    Able to go to mounted folder

    Able to give the list command.

    But not able to create a File.

    Access information:

    Tried to do it as simple as i can to check. But no luck with the NFS acsess.

    Drop me info to help on the case. indianvb@gmail.com

    Thursday, July 4, 2013 11:17 AM
  • hi there,

    This is in regards of Annie's comment from Monday, September 10, 2012 9:40 AM
    Can I follow up on this please ?

    The wording in Annie's reply left a question.
    I have Windows Server 2012 R2.

    Question: Can I do in that Windows a NFSv4 mount on a remote file system and how would I do that ?

    With the recommendations from TechNet applied I keep getting NFSv3 mounts only:


    thanks a lot
    Rainer W. Himmelsbach


    Wednesday, June 4, 2014 9:42 AM
  • I realize this is probably about five years too late, but in case someone stubles upon it, there is no support for NFSv4 in the NFS Client for Windows regardless if it's a client or server OS. 

    Windows and Windows Server versions

    Windows supports multiple versions ofthe NFS client and server, depending on operating system version and family.

    Operating Systems NFS Server Versions NFS Client Versions
    Windows 7, Windows 8.1, Windows 10 N/A NFSv2, NFSv3
    Windows Server 2008, Windows Server 2008 R2 NFSv2, NFSv3 NFSv2, NFSv3
    Windows Server 2012, Windows Server 2012 R2, Windows Server 2016, Windows Server 2019 NFSv2, NFSv3, NFSv4.1 NFSv2, NFSv3


    Andreas Hultgren<br/> MCTS, MCITP<br/> <a href="http://ahultgren.blogspot.com/">http://ahultgren.blogspot.com/</a>

    Thursday, March 7, 2019 8:41 AM