HP CIFS Server Administrator's Guide (5900-1282, April 2011)

NOTE: :88 is required on the server field.
A Sample /etc/nsswitch.conf File
In the ADS Domain Model, you must configure the /etc/nsswitch.conf file to specify the
winbindname service and other name services that you want to use.
The following is a sample /etc/nsswitch.conf used in the sample ADS Domain Model shown
in Figure 9-7:
# /etc/nsswitch.conf #
# #
# This sample file uses Lightweigh Directory Access #
# Protocol(LDAP) in conjunction with dns and files. #
passwd: files winbind [NOTFOUND=return] ldap
group: files winbind [NOTFOUND=return] ldap
hosts: files dns [NOTFOUND=return]
networks: files
protocols: files
rpc: files
publickey: files
netgroup: files
automount: files
aliases: files
services: files
NOTE: HP CIFS Server supports several ways to allocate and map POSIX users and groups. If
winbind is used, winbind name service is required in /etc/nsswitch.conf. If winbind is
not used, a local POSIX account associated with each Windows user and group must be created.
One way to create these accounts automatically is to define the "add user script" and "add
group script" options in smb.conf. See the SWAT help text for more information.
An Example of Windows NT Domain Model
Figure 9-8 shows an example of the Windows NT Domain Model which has a Windows NT server
named hostP as a PDC, an HP CIFS Server machine hostM acting as a domain member server.
The ID maps are saved in the local file, idmap.tdb.
Windows Domain Model 125