Exactly which DCs are contacted by the DsGetDcName command?

[Guest]

Archived from groups: microsoft.public.win2000.active_directory (More info?)

I found that a delayed replication last night prevented a domain controller
from being rebuilt and rejoined to the domain. I recieved error messages
stating the account existed in the domain, but we checked all of the DCs in
the local site, and turned up nothing. We attempted to join the domain, and
failed. I checked the netsetup.log file and found a DC from siteB found the
old domain controller, and failed the domain join. I forced replication
between siteA and siteB, and tried again. The attempt also failed, but this
time it was a DC in siteC. I forced replication between siteA and siteC, and
tried again. This attempt completed successfully, and the netsetup.log file
showed a local DC responded to the DsGetDcName command. It appeared my
attempt to join the server back to the domain contacted bridgehead servers in
all remote sites. Because of replication delays the bridgehead Dcs had not
gotten the remove DC from domain messages. This brought up my question:

"When joining a AD domain, exactly which DCs are contacted by the
DsGetDcName command?"

If available please provide Microsoft documentation links.

 

[Guest]

Archived from groups: microsoft.public.win2000.active_directory (More info?)

Basically the first DC to respond to a 'ping' sent by the client once it has
pulled info. on DCs from DNS.

Once this happens, the site is checked, and the DC is either used or
discarded. This info. is then cached. If the site is optimal, the cache is
kept; if it's not optimal, it's discarded after 15 mins and the process
happens again.

(That's overly simplified of course).


In addition to the article that Chris pointed out, there's a lot of info. on
this in the distributed systems guide.
--
http://www.microsoft.com/resources/documentation/Windows/2000/server/reskit/en-us/Default.asp?url=/resources/documentation/Windows/2000/server/reskit/en-us/w2rkbook/DistSystems.asp


--

Paul Williams

http://www.msresource.net
http://forums.msresource.net


"SCURRA" <SCURRA@discussions.microsoft.com> wrote in message
news:BCA82AC5-1ABA-4CC7-B51B-C582F91A99AE@microsoft.com...
I found that a delayed replication last night prevented a domain controller
from being rebuilt and rejoined to the domain. I recieved error messages
stating the account existed in the domain, but we checked all of the DCs in
the local site, and turned up nothing. We attempted to join the domain, and
failed. I checked the netsetup.log file and found a DC from siteB found the
old domain controller, and failed the domain join. I forced replication
between siteA and siteB, and tried again. The attempt also failed, but this
time it was a DC in siteC. I forced replication between siteA and siteC, and
tried again. This attempt completed successfully, and the netsetup.log file
showed a local DC responded to the DsGetDcName command. It appeared my
attempt to join the server back to the domain contacted bridgehead servers
in
all remote sites. Because of replication delays the bridgehead Dcs had not
gotten the remove DC from domain messages. This brought up my question:

"When joining a AD domain, exactly which DCs are contacted by the
DsGetDcName command?"

If available please provide Microsoft documentation links.