With the Services for NFS snap-in, you can administer each installed component of Services for NFS. When you open the snap-in, the components installed on the local computer are available to administer.

To open Services for Network File System

• Click Start, point to Administrative Tools, and click Services for Network File System (NFS).

Note

To perform this procedure, you must be a member of the Administrators group on the local computer, or you must have been delegated the appropriate authority. If the computer is joined to a domain, members of the Domain Admins group might be able to perform this procedure. As a security best practice, consider using Run as to perform this procedure. You can get help for an item in this snap-in by right-clicking the item and then clicking Help.

Services for NFS provides the following Windows command-line administration tools. To run a tool, type its name at the command prompt. For information about the available parameters, at the command prompt, type toolname /?.

• mapadmin. Administers User Name Mapping.
  
  
• mount. Mounts NFS shared network resources.
  
  
• nfsadmin. Manages Server for NFS and Client for NFS.
  
  
• nfsshare. Controls NFS shared resources.
  
  
• nfsstat. Displays or resets counts of calls made to Server for NFS.
  
  
• showmount. Displays mounted file systems exported by Server for NFS.
  
  
• umount. Removes NFS-mounted drives.
  
  

You need to deploy the following computers and connect them on a local area network (LAN):

• One or more computers running Windows Server 2008 on which you will install the three main Services for NFS components: User Name Mapping Server, Server for NFS, and Client for NFS. You can install the components on the same computer or on different computers. Installation instructions for installing all Services for NFS components are provided later in this document.
  
  
• One or more UNIX computers running NFS client and NFS server software. The computer running the NFS client will access a Windows NFS shared resource provided by Server for NFS. The computer running NFS server will host a UNIX NFS shared resource, which will be accessed by a computer running Windows Server 2008 and Client for NFS. You can install the NFS client and NFS server software on the same computer or on different computers.
  
  
• A Windows Server 2008 domain controller running at the Windows Server 2008 functional level. The domain controller will provide user authentication information for the Windows environment. Or, if you prefer, you can use local user accounts.
  
  
• A Network Information Service (NIS) server to provide user authentication information for the UNIX environment. Or, if you prefer, you can use Password and Group files that are stored on the computer running the User Name Mapping service.
  
  

For the purposes of this test, you can create several fictitious users. For each user, you can create one Windows security account and one UNIX security account, giving the two accounts different user names. You can later use these accounts to test the advanced mapping feature of Services for NFS. Advanced mapping allows you to map a given user's credentials between Windows and UNIX, even when the user name is different.

Note
The alternative to advanced mapping is simple mapping. You can use simple mapping when Windows and UNIX user names for each user are the same. For more information, see the Help topics about User Name Mapping (http://go.microsoft.com/fwlink/?LinkId=127917).

You can create the Windows user accounts on the Windows Server 2008 domain controller. Or if you prefer, you can create local user accounts on each Windows-based computer in the deployment. For instructions on configuring user accounts, see your Windows Server 2008 documentation.

You can create the UNIX user accounts either on the NIS server or in UNIX /etc/passwd and /etc/group files. For instructions on creating NIS user accounts, see the documentation for your NIS server. For instructions on creating /etc/passwd and /etc/group files, see the documentation for your UNIX operating system.

The following table lists some examples of fictitious users and corresponding user and group accounts that you may want to use for this test.

1. Click Start, point to Administrative Tools, and then click Server Manager.

2. In the left pane, click Roles.

3. Under Roles Summary in the right pane, click Add Roles. The Add Roles Wizard appears. Click Next.

4. Select the File Services check box to install this role on the server, and then click Next.

5. Select the Services for Network File System check box, and then click Next.

6. Confirm your selection, and then click Install.

7. When the installation completes, the installation results appear. Click Close.

1. On the computer running Server for NFS, create a folder to use as the NFS shared folder.

2. Right-click the folder you created and click NFS Sharing.

3. Select Share this folder.

4. If you want to allow anonymous access, select Allow anonymous access.

5. Click Permissions, click Add, and then do either of the following:

   • In the Names list, click the clients and groups you want to add and click Add.
     
     
   • In the Add Names box, type the names of clients or groups you want to add, separating names in the list with a semicolon (;).
     
     

6. In the Type of Access list, click the type of access you want to allow the selected clients and groups.

7. Select Allow Root Access if you want a user identified as root to have access other than as an anonymous user. By default, the user identifier (UID) root user is coerced to the anonymous UID.

8. In the Encoding list, click the type of directory name and file name encoding to be used for the selected clients and groups.

9. Click OK twice, and then click Apply.

Note
To perform this procedure, you must be a member of the Administrators group on the local computer, or you must have been delegated the appropriate authority.

Note
To see a list of the members of a group, in the Names list, click a group, and then click Members.

1. On the computer running Client for NFS, open Services for NFS. To open Services for NFS, click Start, point to Administrative Tools, and then click Services for Network File System.

2. In the console tree, right-click Client for NFS and click Properties.

3. On the File Permissions tab, select the default file permissions to apply to each new file and folder created by this computer, and then click OK.

Note
To perform this procedure, you must be a member of the Administrators group on the local computer, or you must have been delegated the appropriate authority.

On the computer(s) running User Name Mapping and Server for NFS, you must open ports in Windows Firewall. On a computer and running only User Name Mapping, you only need to open the portmapper port. On a computer running Server for NFS, you must open all of the ports listed in the following table.

To open ports in Windows Firewall

Note
Depending on your requirements, you may need to open Transmission Control Protocol (TCP) ports, User Datagram Protocol (UDP) ports, or both TCP ports and UDP ports. For testing purposes, we recommend that you open both TCP and UDP transports for all protocols.

On the computer running User Name Mapping, you must add the Mapsvc.exe program to the Windows Firewall exception list.

To add Mapsvc.exe to the exception list

On the computer hosting the Services for NFS snap-in and Services for NFS command-line tools, you must enable file and printer sharing in Windows Firewall.

To enable file and printer sharing

The test is successful if you can map the drive and view the test file on the NFS shared resource from the computer running Client for NFS.

To map a drive letter to a UNIX-based NFS shared resource

The test is successful if you can create a new document, and its ownership and permission match the default file permissions that you had specified.

To create a test file and verify its permissions

The test is successful if you can mount the NFS shared resource.

To mount the Windows NFS shared resource

The test is successful if you can create the text file and the file permissions match from both Windows and UNIX.

To create a test file and verify the file permissions match from both Windows and UNIX