HP CIFS Server 3.0f Administrator's Guide verison A.02.03

9 HP CIFS Deployment Models
This chapter describes three HP CIFS deployment models: Samba Domain, Windows Domain, and Unified
Domain. Examples of configuration files for each deployment model are provided for reference. It contains
the following sections:
• “Introduction”
• “Samba Domain Model”
• “Windows Domain Model”
• “Unified Domain Model”
Introduction
HP CIFS provides HP-UX with a distributed file system based on the Microsoft Common Internet File System
(CIFS) protocols. HP CIFS server interoperates with Windows NT, Windows 200x, Advanced Server, and
other CIFS servers and clients. This chapter provides reference for three deployment models: Samba Domain
Model, Windows Domain Model, and Unified Domain Model. These three models represent common network
environments and demonstrate HP CIFS Server's flexibility.
Each model shows server relationships, but all deployment models support native file access with any
combination of the following clients:
• Windows 2000, XP SP1 sand XP SP2
• Windows Terminal Server (NT4 and 2000)
• HP CIFS Client
• UNIX workstations (via mounting NFS exported CIFS directories)
Samba Domain Model
You can use the Samba Domain Deployment Model in environments with the following characteristics:
• A domain consisting of HP CIFS Servers and no Windows domain controllers.
• Support for any number of UNIX servers that provide file and print services for corresponding numbers
of users.
• An HP CIFS server is configured as a Primary Domain Controller (PDC). One or more HP CIFS Servers
act as Backup Domain Controllers (BDCs).
• The PDC and BDCs use the LDAP backend to consolidate common Posix and Windows accounts on
the LDAP directory. It requires LDAP-UX Integration software for larger deployments.
• Access to an LDAP-UX Netscape Directory Server as the backend storage for larger deployments.
The Samba Domain Model provides the following benefits:
• It can be expanded easily.
• The HP CIFS Server acting as a BDC can pick up network logon requests and authenticate users while
the PDC is busy on the network. The BDC can be promoted to a PDC if the PDC needs to be taken out
of services or fails. The PDC-BDC model provides authentication load balancing for larger networks.
• The PDC, BDCs, and domain member servers store account databases in the LDAP directory to centralize
administration regardless of network size.
Figure 9-1 shows a standalone HP CIFS Server as a PDC with the local password database:
Introduction 121