The following example describes this issue in more detail:
- Configure a Windows 2000 Server as a new domain controller
for a new domain named example.com.
- Start the DNS snap-in and create a new primary DNS zone (in
addition to the DNS zone for example.com) with a namespace of
domain.com.
- Configure a member server to use this new DNS namespace. To
do so:
- On the member server, right-click My
Computer and then click Properties.
- Click the Network Identification tab,
and then click Properties.
- Click More, and then type
domain.com in the Primary DNS suffix of this
computer box.
- Click to clear the Change primary DNS suffix
when domain membership changes check box and then click
OK.
- Click OK, and then restart the
computer when prompted.
- Join the member server to the Example.com
domain.
- On the domain controller, run the ISA Server
Enterprise Initialization portion of Setup.
- When Active Directory schema has been successfully updated,
run the Install ISA Server portion of Setup on the member
server whose domain namespace you changed to domain.com.
The installation of ISA Server 2000 will be unsuccessful on this
member server because ISA Server 2000 Setup queries the DNS that is specified
in the TCP/IP properties of the member server (in this case, that of
domain.com) to obtain service records like LDAP and Kerberos. However, because
these records do not exist in the
domain.com zone,
but are registered in the
example.com zone, Setup is
unsuccessful.
For additional information about other issues that may
prevent ISA Server 2000 from querying Active Directory, click the following
article number to view the article in the Microsoft Knowledge Base:
282035�
Unable to Control ISA If LAT Configuration Prevents Access to Domain Controller