RE: client logon with more than 1 DC

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Allen Firouz (AllenFirouz_at_discussions.microsoft.com)
Date: 01/21/05


Date: Fri, 21 Jan 2005 08:37:02 -0800

Hi Normail:

this question comes up in these board over and again. I am reposting an
answer that was given by Tomasz Onzyszko [MVP] a few days ago. It is well
stated:

...it is not possible on the client side - what You can try to do
is to modify server priority in the DNS SRV records for this DC:
http://www.microsoft.com/resources/documentation/Windows/2000/server/reskit/en-us/Default.asp?url=/resources/documentation/Windows/2000/server/reskit/en-us/distrib/dsbc_nar_sdns.asp
http://www.microsoft.com/resources/documentation/Windows/2000/server/reskit/en-us/Default.asp?url=/resources/documentation/Windows/2000/server/reskit/en-us/distrib/dsbc_nar_jevl.asp

Client should try to contact DC with the lowest priority

To force DC to register with specified priority in DNS see this tip:
http://www.jsiinc.com/SUBK/tip5100/rh5162.htm

-Allen Firouz [MentalFloss]

"nomail" wrote:

> Hi There !
>
> I've 3 w2k3standard servers in 3 different sites on a WAN. There's a
> domain and the three servers are DC.
>
> This is the problem: on clients logons are made by user on all
> servers, even the remote servers.
>
> I made this test on the same client:
> (logon)
> %LOGONSERVER%=server1 (local)
> ipconfig /flushdns
> nbtstat -R
> (restart client)
> (logon)
> %LOGONSERVER%=server2 (remote)
> ipconfig /flushdns
> nbtstat -R
> (restart client)
> (logon)
> %LOGONSERVER%=server3 (remote)
> ipconfig /flushdns
> nbtstat -R
> (restart client)
> (logon)
> %LOGONSERVER%=server1 (local)
> ipconfig /flushdns
> nbtstat -R
> (restart client)
>
> DNS and WINS server appears configured fine. Client TCP and LMHOSTS
> too. Roun Robin is disabled on all DNS servers.
>
> Any ideas ?
> Which is the way to force a client to logon on a specific DC ???
> Plz help me !!!
>
> Bye from Italy
>
>



Relevant Pages

  • Re: [fw-wiz] Defense in Depth to the Desktop
    ... > network hardware mechanisms. ... The Strong Internal Network Defense ... The client subnet and the server ... Servers are allowed to reply to clients, ...
    (Firewall-Wizards)
  • [fw-wiz] Defense in Depth to the Desktop
    ... network hardware mechanisms. ... controls is highlighted when the internal network and systems suffer ... The client subnet and the server ... Servers are allowed to reply to clients, ...
    (Firewall-Wizards)
  • Re: [fw-wiz] Defense in Depth to the Desktop
    ... Sounds a lot like Domain Based Security (not Windows 'domains', ... > network hardware mechanisms. ... The client subnet and the ... Servers are allowed to reply to clients, ...
    (Firewall-Wizards)
  • Re: What doesnt lend itself to OO?
    ... objects need to be explicitly maintained....thus the rise of stateless ... of state largely the responsibility of the client. ... object only exists on 1 out of n servers the load balancer needs to ...
    (comp.object)
  • Re: 1058 and 1030 errors revisited
    ... Are you sure about the symptoms ie when the11th or 12th user logs ... Does the issue occour only on some machines? ... We have four servers to ... There are about sixty client ...
    (microsoft.public.windows.group_policy)