Authentication Table - HP ProLiant SB460c - SAN Gateway Storage Server User Manual

UNIX computers follow advisory locking for all lock requests. This means that the operating system
does not enforce lock semantics on a file, and applications that check for the existence of locks can
use these locks effectively. However, Server for NFS implements mandatory locks even for those
locking requests that are received through NFS. This ensures that locks acquired through NFS are
visible through the server message block (SMB) protocol and to applications accessing the files locally.
Mandatory locks are enforced by the operating system.
Server for NFS Authentication DLL versus Service for User for Active Directory domain controllers
On a Windows Storage Server 2003 R2 storage server, Server for NFS depends on a domain
controller feature called Service for User (S4U) to authenticate UNIX users as their corresponding
Windows users. Windows Server operating systems prior to Windows Server 2003 and Windows
Storage Server 2003 do not support S4U. Also, in mixed domain environments, legacy Services for
UNIX (SFU), Services for NFS and Windows Storage Server 2003 NFS deployments do not use the
S4U feature and still depend on the Server for NFS Authentication DLL being installed on domain
controllers.
Therefore, the administrator needs to install the Server for NFS Authentication DLL on Windows 2000
domain controllers when:
• The NFS file serving environment uses previous NFS releases (NAS, SFU, and so on).
• The Windows domain environment uses pre-2003 domain controllers.
See Table 4 for guidance as to when to use NFS Authentication DLL instead of S4U legacy NFS and
R2 MSNFS.
Table 4 Authentication table
Domain controller type
Legacy domain controller
(pre-WSS2003)
Recent domain
controllers (WSS2003
and later)
The S4U set of extensions to the Kerberos protocol consists of the Service-for-User-to-Proxy (S4U2Proxy)
extension and the Service-for-User-to-Self (S4U2Self) extension. For more information about the S4U2
extensions, see the Kerberos articles at the following URLs:
searchwindowssecurity.techtarget.com/originalContent/0,289142,sid45_gci1013484,00.html
(intended for IT professionals) and
default.aspx (intended for developers).
Installing NFS Authentication DLL on domain controllers
NOTE:
If the authentication software is not installed on all domain controllers that have user name mappings,
including primary domain controllers, backup domain controllers, and Active Directory domains, then
domain user name mappings will not work correctly.
You need to install the version of NFS Authentication included with Services for UNIX 3.5. You can download
Services for UNIX 3.5 at no charge from http://go.microsoft.com/fwlink/?LinkId=44501.
66 Microsoft Services for Network File System (MSNFS)
Legacy NFS (pre-WSS2003
R2)
Requires NFS Authentication
DLL on domain controller
Requires NFS Authentication
DLL on domain controller
http://msdn.microsoft.com/msdnmag/issues/03/04/SecurityBriefs/
MSNFS (WSS2003 R2)
Requires NFS Authentication DLL on domain
controller
Uses the built-in S4U (on the domain controller). It
is unaffected by the NFS Authentication DLL on the
domain controller.
http://