Domain Authentication

A domain, as it pertains to Windows, is a group of computers that share a network resource database and have a common security policy. A Windows domain contains a primary domain controller (PDC) computer that acts as the resource and user manager for the entire domain. One or more computers in the domain can be configured to act as a backup domain controller (BDC). The BDC can take over for the PDC should any problems arise. The remaining computers in the domain are user workstations or servers that provide resources to domain users.

Within a Windows domain, Host Integration Server 2004 computers are logically grouped into an entity called a subdomain. Each SNA subdomain can contain up to 15 Host Integration Server 2004 computers, and a Windows domain can contain an unlimited number of subdomains. It is common to have multiple domains that manage user accounts independently of one another.

The domain model provides two key advantages over peer-to-peer networks with regards to security:

  • You can manage user accounts from a central location.
  • You can set up one unified security system for all user accounts in the domain.

Host Integration Server 2004 relies on the PDC or BDC to provide authentication services to users requesting access to host resources. Only users who have been validated by the PDC or BDC can gain access to resources provided by servers in the subdomain.

You can use domain authentication to verify users who request resources provided by these services:

  • 3270 or 5250 terminal access from workstations using Host Integration Server 2004 client software
  • APPC, CPI-C, or LUA applications built using Host Integration Server 2004 APIs

See Also

About Authentication

Workstation Authentication

To download updated Host Integration Server 2004 Help from, go to

Copyright © 2004 Microsoft Corporation.
All rights reserved.