| Author | Messages | |
ZJORZ
Posts:131
 | | 10/18/2007 9:22 AM |
| FYI
If you have configured your branch office DCs to not register domain-wide specific records, the clients will use those DCs and fail over to the datacenter if the local DC becomes unavailable. However if the local DC comes back online the client keeps using the datacenter DC until the client is restarted or the datacenter DCs become unavailable for some reason. This article provides hotfixes for both XP and 2003 and a registry key that allows the configuration of an interval for discovery.
-------
The domain controller locator cannot find an appropriate domain controller on a computer that is running Windows XP or Windows Server 2003
http://support.microsoft.com/kb/939252
SYMPTOMS
loadTOCNode(1, 'symptoms');
On a computer that is running Windows XP or Windows Server 2003, the domain controller locator cannot find an appropriate domain controller.For example, the computer may select out-of-site domain controllers to service authentication, LDAP, and other domain controller-specific requests even when in-site domain controllers exist. Or, the computer may send authentication, LDAP, and other domain controller-specific requests to several domain controllers instead of evenly balancing the load across the pool of available domain controllers.
Back to the top
CAUSE
loadTOCNode(1, 'cause');
The domain controller locator in Windows XP and in Windows Server 2003 caches the name of a single domain controller. This client cache is not updated until the targeted domain controller stops responding to locator requests or until the client is restarted. Therefore, the client continues to send domain controller requests to the cached domain controller. -------
http://blogs.dirteam.com/blogs/jorge/archive/2007/06/30/dc-locator-process-in-w2k-w2k3-r2-and-w2k8-part-1.aspxhttp://blogs.dirteam.com/blogs/jorge/archive/2007/07/02/dc-locator-process-in-w2k-w2k3-r2-and-w2k8-part-2.aspx
http://blogs.dirteam.com/blogs/jorge/archive/2007/07/02/dc-locator-process-in-w2k-w2k3-r2-and-w2k8-part-3.aspx
Met vriendelijke groeten / Kind regards,
Ing. Jorge de Almeida Pinto
Senior Infrastructure Consultant
MVP Windows Server- Directory Services
LogicaCMG Nederland B.V. (BUISA Eindhoven)
(Tel : +31-(0)40-29.57.777
(Mobile: +31-(0)6-26.26.62.80
* E-mail:
This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you. | | | |
| gabriel/tfi
Posts:192
| | 10/28/2007 7:56 AM |
| v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
Very
usefull! Expecially for servers at remote sites that are seldomly restarted. –
regards. Gabriele.
From:
ActiveDir-owner@mail.activedir.org [mailto:ActiveDir-owner@mail.activedir.org] On
Behalf Of Almeida Pinto, Jorge de
Sent: giovedì 18 ottobre 2007 15.22
To: ActiveDir@mail.activedir.org
Subject: [ActiveDir] DC Locator Process UPDATE (MS-KBQ939252)
FYI
If you have configured your branch office DCs to not register
domain-wide specific records, the clients will use those DCs and fail over to
the datacenter if the local DC becomes unavailable. However if the local DC
comes back online the client keeps using the datacenter DC until the client is
restarted or the datacenter DCs become unavailable for some reason. This
article provides hotfixes for both XP and 2003 and a registry key that allows
the configuration of an interval for discovery.
-------
The domain controller locator cannot find an appropriate domain
controller on a computer that is running Windows XP or Windows Server 2003
http://support.microsoft.com/kb/939252
SYMPTOMS
On
a computer that is running Windows XP or Windows Server 2003, the domain
controller locator cannot find an appropriate domain controller.
For example, the computer may select out-of-site domain controllers to service
authentication, LDAP, and other domain controller-specific requests even when
in-site domain controllers exist. Or, the computer may send authentication,
LDAP, and other domain controller-specific requests to several domain
controllers instead of evenly balancing the load across the pool of available
domain controllers.
Back to the top
CAUSE
The
domain controller locator in Windows XP and in Windows Server 2003 caches the
name of a single domain controller. This client cache is not updated until the
targeted domain controller stops responding to locator requests or until the
client is restarted. Therefore, the client continues to send domain controller
requests to the cached domain controller.
-------
http://blogs.dirteam.com/blogs/jorge/archive/2007/06/30/dc-locator-process-in-w2k-w2k3-r2-and-w2k8-part-1.aspx
http://blogs.dirteam.com/blogs/jorge/archive/2007/07/02/dc-locator-process-in-w2k-w2k3-r2-and-w2k8-part-2.aspx
http://blogs.dirteam.com/blogs/jorge/archive/2007/07/02/dc-locator-process-in-w2k-w2k3-r2-and-w2k8-part-3.aspx
Met vriendelijke groeten / Kind regards,
Ing. Jorge de Almeida Pinto
Senior Infrastructure Consultant
MVP Windows Server- Directory Services
LogicaCMG Nederland B.V. (BUISA Eindhoven)
( Tel : +31-(0)40-29.57.777
( Mobile : +31-(0)6-26.26.62.80
* E-mail :
This
e-mail and any attachment is for authorised use by the intended recipient(s)
only. It may contain proprietary material, confidential information and/or be
subject to legal privilege. It should not be copied, disclosed to, retained or
used by, any other party. If you are not an intended recipient then please
promptly delete this e-mail and any attachment and all copies and inform the
sender. Thank you. | | | |
|
|