Anonymous access FAQ with UNIX clients after Windows 2008 added and made to the Server for NFS role

In the complex host and network environment, we may be exposed to a variety of host and operating system, with the Windows Server 2008 R2 Native "NFS Server" feature can make such a complex operating system more convenient to apply.

However, in the face of the network of numerous Help Guide and Setup Wizard will inevitably cause some incomplete operation, this blog after the relevant attempts on the anonymous access to some of the support for some make up, but also welcome many netizens to correct.

Microsoft Official website provides the appropriate server for NFS configuration guide, if you are the first time use can refer to this link: http://technet.microsoft.com/zh-cn/library/cc753312.aspx

This article refers to the UNIX client anonymous access Windows provided NFS server is in a more specific direction, so it is highly recommended that you use authenticated authorization to access and connect without more secure safeguards, and that the existing environment does not use domain control for unified authorization and management. Therefore, the operation is entirely in accordance with the mode of independent host practice.

The following are the common questions that I summarize after I use myself to allow anonymous access.

Question one: What happens when "Input/output error" occurs when a UNIX client mounts (mount)?

Answer: The client needs to turn on the protmap service , and the server needs to set the appropriate NFS access ( Anonymous access permissions need to be set gid=-2, uid=-2) , the security policy sets network access: apply Everyone permissions to anonymous users as enabled , and NFS permissions to read and write to shared directories.

Figure 1 Problem One illustration, set NFS Authentication to ensure anonymous access is valid

Figure 2 Problem One illustration, set NFS permissions to ensure that the shared directory is readable and writable

Question two: After the client mounts, prompts no permissions ("Permission Denied") to create a file or folder

Answer: The lack of permissions mentioned here is mostly because the NFTS permission policy cannot be created because it uses the "user" of the UNIX anonymous account id=-2 that does not exist in Windows itself, and we need to add this special user ID to the corresponding NTFS Access CONTROL permission (ACL) inside, we use the nfsfile command (the command needs to be available after the NFS service role is installed) to do so.

The help commands are simple, and the following table shows the Help file information:

Operation NFS the service properties of the file. nfsfile [/v][/S] [/I [u=<uid>]|[ g=<gid>]| [wu=<account>]| [Wg=<account>]]] [/R[[u=<uid>]|[ g=<gid>]| [M=<mode>]]] [/c[w|x]] <filespec> /? -This message /V-Detailed /s-Scan subdirectories to find matching files /I-includes files that match the specified criteria U <uid>-NFS owner SID Match <uid> G <gid>-NFS group SID matching <gid> Wu <account>-NFS owner SID matching <account> WG <account>-NFS group SID matching <account> /R-Replaces the options specified on the file U <uid>-Set UID G <gid>-Set GID M <mode>-Set the mode bit to <mode> Wu <account>-set Windows owner account WG <account>-Set up Windows group accounts /C-Convert file basis W-windows style ACL (mapped) X-unix style ACL (unmapped)