I have Windows 7 Professional, but the NFS Client for Windows is only included in the Enterprise and Ultimate editions.
Microsoft Server 2003
NFS Windows Client to Access Unix System - DiskAccess is Premier NFS Windows Client enables Windows 9x/NT/2000/2003/XP systems to perform as NFS clients, so you can access file and print resources located on UNIX servers, mainframes, or other NFS-based server systems.DiskAccess is Premier. Feb 03, 2011 Windows 2003 has an add on component called Windows Services for UNIX has a component called Client for NFS. Services for UNIX setup is used to add/remove Client for NFS. Windows 2008 and Windows 2008 R2 the Services for Network File System have been made part of the File Server Role.
I would like to connect some Windows machines to our NFS server so I can drop the Samba Server we are currently using.
Are there any free NFS clients for Windows 7?
I know there are some tools like ProNFS and axeNFS but they are not free.
ThatGraemeGuy7 Answers
Check this open source project:
Nekodrive
https://github.com/nekoni/nekodrive
The target of this project is to implement NFS (Network File System v2/v3/v4.1) over the Dokan user file system for windows. This let you mount very easily an NFS export as a local windows drive. You don't need any NFS windows client to access the NFS remote export, you can just use microsoft explorer. The current version doesn't support NFS v4.1 yet.
As long as I understand the question, you should be able to use Microsoft Windows Services for UNIX. You can get them here:
Informative Edit: Download in link is no longer available. 2017-Nov-05
StevenAs only a last resort I suppose it would be possible to install a linux in a Virtualization environment hosted by the Windows workstation, ie. Virtualbox- which would then provide a shared storage that the guest would have mounted as an NFS volume.
I imagine it would help considerably to have a seperate network interface for the guest to mount the share through.
In other words:
Install Virtualbox to Windows desktop.
Install TinyCore to Virtualbox.
Configure TinyCore's environment to include a shared storage directory.
Install nfs-common to TinyCore.
Mount desired NFS share from TinyCore.
6a. Either point the Virtualbox share to where TinyCore mounts the NFS share to reach it from the Windows host,
or
6b. Mount the NFS mount to the directory Virtualbox is providing to the Windows host.
As I said, last resort.
NginUSNginUS
There's an NFS 4.1 Windows client open source project from UMichigan, but you have to build it yourself and I suspect it would need some testing before deployment in a production environment.
I'd be hesitant of running one that isn't Microsoft's or a very well tested solution - especially for any 'serious' sharing (beyond simple file copy).
Realize NFS is a very powerful network protocol, more so than most people use it for. For example storing virtual machine images on NFS works fine, survives a server outage (regardless of length) without losing data, etc.
This covers why it's not 'easy' - http://cygwin.com/ml/cygwin/2006-10/msg01074.html
A better question mayb e why not just use samba on the nfs server to expose the shares via smb? I ask because you make it sound like the two servers are unrelated. Samba should be fairly easy to support on the same machine.
I don't know of any free NFS client programs for Windows. I did some googling and found these:
Nfs Client Service Windows Server 2012
I tried the Win7 NFS client and it wasnt that great. So dont be too quick to drop your samba server, even if you find a client.
I think cygwin has a NFS client and server now. However the client is just the cusp of the problem. There's also aligning the unix permissions with the windows ones which is non-trivial.