Map NFS share to the windows machine

[bronze glacier]

Hi Team,

We have a couple of questions as follows:

• How can we map an NFS share to a Windows machine (desktop/server)?
• What is the step-by-step procedure to map an NFS share to a Windows machine?
• Can we map the CIFS share to the UNIX/Linux machine? If yes, we would like to know the procedure for the same?

We have been following the below steps to map the NFS share to a Windows machine:

-Created an SVM with NFS protocol enabled.
-Created a volume within the NFS-enabled SVM.
-Configured the NFS share during volume creation on the NetApp storage.
-Installed the "Client for NFS" feature on the Windows machine.
-Tried mapping the network drive on the Windows machine using File Explorer: \server_name\share_name

However, it shows the error "Windows is not able to access the path."

We can successfully ping the NFS LIF IP from the Windows machine.

Could any one please assist us with this? Are there any additional steps we need to follow?

I’ve also referred to the following KB article for guidance:

https://docs.netapp.com/us-en/ontap/nfs-admin/enable-access-windows-nfs-clients-task.html#:~:text=To successfully use this functionality,of certain requirements and limitations.&text=By default%2C Windows NFSv3 client support is disabled.&text=NFSv3 must be enabled on the SVM.&text=Windows NFSv3 clients can now mount exports on the storage system.

We followed the instructions in the article, but we are still encountering the same error. Kindly provide the step-by-step procedure to map the NFS share to a Windows machine and CIFS share to UNIX/linux machine.

Thank you for your assistance.

[midnight saffron]

couple of things.
on the NFS side for the NetApp, what is the export policy? Does the machine have access by name or ip in the policy?
to map the mount it would need to be different than accessing a normal SMB share.
You need to use the mount command
mount server:/mount z: (server being the netapp, mount being the mount name, and z: being the letter to map to)

depending on the version of windows you are using the mount command might be a little different.
mount \server\share z:
you also might hagve to use -o nolock or -o hard depending on other factors.
but the biggest thing to verify is the policy and if the system is allowed access

[small steeple]

curious: Why use NFS on Windows? the NFS client on windows is not very RFC compliant. Why not just share the same volume via SMB to Windows clients?

[bitter trout]

Even for volumes with a security style of "unix", you can still create CIFS shares for it and access it from windows. It starts to get real goofy with permissions though. Not sure if you have a requirement to use NFS on Windows specifically, or if you just want to access an existing volume that is currently mounted and exported to your unix environment?

Just create the cifs share as you normally would, use the junction-path of the unix volume. Leave the default "Everyone - Full Control" access for testing purposes at first.

Then navigate to the share in Windows. ONTAP will attempt to convert your Windows user ID to a Unix ID based on the rules described in this KB (check out the "How does name-mapping work for CIFS clients accessing UNIX security style resources?" section):
https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/Understanding_name-mapping_in_a_multiprotocol_environment

Whatever unix permissions you have configured on that volume will be enforced on the user account that ONTAP has assumed for the CIFS session. You can create explicit rules to tell ONTAP how to convert users as well using "vserver name-mapping":
https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/How_to_create_and_understand_vserver_name-mapping_rules