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

[domain_realm]
.org.hp.com = CIFSW2KSFU.ORG.HP.COM
[logging]
kdc = FILE: /var/log/krb5kdc.log
admin_server = FILE:/var/log/kadmin.log
default = FILE:/var/opt/KRB5lib.log
Installing SFU 3.5 on a Window 2000 or 2003 Domain Controller
POSIX accounts have some attributes, such as user ID, login shell, and home directory, which are
not used by Windows 2000 or 2003. To use Active Directory as a data repository for HP-UX users,
you must install SFU Version 3.5 on a Windows 2000 or 2003 doman controller. SFU is used to
extend the Active Directory schema to include the POSIX schema. For detailed installation instructions
for SFU 3.5, refer to Chapter 2 "Installing LDAP-UX Client Services", in LDAP-UX Client Services
with Windows 2000 Active Directory Server Administrator's Guide, available at http://docs.hp.com.
For more information on SFU, refer to the Microsoft web site at http://www.microsoft.com/
windows2000/sfu/.
NOTE: You need to install the LDAP-UX Client Services software on an HP CIFS member server
before installing SFU on a Windows 2000 or 2003 domain controller.
An Example of the Unified Domain Model
Figure 9-10 shows an example of the Unified Domain Model which has the realm named
HPCIFSW2KSFU.ORG.HP.COM, an ADS domain controller machine hpntcdn, an HP CIFS Server
machinehostD acting as a member server and the Windows NT machine with IP address
1.13.112.166 as the WINs server.
Figure 32 An Example of the Unified Domain
Windows
ADS DC/SFU
“hpntcdn”
Realm:
CIFSW2KSFU
.ORG.HP.COM
Windows
and UNIX
users
Windows
NT/WINS
Server
IP address
“1.13.112.166”
HP CIFS
Member Server
“hostD”
A sample smb.conf file For an HP CIFS Member Server
The following is a sample Samba configuration File, /etc/smb.conf, used for an HP CIFS Server
machine hostD acting as an ADS member server in the sample Unified Domain Model shown in
Figure 9-10:
######################################################
#
# An sample smb.conf file for an HP CIFS ADS member server
#
130 HP CIFS Deployment Models