Specify preferred login server ?

[Eric P]

Q192064 described a problem in NT4 domains which I will just copy and paste here because it is described eloquently (although you can substitute DNS for WINS):

Symptoms
When a Windows NT 4.0 computer starts up, it normally queries WINS to locate domain controllers that it can log on to. WINS does not have any awareness of geographical locations of domain controllers, so, if a distant or low-bandwidth domain controller is selected, boot and logon times can be slow.
Cause
The starting computer queries WINS for the domain[1C] name list. WINS returns a list of domain controllers, and the computer sends a datagram to each of them (as well as a subnet broadcast for any domain controllers that happen to be on the same subnet). The first DC to respond is chosen as the one to use for logging on.

I am running into the same issue in a mixed mode domain that I am steadily moving towards a pure native AD domain. All of the clients are Win2K Pro SP2. Does anyone have a way of specifying the preferred login server? It really slows down the login proccess (which includes fairly extensive login scripting via Script Logic)in another area code. I am basically dead in my tracks upgrading the servers at my branch offices until I have a fix for this.

TY!!

[Matt]

Hi Eric,

I use a couple of utilities to maintain secure connections (secure channels) between servers in different domains. It's basically so that if you are a member of domainX and travel to the site which contains domainY that you'll still be able to log on. It directs the domainY servers to a server that they should use to authenticate people from domainX

the utilities are :

nltest.exe &
setprfdc.exe

i think you should be able to use them. they can be used to create secure channels to any DC in a domain you (your pc/server) trusts.

Hope it helps!

Matt




------------
Eric P at 7/31/2002 1:29:43 PM

Q192064 described a problem in NT4 domains which I will just copy and paste here because it is described eloquently (although you can substitute DNS for WINS):

Symptoms
When a Windows NT 4.0 computer starts up, it normally queries WINS to locate domain controllers that it can log on to. WINS does not have any awareness of geographical locations of domain controllers, so, if a distant or low-bandwidth domain controller is selected, boot and logon times can be slow.
Cause
The starting computer queries WINS for the domain[1C] name list. WINS returns a list of domain controllers, and the computer sends a datagram to each of them (as well as a subnet broadcast for any domain controllers that happen to be on the same subnet). The first DC to respond is chosen as the one to use for logging on.

I am running into the same issue in a mixed mode domain that I am steadily moving towards a pure native AD domain. All of the clients are Win2K Pro SP2. Does anyone have a way of specifying the preferred login server? It really slows down the login proccess (which includes fairly extensive login scripting via Script Logic)in another area code. I am basically dead in my tracks upgrading the servers at my branch offices until I have a fix for this.

TY!!

[Eric P]

Unfortunately, not really. We are talking one big fat domain spread accross several different geograhic locations/subnets. I am trying to avoid overly complicating things by introducing subdomains, etc. Thanks for the tip though!


------------
Matt at 8/1/2002 10:28:41 AM

Hi Eric,

I use a couple of utilities to maintain secure connections (secure channels) between servers in different domains. It's basically so that if you are a member of domainX and travel to the site which contains domainY that you'll still be able to log on. It directs the domainY servers to a server that they should use to authenticate people from domainX

the utilities are :

nltest.exe &
setprfdc.exe

i think you should be able to use them. they can be used to create secure channels to any DC in a domain you (your pc/server) trusts.

Hope it helps!

Matt




------------
Eric P at 7/31/2002 1:29:43 PM

Q192064 described a problem in NT4 domains which I will just copy and paste here because it is described eloquently (although you can substitute DNS for WINS):

Symptoms
When a Windows NT 4.0 computer starts up, it normally queries WINS to locate domain controllers that it can log on to. WINS does not have any awareness of geographical locations of domain controllers, so, if a distant or low-bandwidth domain controller is selected, boot and logon times can be slow.
Cause
The starting computer queries WINS for the domain[1C] name list. WINS returns a list of domain controllers, and the computer sends a datagram to each of them (as well as a subnet broadcast for any domain controllers that happen to be on the same subnet). The first DC to respond is chosen as the one to use for logging on.

I am running into the same issue in a mixed mode domain that I am steadily moving towards a pure native AD domain. All of the clients are Win2K Pro SP2. Does anyone have a way of specifying the preferred login server? It really slows down the login proccess (which includes fairly extensive login scripting via Script Logic)in another area code. I am basically dead in my tracks upgrading the servers at my branch offices until I have a fix for this.

TY!!

[Eric P]

Found the answer...and the answer is to use sites. Q318480 explains. http://support.microsoft.com/default.aspx?scid=KB;EN-US;q318480&

Be careful...the documentation warns about deleting Default-First-Site...don't rename it either...same effect.

------------
Eric P at 7/31/2002 1:29:43 PM

Q192064 described a problem in NT4 domains which I will just copy and paste here because it is described eloquently (although you can substitute DNS for WINS):

Symptoms
When a Windows NT 4.0 computer starts up, it normally queries WINS to locate domain controllers that it can log on to. WINS does not have any awareness of geographical locations of domain controllers, so, if a distant or low-bandwidth domain controller is selected, boot and logon times can be slow.
Cause
The starting computer queries WINS for the domain[1C] name list. WINS returns a list of domain controllers, and the computer sends a datagram to each of them (as well as a subnet broadcast for any domain controllers that happen to be on the same subnet). The first DC to respond is chosen as the one to use for logging on.

I am running into the same issue in a mixed mode domain that I am steadily moving towards a pure native AD domain. All of the clients are Win2K Pro SP2. Does anyone have a way of specifying the preferred login server? It really slows down the login proccess (which includes fairly extensive login scripting via Script Logic)in another area code. I am basically dead in my tracks upgrading the servers at my branch offices until I have a fix for this.

TY!!