I am using the Windows 7 NFS Client to access a Fedora FC 11 NFS Server. The identity presented by Windows NFS Client to the NFS server can only be set in AD or if running a special identity server that runs on Windows Server 2003 R2. Is there any way to set the identity from a standalone Windows client machine?
feedback
|
|
That's a tough one. Microsoft's NFS Client is designed for integrating Unix with a business network. It's not really for individual client machines. All the documentation suggests a mapping server of some kind is required. You may have better luck with a third-party nfs client: If your willing to wait, the CITI research group and the University of Michigan is researching an open source NFSv4.1 client for Windows. Ironically it is being funded by a grant from Microsoft. | ||||
|
feedback
|
|
On non-domain joined machines, you can setup Unix UID/GID to Windows Account mappings using the Lightweight Directory Services on Windows. Step by step guide is available on http://technet.microsoft.com/en-us/library/dd764497(WS.10).aspx. A scriptable solution to propagate the UNIX passwd/group files into an LDS instance is available at hhtp://support.microsoft.com/kb/973840 Both work very well when you have non-domain joined machines that need to use NFS protocol. | |||
|
feedback
|
|
For Windows 7 Client for NFS (packaged with Ultimate and Enterprise versions), you can set the Windows Registry Editor Version 5.00:
| ||||
|
feedback
|
