Adding a PC to a domain

  • Thread starter Thread starter Ste
  • Start date Start date
S

Ste

We are trying to add a PC to a domain, but keep coming up with this error
message:


A domain controller for the domain %domainname% could not be contacted.

The following error occurred when DNS was queried for the service location
(SRV) resource record used to locate a domain controllerfor domain
%domainname%:

The error was: "This operation returned because the timeout period expired."
(error code 0x000005B4 ERROR_TIMEOUT)

The query was for the SRV record for _ldap.tcp.dc_msdcs.%domainname%

The DNSservers used by this computer for name resolution are not responding.
This computer is configured to use DNS servers wit the following IP
addresses:

???.???.???.???

Verify that this computer is connected to the network, that these are the
correct DNS server IP addresses, and that at least one of the DNS servers is
running.


From the client PC we can ping the DNS server via IP address and host name.
Also, DNS and WINS are running on the server. Please help!!!!!
 
Usually this means you DNS server is wrong (or maybe
the client DNS settings -- DCs are DNS clients TOO!)

DNS
1) Dynamic for the zone supporting AD
2) All internal DNS client NIC\IP properties must specify SOLELY
that internal, dynamic DNS server (set.)
3) DCs and even DNS servers are DNS clients too -- see #2

Restart NetLogon on any DC if you change any of the above that
affects a DC.

People forget to make the DC a client of the DNS server (frequently
itself) and then it never registers in the DNS.

Or people try to use multiple -- internal AND EXTERNAL (wrong)
-- DNS servers in the client NIC settings and that doesn't work
RELIABLY either.

Internal only, DCs are DNS clients too -- usually DNS servers are
too.
 
Hi Herb

The DNS on the client PC is set to that of the DNS server, and that only.
The DNS servers DNS is set to servers IP address as well. The IP address
for both the client and server are static. The three options (003, 006 and
015) have been setup correctly.We have run dcdiag /c /v, netdiag /v? and
netdiag /fix and they have run just fine. I have looked in the DNS MMC have
all four subfolders, with all their content as well. Netlogon has been
stopped and restarted after any changes. Any other ideas? Getting desperate
now!!

cheers

Ste
 
Ste said:
Hi Herb

The DNS on the client PC is set to that of the DNS server, and that only.
The DNS servers DNS is set to servers IP address as well. The IP address
for both the client and server are static. The three options (003, 006 and
015) have been setup correctly.We have run dcdiag /c /v, netdiag /v? and
netdiag /fix and they have run just fine. I have looked in the DNS MMC have
all four subfolders, with all their content as well. Netlogon has been
stopped and restarted after any changes. Any other ideas? Getting desperate
now!!
Click to expand...


Are you saying that DCDiag come out clean with NO
"WARNING", "ERROR", or "FAIL" messages?
(Send to a text file and search it.)

Do all of your machines have the "domain name" specified
in their System control panel?

Does your Domain name have at LEAST 2-tags, e.g., "domain.com"
but NOT just "domainname".
 
Back
Top