This article was previously published under Q192064
This article has been archived. It is offered "as is" and will no longer be updated.
When a Windows NT 4.0 computer starts up, it normally queries WINS tolocate domain controllers that it can log on to. WINS does not have anyawareness of geographical locations of domain controllers, so, if a distantor low-bandwidth domain controller is selected, boot and logon times can beslow.
The starting computer queries WINS for the domain[1C] name list. WINSreturns a list of domain controllers, and the computer sends a datagram toeach of them (as well as a subnet broadcast for any domain controllers thathappen to be on the same subnet). The first DC to respond is chosen as theone to use for logging on.
NetBT has been modified to support multiple domain controller entries inthe LMHOSTS file. Entries can be added to specify preferred domaincontrollers to use when logging on. Entries must appear as shown here:
To take advantage of this new feature, LMHOSTS lookups must be enabled. Toenable LMHOSTS lookup, go to Control Panel->Network->Protocols->TCP/IP->properties->WINS addresses, and select the "Enable LMHOSTS Lookup"checkbox.
With the above LMHOSTS file entries, a computer would attempt to use the IPaddresses 10.1.1.1 and 10.1.1.2 to log on to the domain called mydomain.
To resolve this problem, obtain the latest service pack for Windows NT 4.0 or Windows NT Server 4.0, Terminal Server Edition. For additional information, click the following article number to view the article in theMicrosoft Knowledge Base:
152734 How to Obtain the Latest Windows NT 4.0 Service Pack
Microsoft has confirmed that this is a problem in Windows NT 4.0 and Windows NT Server 4.0, Terminal Server Edition. This problem was first corrected in Windows NT 4.0 Service Pack 4.0 and Windows NT Server 4.0, Terminal Server Edition Service Pack 4.