Introduction

This chapter describes how to configure the roles that an HP CIFS Server can play in an NT style domain, whether it is a Samba Domain, consisting solely of HP CIFS Servers, or as an NT Domain with a Microsoft NT Primary Domain Controller (PDC). Configuration of Member Servers joining an NT style domain or a Windows 2000/2003 Domain as a pre-Windows 2000 compatible computer is described here. Chapter 5, Windows 2000/2003 Domains, should be consulted for configuration of Member Servers joining Domains with a Windows 2000/2003 Domain Controller as an ADS Member Server. Chapter 9, HP CIFS Deployment Models describes further how the server roles can be utilized in common network deployments.

HP CIFS Server can be configured to play different roles in an NT Style Domain Model including:

Member Server in an NT Domain with a Microsoft NT PDC
PDC in an Samba Domain where an HP CIFS Server serves as the PDC
Backup Domain Controller (BDC) in an Samba Domain where an HP CIFS Server serves as the PDC
Member Server in an Samba Domain where HP CIFS Server serves as the PDC

Advantages of the Samba Domain Model

The HP CIFS Server PDC domain model provides a number of advantages:

HP CIFS Server PDC domain administrators may group workstations and servers under the authority of a domain controller
Domain members may be centrally administered by using domains to group related machines. One of the benefits of this is the ability for user accounts to be common for multiple systems. A user may now make one password change which will affect multiple systems accessed by that user. Another benefit is that IT administration work is reduced, since there is no longer a need for individual accounts to be administered on each system
HP CIFS BDCs may be configured to off load some of the HP CIFS PDC authentication responsibilities and can be promoted to a PDC if the PDC fails or needs to be taken out of services.

Primary Domain Controllers

The Primary Domain Controller (PDC) is responsible for several tasks within the domain. These include:

Authenticating user logons for users and workstations that are members of the domain
Acting as a centralized point for managing user account and group information for the domain
A user logged on to the Primary Domain Controller (PDC) as the domain administrator can add, remove or modify Windows domain account information on any machine that is part of the domain

Backup Domain Controllers

Advantages of Backup Domain Controllers

HP CIFS Server with BDC support provides the following benefits to the customer:

The BDC can authenticate user logons for users and workstations that are members of the domain when the wide area network link to a PDC is down. A BDC plays an important role in both domain seurity and network integrity.
The BDC can pick up network logon requests and authenticate users while the PDC is very busy on the local network. It can help to add robustnees to network services.
The BDC can be promoted to a PDC if the PDC needs to be taken out of services or fails. This is an important feature of domain controller management. To promote a BDC to a PDC on the HP CIFS Server, change the domain master parameter from "no" to "yes".

Limitations

The following is a list of limitations for the BDC support:

HP CIFS Server can only function as a BDC to an HP CIFS PDC.
HP CIFS Server and MS Windows server can each function as a BDC to its own type of PDC.
HP CIFS Server cannot create Security Account Management (SAM) update delta files. It cannot interoperate with a PDC to synchronize the SAM from delta files that are held by a BDC.
The Samba 3.0 BDC does not support replication to a PDC. Running a Samba 3.0 BDC with a non-LDAP backend can have the difficulty in synchronizing the SAM database. Refer to Table 5.1, Domain Backend Account Distribution Option, in the Official Samba HOWTO and Reference Guide for more information on possible design configuration for a PDC/BDC infrastructure.

Domain Members

The following member servers are supported:
- Windows NT
- Windows 2000 and Windows 2003
- HP CIFS Server
Users on a domain member machine can access network resources within the domain. Some examples of these resources are file and printer shares and application servers
Domain members do not perform the user authentication for user logons. Instead, the member sends the credentials to a domain controller via a secure channel. The domain controller checks the credentials against those in its database and returns the results to the member server. Access is granted based on the results returned

Introduction

Technical documentation

» Table of Contents

» Glossary