HP CIFS Server 3.0a Administrator's Guide version A.02.01

HP CIFS Deployment Models
Windows Domain Model
Chapter 11 203
Figure 11-6 shows the Windows Domain Deployment Model as follows:
Figure 11-6 Windows Domain
In the Windows Domain Model, HP CIFS Server can join to a Windows
domain as a member server with Windows NT or Windows 200x domain
controllers. HP CIFS Server supports winbind to provide UID and GID
mappings for Windows users. For a larger deployment environment, you
can use the LDAP directory to maintain unique ID maps across multiple
HP CIFS Servers.
Windows Domain Components
HP CIFS Server supports the NTLMv1/NTLMv2 security used for NT
domain membership and Kerberos security used for Windows 2000/2003
native membership, so HP CIFS Servers can be managed in any
Windows 2000/2003 ADS, Windows 200x mixed mode, or NT
environment. HP CIFS Server does not support a true SAM database
and can not participate as a domain controller in an Windows NT,
Windows 2000 or Windows 2003 domain. HP CIFS supports winbind,
Windows NT
Windows NT
or Windows
ADS/PDC
HP CIFS
Member
Server
LDAP
ldap-ux client
winbind daemon
libnss_winbind
idmap.tdb
idmap backend
windows
users
BDC
windows
users
idmaps
winbind
winbind
= ldap