Help and Support
 

powered byLive Search

You cannot log on to a domain controller from a Windows 2000 Terminal server in a WINS environment

View products that this article applies to.
Article ID:840689
Last Review:October 26, 2007
Revision:1.4
On This Page

SYMPTOMS

When you try to log on to a domain controller from a Microsoft Windows 2000 Server-based computer that has Terminal Services enabled, the operation is unsuccessful. Additionally, your roaming profile may not be loaded, and your home drive may not be mapped.

Back to the top

CAUSE

A Windows 2000 Terminal server depends on NetBIOS name resolution to locate a domain controller and to find these attributes on the user account. The issue that is described in the "Symptoms" section occurs if Windows Internet Name Service (WINS) is not configured, and therefore the Terminal server cannot reach a domain controller through a broadcast.

Back to the top

RESOLUTION

To resolve this issue, use one of the following methods.

Back to the top

Method 1

Set up and install WINS, and make sure that all domain controllers are registered. If WINS is already installed, follow these steps on the Terminal server and on the domain controllers:
1.Click Start, and then click Run.
2.Type nbtstat -RR, and then press ENTER.

Back to the top

Method 2

Install an LMHOSTS file on the Terminal server if you cannot configure WINS in your environment. For additional information about how to create an LMHOSTS file and add a domain name, click the following article number to view the article in the Microsoft Knowledge Base:
180094 (http://support.microsoft.com/kb/180094/) How to write an LMHOSTS file for domain validation and other name resolution issues

Back to the top

MORE INFORMATION

When this issue occurs, the following information is logged to the Userenv.log file on the Terminal server:
USERENV(f00.8d0) 16:17:33:171 =========================================================
USERENV(f00.8d0) 16:17:33:187 LoadUserProfile: Entering, hToken = <0xa4>, lpProfileInfo = 0x6f64c
USERENV(f00.8d0) 16:17:33:187 LoadUserProfile: Entering, hToken = <0xa4>, lpProfileInfo = 0x6f64c
USERENV(f00.8d0) 16:17:33:187 LoadUserProfile: lpProfileInfo->dwFlags = <0x0>
USERENV(f00.8d0) 16:17:33:203 LoadUserProfile: lpProfileInfo->lpUserName = <user>
USERENV(f00.8d0) 16:17:33:203 LoadUserProfile: NULL central profile path
USERENV(f00.8d0) 16:17:33:218 LoadUserProfile: lpProfileInfo->lpDefaultPath = <\\ROOTDC\netlogon\Default User>
USERENV(f00.8d0) 16:17:33:218 LoadUserProfile: NULL server name
If you monitor the network traffic from the Terminal server, you may see the following traffic: 
NBT NS: Query req. for DomainController <00> 192.0.0.1 172.21.4.128 IP
The WINS server may respond as follows: 
NBT NS: Query (Node Status) resp. for Domain Controller <00>, Requested name doesn't exist 192.0.0.1 172.21.4.67 IP
If WINS is not configured, the Terminal server sends out a broadcast for the domain controller.

Back to the top

REFERENCES

For additional information about WINS, visit the following Microsoft Web sites:
http://technet.microsoft.com/en-us/library/Bb742607.aspx (http://technet.microsoft.com/en-us/library/Bb742607.aspx)
For additional information about how two computers communicate in a WINS environment, click the following article number to view the article in the Microsoft Knowledge Base:
139608 (http://support.microsoft.com/kb/139608/) SMB traffic during Windows NT domain logon
185786 (http://support.microsoft.com/kb/185786/) Recommended practices for WINS

Back to the top

APPLIES TO
•Microsoft Windows 2000 Advanced Server
•Microsoft Windows 2000 Server

Back to the top

Keywords: 
kbwinservnetwork kbnetwork kbprb KB840689

Back to the top

Article Translations

 

Related Support Centers

Other Support Options

  • Need More Help?
    Contact a Support professional by Email, Online or Phone.
  • Customer Service
    For non-technical assistance with product purchases, subscriptions, online services, events, training courses, corporate sales, piracy issues, and more.
  • Newsgroups
    Pose a question to other users. Discussion groups and Forums about specific Microsoft products, technologies, and services.