Re: PC's join domain to remote site DC's

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Glenn L (the.only(delete)_at_gmail.com)
Date: 11/06/04


Date: Fri, 5 Nov 2004 19:52:59 -0800

When a computer joins the domain, it does not know which site it belongs to.
It queries for _LDAP._TCP.DS._MSDCS.domainname.com

Every DC registers this record, and the DNS server will reply with a
randomized list of all the DCs in the domain.
The client then picks the first one in the list to connect to and join the
domain.
This DC could conceivably be on the other side of the planet.
The only way to control this behavior is to use the priority and weight
fields on the LDAP records.
You would increase the priority and weight for the DC you want computers to
use when joining the domain.

Then when the client qeries the LDAP record, the DNS server will order the
reply based on priority and weight.
The record with the highest priority will then be used when joining the
domain.

-- 
Glenn L
CCNA, MCSE (2000,2003) + Security
"conundrum" <conundrum@discussions.microsoft.com> wrote in message 
news:3F8AA67C-762B-4C41-96DE-6CFA94B40520@microsoft.com...
> Ryan,
>
> Sorry. I guess I didn't do a good job of explaining the issue.
>
> The new pc's at the host site are currently joining the domain to a remote
> site DC.
>
> They should be joining the domain to one of the available host site DC's.
>
> I don't know why this is happening. So far, I've checked my sites and
> services/subnetting, and DNS.
>
> Sorry for the confusion.
>
>
>
> "Ryan Hanisco" wrote:
>
>> When joining workstations to a domain, the workstation needs to be able 
>> to
>> access domain resources that are not being hosted by your remote DCs. 
>> These
>> would be things like the PDC Emulator and RID Master.  This behavior is 
>> to
>> be expected.
>>
>> For that join, they will need to talk to the domain masters, after that,
>> they should be able to authenticate locally.  Take a  look at your FSMO 
>> Role
>> placement and see if that makes sense.  Otherwise post back and we can 
>> look
>> at other things.
>>
>> Ryan Hanisco
>> MCSE, MCDBA
>> Flagship Integration Services
>>
>> "conundrum" <conundrum@discussions.microsoft.com> wrote in message
>> news:7E48FC6C-0153-4435-9AF2-F30DA26B3219@microsoft.com...
>> > When joining a pc to the domain at the host site, the accepting DC ends 
>> > up
>> > being a DC at a remote-site.
>> >
>> > I have 3 DC's at my host site, and only 1 at each remote.
>> >
>> > I'm using Sites and Services, and have setup all my  locations with
>> Subnets.
>> >
>> > I also checked the DNS in Active Directory at the host site.
>> >
>> > Any ideas?
>>
>>
>> 


Relevant Pages

  • Re: PCs join domain to remote site DCs
    ... It sends a query for the following record in DNS. ... > The new pc's at the host site are currently joining the domain to a remote ... > They should be joining the domain to one of the available host site DC's. ...
    (microsoft.public.win2000.active_directory)
  • Re: PCs join domain to remote site DCs
    ... They should be joining the domain to one of the available host site DC's. ... > would be things like the PDC Emulator and RID Master. ... >> I also checked the DNS in Active Directory at the host site. ...
    (microsoft.public.win2000.active_directory)
  • Re: PCs join domain to remote site DCs
    ... You would increase the priority and weight for the DC you want computers to ... Then when the client qeries the LDAP record, the DNS server will order the ... The record with the highest priority will then be used when joining the ... > They should be joining the domain to one of the available host site DC's. ...
    (microsoft.public.win2000.active_directory)
  • Re: Adding Windows Vista SP1 to AD on Windows Server 2003
    ... My FQDN is siudek.info bu I've alweays used only siudek. ... And joining Win XP Pro works this way, but when I try to connect Vista I ... you probably have a DNS problem. ...
    (microsoft.public.windows.server.active_directory)
  • Re: UNC access failure: Logon Failure: The target account name is
    ... > which the ethernet cable was connected, deleted any references in DNS ... > and AD and swapped between being in a Workgroup and joining my domain ...
    (microsoft.public.win2000.dns)