Hp ProLiant DL585 G2 Storage-Server User Manual Page 80

  • Download
  • Add to my manuals
  • Print
  • Page
    / 150
  • Table of contents
  • TROUBLESHOOTING
  • BOOKMARKS
  • Rated. / 5. Based on customer reviews
Page view 79
the Windows user and group names to grant le access. If the UNIX UID and GID information is not
mapped, then Server for NFS will deny le access.
There are two ways to specify how Server for NFS on the storage ser ver obtains Windows user a nd
group information:
Using the Windows interface
Using a command line (nfsadmin.exe)
IMPORTANT:
Before using Active Directory Lookup, administrators must install and populate the Identity
Management for UNIX Active Directory schema extension, included in Windows Server 2003 R2, or
have an equivalent schema which includes UNIX UID and GID elds.
The IP address of the User Name Mapping server can be specied instead of the name of the server.
Before using User Name Mapping, the computer running Server for NFS must be listed in the
.maphosts le on the computer running User Name Mapping. For more information, see “Securing
access to the User Name Mapping server.
For additional information about accessing NFS resources, see the MSNFS online help. For additional
information about Identity Management for UNIX, see the UNIX Identify Management online help
Managing access using the .maphosts le
The User Name Mapping component of MSNFS acts as an intermediary between NFS servers and NFS
clients on a network containing UNIX hosts and Windows-based computers. To maintain the implicit trust
relationship between NFS client and host comp uters, administrators can control which computers can
access User Name M apping by editing the .maphosts in the %windir%\msnfs directory of the storage
server. Conditions to allow or deny access include:
If the . maphosts le is present but not empty, then only those comp uters allowe d access by entries
in the le can access User Name mapping.
If the .maphosts le is present but empty (the default), no computers except the computer running
User Nam e Mapping itself can access User Name Mapping.
If the .maphosts le is not present, no computers (including the computer running User Name
Mapping) can access User Name Mapping.
The ordering of entries is impor tant as User Name Mapping searches the .maphosts le from the top
down until it nds a match.
For additional information about the .maphosts le, see the MSNFS online help.
Allowing anonymous access to resources by NFS clients
It may be desirable to add anonymous access to a share. An instance would be when it is not desirable
or possible to create and map a U NIX account for every Windows user. A UNIX user whose account is
not mapped to a Windows account is treated by Ser ver for NFS as an anonymous user. By default, the
user identier (UID) and group identier (GID) is -2.
For example, if lesarecreatedonanNFSSharebyUNIXuserswhoarenotmappedtoWindowsusers,
the owner of those les a re listed as anonymous user and anonymous group, (-2,-2).
By default, Server for NFS does not allow anonymous users to access a shared director y. When an NFS
share is created, the anonymous access option can b e added to the NFS share. The values can be
changed from the default anonymous UID and GID values to the UID and GID of any valid UNIX user
and group accounts.
NOTE:
In Windows Server 2003, the Everyone g roup does not include anonymous users by default.
80
Microsoft Services for Network File System (MSNFS)
Page view 79
1 2 ... 75 76 77 78 79 80 81 82 83 84 85 ... 149 150

Comments to this Manuals

No comments