6. Click the UNIX Sharing tab.
7. Select the machine or group from the list on the left, or type an NFS client computer name or IP address in the box on the right.
8. Select the degree of control the specified client can exercise over files in the share from the Access Permissions list.
9. Select the Allow root access check box to grant root access to the selected group.
10. Click Add.
11. Click OK.
To remove a client or client group from an NFS share, perform the following steps:
1. On the Shares page, click Shares.
2. Select the share for which you want to remove an NFS client or client group.
3. In the Tasks list, click Properties.
4. Click the UNIX Sharing tab.
5. Select the system or client group from the list in the center of the page, and then click Remove.
6. Click OK.
Basic Scenarios
For UNIX and Windows NT®user name mapping, an NIS Server must already exist in the UNIX environment, or UNIX user and group files must exist on the
NAS system. User name mapping associates UNIX users and groups to Windows NT users and groups. You can use two types of maps, simple and explicit.
Simple maps define a one-to-one relationship between the same user names and groups. Explicit maps define a relationship between dissimilar user names
and groups.

Workgroup

In the workgroup scenario, you configure user name mapping locally on the NAS system. All maps are contained on this system, and Windows NT pass-through
authentication is performed locally on the NAS system.

Domain

In the domain scenario, you configure user name mapping locally on the NAS system. All maps are contained on this system, but Windows NT pass-through
authentication for domain users is performed by the domain controllers. This scenario requires that the Services for NFS Authentication component of Microsoft
Services for UNIX 3.0 is installed on all domain controllers.
Filename Character Translation
Although Windows and UNIX file systems do not allow certain characters in filenames, the characters that are prohibited by each operating system are not the
same. For example, a valid Windows filename can not contain a colon (:), but a UNIX filename can. If a UNIX user attempts to create a file in an NFS share and
that file contains an illegal character for Windows in its name, the attempt will fail.
You can use filename character translation to replace characters that are not allowed in a file system by mapping them to characters that are valid. To enable
filename character translation, create a text file that maps Windows to UNIX characters, and then modify the registry entry that specifies the path and name of
the translation file.
The filename character translation text file is a list of mapped characters in a format such as the following:
0xnn : 0xnn [ ; comment ]
where nn is the hexadecimal value of the character
NOTE: SFU 3.0 is an optional component that you must purchase separately from Dell.