Windows 10 Nfs Client
Posted : admin On 13.08.2019I decided to give NFS a shot, since it was simple, higher performance (in theory) and easy to get going. I am using Windows 10 Pro 64-bit for my NFS client. I do not know if all editions of Windows 10 support NFS, I imagine “Home” probably does not. I'm trying to mount a share from My Cloud to Windows 10 Ultimate using NFS. I've enabled NFS in Windows 10, but I can't seem to mount. I keep getting invalid UN and PW. What's the best way to do this from a Windows 10. NFS's client from windows have finally been updated for Windows 10 PRO. So with your latest windows 10 PRO 14393.576, your NFS's client is finally operational in comparison with before like shown in this thread: as stated before by Tom jolly Tom Jolly (Group Software Engineering Manager) in the same thread, they were working on a fix because of problems with the transition from Windows.
We had two NFS shares that we needed to allow windows user's to connect (if it was possible) after some hassle it was.
This is specifically for a machine that is not on an active directory domain or if you do not want to set up the AD identity service.
I have tested this functionality in Windows 7 SP1, Windows 8.1 and Windows 10 Anniversary edition.
** All OSes tested were enterprise edition. i believe all versions of 8 and 10 have this available but win 7 is enterprise only **
10 Steps total
Step 1: Go to windows add or remove features
Step 2: Under Services for NFS click on NFS Client for Windows
Step 3: Once the package installs follow these instructions
Find your linux UID and GID by typing the following on your linux server.
Id -USERNAME
this will print your uid and gid
Step 4: Once you have this information you will need to add/modify two registry keys:
*** Alternative Copy after this line to a text file and name it with a .reg extension and run it.***
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINESOFTWAREMicrosoftClientForNFSCurrentVersionDefault]
'AnonymousGid'=dword:00000000
'AnonymousUid'=dword:00000000
Step 5: Make sure to edit the IDs before importing
This binary calculator can help convert a decimal number (the number you got from the id command) to hexadecimal which is the format the is required for the windows registry key.
http://www.binaryhexconverter.com/decimal-to-hex-converter
Nfs Client For Windows
Alternatively, you can run or add the registry keys above by navigating to the location mentioned in the windows registry, when editing the registry key, make sure the decimal radio button is checked.
Step 6: Reboot!!
Yes i mean it, if not your NFS Client wills till use the old Anonymous IDs and will not allow you to connect if you dont allow anonymous connections
Step 7: Mounting NFS Share:
This step and forward is just instructions on mounting the share as it should now be accessible.
Step 8: Run a windows command prompt window.
Step 9: Type the following
mount -o nolock share:/SHAREPATH {desired drive letter}
Step 10: If you are mounting to the root of the share location, type in
Mount -o nolock share:/! {desired drive letter}
it is very important to put the ! As the connection will not work without it.
Windows 10 Nfs Server Reddit
10 Comments
- CayenneSBS0518 Nov 4, 2016 at 07:20pm
I'm on 7, SP1 but the NFS option isn't listed.
- SerranoXylems92 Nov 4, 2016 at 08:07pm
Ill attach a screen shot of what it looks like and the version of windows 7 i am running.
- SerranoJM0176 Nov 4, 2016 at 08:08pm
its pretty straight forward i'm not a huge linux user myself only our guys who code really use linux. But its cool to know if we need to access and of our servers this way.
- SerranoXylems92 Nov 4, 2016 at 08:11pm
SBS0518: As far as the screen shot ill just leave it out. I changed the wording the options is not called NFS services its called Services for NFS so alphabetically look for S not N.
The version of windows i am testing this on is : Windows 7 SP 1 Ver 6.1.7601
- SerranoJoshScott9 Nov 4, 2016 at 08:50pm
You need Windows 7 Enterprise for NFS Client. They took it out of Windows 7 Pro. Or else you can use a third-party option.
- Serranojorgealdana Nov 4, 2016 at 08:54pm
SBS0518, You need the Enterprise version of Win7 to have the NFS features, Pro does not have it.
- SerranoXylems92 Nov 4, 2016 at 08:57pm
Well there you have it. i never looked because we use enterprise here
- Jalapenogunnermike53 Nov 4, 2016 at 08:59pm
I'm a little confuse. Why wouldn't you just map a drive
ip addressshare folder
UN: domainusername
PW: whatever - Macebbigford Nov 4, 2016 at 10:25pm
@mchance2, you're thinking of SMB (Server Message Block). That's for windows. NFS (Network File System) is what *nix uses primarily. If you try to connect to a *nix share the way you're suggesting, it won't work.
- JalapenoMassT Nov 7, 2016 at 09:50pm
What there is an NFS client in Windows! Thank you very much for info.
sleeper52
Newbie
I've been reading that NFS has some performance advantages over SMB.
I was successfully able to create a NFS share on a dataset named 'NFS.TEST'
NFS Services (AdministrativeTools and ClientforNFS) has been enabled in Control Panel.
On HKEY_LOCAL_MACHINESOFTWAREMicrosoftClientForNFSCurrentVersionDefault I have created the appropriate New DWORD (32-bit) Value for AnonymousUid and AnonymousGid (In my case it is 1001 for Uid and Gid)
On CMD, I have entered the following command to mount/map the NFS share:
>mount -o nolock,anon,fileaccess=7,mtype=hard NASGULmntVolume2NFS.TEST *
I am able to create, delete, modify files on the NFS share fine on the Windows 10 client.
My issue is the performance as I have tested the NFS share compared to the SMB share using CrystalDiskMark 6.0.2 x64 and I am producing significantly lower performance on the former.
NOTE: Left is SMB. Right is NFS.
The Windows 10 client is using updated Windows 10 Pro x64 running on Ryzen 5 2400G with 16GB DDR4 RAM on a wired CAT 5e connection.
Any idea why the performance is slow and how I can correct this?