IBM TotalStorage NAS 300, User Reference

Page: 63 / 200

7) Select a UNIX group name to be mapped to the Windows group name
that you specified.
8) Click Add to add the mapping between the UNIX group name and
Windows group name to the list of maps.
9) If multiple Windows group names are mapped to one UNIX group
name, you must select one Windows group name to be the primary
group name. Select the mapping corresponding to the primary group
name from the list of maps, and then click
Set Primary .
10. Click Apply .
You can now continue with “Creating shares”.
Creating shares
To create new file shares on the NAS Gateway 300, do the following:
1. Start the Windows 2000 for NAS user interface.
2. Click the Shares tab.
3. Click the Shares task.
4. Click New... .
5. Specify the share name (the name that clients and servers will use to access
the share).
6. Specify the share path and select the Create folder if it does not already
exist check box.
7. By default, the Microsoft Windows (CIFS) and UNIX (NFS) check boxes are
selected (enabled). If this share is not to be accessed by Windows clients and
servers, clear (disable) the Microsoft Windows (CIFS) check box. If this share
is not to be accessed by UNIX clients and servers, clear the UNIX (NFS)
check box.
8. If this share is to be accessed by:
v
Windows clients and servers, then click CIFS Sharing and specify the
access permissions that you want. (Note that, by default, every user has full
access to all files and directories under the shared folder.)
v
UNIX clients and servers, then click NFS Sharing and specify the access
permissions that you want. (Note that by default, every user has full access
to all files and directories under the shared folder.)
9. Click OK . The new share should appear in the list of shares.
10. Repeat Steps 4 through 9 for each additional share that you want to create.
A note on anonymous access: It is strongly recommended that you not disable
anonymous access. If a client presents a UID that is not recognized, Server for
NFS can still grant that client a very limited form of access as a special
nobody
user. This is known as anonymous access, and you can enable or disable on a
per-share basis. This anonymous user will have very limited access to resources on
the NAS: it has only the permissions that are granted to the
Everybody group in
Windows, which corresponds to the other (or world ) bits in a POSIX permissions
mode.
Allowing anonymous access is not a security risk, so disabling it might provide a
false sense of security. (The real security risk is to grant everyone access to
resources that should be protected.) And disabling anonymous access has one
severe consequence: it is so unexpected by NFS clients that they might not be able
to connect as NFS V3 clients at all, and might instead downgrade the connection to
use the NFS V2 protocol.
Chapter 5. Completing networking, clustering, and storage access setup
49