Active Directory Configuration Issues ...

1. Configure a "Active Directory Domain Controller" on server A

2. Set Server B's domain to the domain configured in server A , say, "sample.com"

In step 2 we may get some exceptions as :

• The following error occurred when DNS was queried for the service location (SRV) resource record used to locate an Active Directory Domain Controller (AD DC) for domain "xxx.com":

  The error was: "DNS name does not exist."

  (error code 0x0000232B RCODE_NAME_ERROR)

  The query was for the SRV record for _ldap._tcp.dc._msdcs.xxxx.com

  Common causes of this error include the following:

  - The DNS SRV records required to locate a AD DC for the domain are not registered in DNS. These records are registered with a DNS server automatically when a AD DC is added to a domain. They are updated by the AD DC at set intervals. This computer is configured to use DNS servers with the following IP addresses:

  xx.xx.xx.xx

  - One or more of the following zones do not include delegation to its child zone:

  xxx.com

  com

  . (the root zone)

• The following error occurred attempting to join the domain "bamv2":

  An attempt to resolve the DNS name of a domain controller in the domain being joined has failed. Please verify this client is configured to reach a DNS server that can resolve DNS names in the target domain. For information about network troubleshooting, see Windows Help.

This is possibly caused by wrongly setting the DNS server IP on the client which is intented to join the target domain.

Open Network and Sharing Center -> Local Area Connection Properties Dialogbox -> IPV4 Properties dialog -> Use the folowing DNS IP Address -> Set "Preferred DNS Server" to the target AD server ip address