In this article, you will learn-
- 1 Install and Configure NFS Client on Windows 10/Server 2019
- 2 Introduction
- 3 Stage 1: Server Manager
- 4 Stage 2: Role-based
- 5 Stage 3: Choose Server
- 6 Stage 4: Select Server Roles
- 7 Stage 5: FeaturesIn this “Select features” page, check the “Client for NFS” box and snap “Next”.
- 8 Stage 6: Confirm and Install
- 9 Stage 7: Connect to NFS Server’s Share using umount.exe
- 10 Stage 8: Confirm the share in File Manager
Introduction
In our past guide, we installed NFS Server on Windows Server and made a share ready to be connected to. In this guide, we are going to make use of our share and our hope will be interesting. The procedure is basic and concise and here we go..
Stage 1: Server Manager
Open Server Manager, click on “Install Roles and Features” and snap “Next” on the wizard.
Stage 2: Role-based
In the “Select Installation type page”, select “Role-based or feature-based installation” and snap “Next”
Stage 3: Choose Server
Select the server you will install NFS on and click “Next”.
Stage 4: Select Server Roles
In this “Select server roles” part, click “Next”.
Stage 5: Features
In this “Select features” page, check the “Client for NFS” box and snap “Next”.
Stage 6: Confirm and Install
Confirm your installation selections and hit “Install”. Let it complete the process of installing at that point click “Close” and you will have completed the NFS Client installation process.
Open your Powershell with Administrator privileges and execute the command below. Ensure the drive you are marking the share isn’t used already on the client. Keep in mind; 10.10.20.2 is your NFS Server’s IP,/TestShare is the name you gave your Share and E:\ is the label your share will have on your NFS Client as confirmed in stage 8.
Open File Explorer and check if the share was mounted successfully. Play around with the offer by including files and directories while confirming they are reflecting in the parent directory.
For More Latest Articles Click on Below Link
https://www.worldofitech.com/category/microsoft-windows-server-2019/
I have recently been testing and working through some scenarios where I require the NFS client on a Windows machine to access some NAS shares over the NFS protocol, not much has changed I believe between Windows Server 2016 and Windows Server 2019 but thought it might help some to see how easy it is to get going.
I am picking up at this stage with my fully patched and ready to go Windows Server running 2019. As mentioned previously I want to use this machine to access my NFS share which doesn’t matter what it is or what it is for but this Windows machine is running in Microsoft Azure and I am access Azure NetApp Files over the NFS protocols, Azure NetApp Files can be presented over both NFS and SMB and I will have additional posts about this later.
Installing the Client for NFS
I am pretty sure this could also be achieved through the system manager and selecting the Add Features dialog and working through the wizard approach, I have been purposely doing a lot more of my tasks through PowerShell so that I can re-use and make my tasks quicker, this is something I have picked up from my learnings around Infrastructure as Code. For that reason, I am using PowerShell. I am sure someone else had documented the process through the system manager and UI.
First of all, let’s see what NFS based features we have available to us by running the below command.
Get-WindowsFeature -Name NFS*
As you can see from the image above, we have one feature available to us, “Client for NFS” by installing this it will allow us to mount NFS exports to our Windows machine so we can access the data within.
To install this feature run the following command.
Install-WindowsFeature -Name NFS-Client
That’s it, it’s that simple, hardly not worth mentioning. That’s the NFS Client installed on our machine, next we need to make sure from the NAS server point of view that the IP address of this windows machine can access that data.
As I said before I am using Azure NetApp Files, this export is configured in the following screen when configuring Azure NetApp Files. I will provide a step by step walkthrough of this process after this initial post.
As you can see from the above, I have allowed all clients from all subnets using the export policy (This is the default setting for ANF), my advice is that if this was production you should to create more secure export policies.
Mounting the share
Now we have our NFS Client and we have our export policy from whichever NAS device you are looking to mount onto your Windows, next we actually need to mount the share for use.
Some people will ask now, why you are using NFS when you can use SMB, certain applications, certain environments may require this method and protocol. If this was a traditional Windows environment and this share was going to house predominately user shares and home drives, then absolutely the way to do this would most likely be with the SMB protocol.
Next up is open up a command prompt with Administrator privileges, the mount command is going to be the command you use and then you will be using the NAS IP Address followed by the share name and then which letter you would like to mount this to on your Windows system.
Mount 10.1.1.4:/vZillaANFShare n:
Providing you have the correct configuration, mostly down to the export policy on your NAS device then this process should take seconds. And then by seeing the success message as per above but then checking this now as a mapped network drive as per below.
Quick post hope that it is useful for somebody. This was something I was working on so that I could test Azure NetApp Files without access to Azure Active Directory services (due to corporate policy) this stopped me from being able to use SMB but allowed me to test the functionality via NFS on Windows and Ubuntu.
Justin Parisi did a great blog on this at the start of the year – Windows NFS? WHO DOES THAT???
2019-11-12
How to Install and Configure NFS Client on Windows Server 2019. One of the services is NFS storage space sharing. NFS stands for Network File System and allows it to create a storage space that can be shared over other servers or clients over the network. This service operates as a server/client and through it can create central storage.
In our previous guide, we installed NFS Server on Windows Server and created a share ready to be connected to. In this article, we are going to teach of you how to Install and Configure NFS Client on Windows Server 2019.
Stay with us.
Table of Contents
A) Server Manager
Open Server Manager, click on Add Roles and Features and click Next on the wizard.
*
B) Role-based
In the Select Installation type page, select Role-based or feature-based-installation and click Next.
C) Choose Server
Select the server you will install NFS on and click Next.
D) Select Server Roles
In this Select server roles part, click Next.
E) Features
In this Select features page, check the Client for NFS box and click Next.
F) Confirm and Install
Confirm your installation selections and hit Install.
Let it finish installing then click Close and you will have finished the NFS Client installation process.
**
***
G) How to Connect to NFS Server’s Share using umount.exe
Open your Powershell with Administrator privileges and execute the command below.
Make sure the drive you are labeling the share with is not used already on the client.
— 10.10.20.2 is your NFS Server’s IP.
— TestShare is the name you gave your Share.
— E:\ is the label your share will have on your NFS Client as confirmed in step H.
H) Confirm the share in File Manager
Open File Explorer and check if the share was mounted successfully.
Play around with the share by adding files and directories whilst confirming they are reflecting in the parent directory.
Dear user, we hope you would enjoy this tutorial, you can ask questions about this training in the comments section, or to solve other problems in the field of Eldernode training, refer to the Ask page section and raise your problem in it as soon as possible. Make time for other users and experts to answer your questions.
Goodluck.
-
Star
(0)
You must be signed in to star a gist -
Fork
(0)
You must be signed in to fork a gist
-
Clone this repository at <script src="https://gist.github.com/gilangvperdana/8edd14319f7e0f82732d2554f1dcd278.js"></script>
- Save gilangvperdana/8edd14319f7e0f82732d2554f1dcd278 to your computer and use it in GitHub Desktop.
Clone this repository at <script src="https://gist.github.com/gilangvperdana/8edd14319f7e0f82732d2554f1dcd278.js"></script>
Mount NFS Directory on Windows Server 2019
Network File System (NFS) клиент по умолчанию не установлен в Windows Server 2022/2019/2016 и десяточных версиях Windows 11/10. Для его установки запустите Server Manager, выберите Add Roles and Features -> Client for NFS.
Если вы хотите установить графические консоли управления NFS (nfsmgmt.msc), выберите дополнительно Services for Network File System Management Tools в Remote Server Administration Tools -> Role Administration Tools -> File Services Tools.
Или вы можете установить клиент NFS и консоль управления с помощью PowerShell:
Install-WindowsFeature NFS-Client, RSAT-NFS-Admin
В Windows 10/11 для установки NFS клиента выполните:
Enable-WindowsOptionalFeature -FeatureName ServicesForNFS-ClientOnly, ClientForNFS-Infrastructure -Online -NoRestart
Клиент NFS в Windows поддерживает NFSv2 и NFSv3.
Теперь вы можете подключить NFS шару с помощью PowerShell:
New-PSdrive -PSProvider FileSystem -Name M -Root \\192.168.0.211\mnt\hyperv -Persist
Опция Persist включает автоматическое подключение NFS шары после перезагрузки.
Из CMD:
mount -o anon nolock \\192.168.0.211\mnt\hyperv M:
Также вы можете смонтировать NFS каталог из графического интерфейса File Explorer.
Для отключения NFS шары, выполните:
Umount M:
Или
Remove-PSdrive -Name M
При подключении NFS шары может появится ошибка:
The remote device or resource won’t accept the connection.
Чтобы исправить проблему, запустите консоль Services for Network File System (NFS) и проверьте права для подключения к удаленному ресурсу.
Если вы хотите подключиться к NFS ресурсу под anonymouse пользователем, нужно добавить два параметра реестра:
New-ItemProperty HKLM:\SOFTWARE\Microsoft\ClientForNFS\CurrentVersion\Default -Name AnonymousUID -Value 000001f4 -PropertyType "DWord"
New-ItemProperty HKLM:\SOFTWARE\Microsoft\ClientForNFS\CurrentVersion\Default -Name AnonymousGID -Value 00000064 -PropertyType "DWord"
Если для подключения нужно всегда использовать учетную запись root, измените значения параметров AnonymousUID и AnonymousGID на 0.
Если вы используете NFS подключения в окружении Active Directory, нужно отменить важный нюанс.
Если в AD не добавлены UNIX атрибуты и User Name Mapping не настроен, то для подключения к NFS серверу из Windows будет использоваться анонимное подключение. Для использование учетных данных для подключения к NFS вам нужно внести изменения в схему AD (атрибуты uidNumber и gidNumber).
На контроллерах домена WS 2012R2 можно добавить вкладку UNIX атрибутов в свойствах пользователя AD:
Dism.exe /online /enable-feature /featurename:adminui /all
Однако эта опция является deprecated в Windows Server 2016 и атрибуты пользователя предлагается править вручную или с помощью PowerShell:
Set-ADUser -identity user1 -add @{uidNumber="<user_unix_uid>";gidNumber="<user_unix_gid>"}
При подключении NFS каталога также может появится ошибка:
You can't access this shared folder because your organization's security policies block unauthenticated guest access. These policies help protect your PC from unsafe or malicious devices on the network.
В этом случае нужно создать параметр реестра AllowInsecureGuestAuth:New-ItemProperty HKLM:\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters -Name AllowInsecureGuestAuth -Value 00000001
New-ItemProperty HKLM:\ oftware\Policies\Microsoft\Windows\LanmanWorkstation -Name AllowInsecureGuestAuth -Value 00000001
Затем перепустите службу NFS.