Terminal Services Client Cannot Obtain Terminal Services User Configuration from Domain Controller During Logon

Article translations Article translations
Article ID: 331627 - View products that this article applies to.
This article was previously published under Q331627
Notice
This article applies to Windows 2000. Support for Windows 2000 ends on July 13, 2010. The Windows 2000 End-of-Support Solution Center is a starting point for planning your migration strategy from Windows 2000. For more information see the Microsoft Support Lifecycle Policy.
Expand all | Collapse all

On This Page

SYMPTOMS

When a Terminal Services client requests a Terminal Services user configuration from a domain controller that is under a heavy load, the domain controller may not respond to the request. When this occurs, the client uses the default profile path if one is defined.

RESOLUTION

Service Pack Information

To resolve this problem, obtain the latest service pack for Microsoft Windows 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
260910 How to Obtain the Latest Windows 2000 Service Pack

Hotfix Information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=support
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language. The English version of this fix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
   Date          Time    Version              Size   File name
   --------------------------------------------------------------
   25-Nov-2002   14:43   5.0.2195.5265      42,256   Basesrv.dll
   25-Nov-2002   14:43   5.0.2195.5907     222,992   Gdi32.dll
   25-Nov-2002   14:43   5.0.2195.6137     709,392   Kernel32.dll
   25-Nov-2002   14:43   5.0.2195.6090     332,560   Msgina.dll
   22-Nov-2002   18:03   5.0.2195.6129     146,432   Sp3res.dll
   25-Nov-2002   14:43   5.0.2195.6097     379,664   User32.dll
   25-Nov-2002   14:43   5.0.2195.6140     370,960   Userenv.dll
   22-Nov-2002   17:53   5.0.2195.6139   1,643,344   Win32k.sys
   25-Nov-2002   14:41   5.0.2195.6141     179,984   Winlogon.exe
   25-Nov-2002   14:43   5.0.2195.6097     243,472   Winsrv.dll
 

After you install this hotfix, if a domain controller does not respond to a client request for a user configuration, the client tries to rediscover a domain controller and resubmits the request for the terminal server user configuration.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Microsoft Windows 2000 Service Pack 4.

MORE INFORMATION

To prevent a user from logging on when a domain controller does not respond to the request for a user configuration (for example, a profile path), turn on the "Log users off when roaming profile fails" policy. To do so:

  1. Start the Group Policy snap-in.
  2. In the left pane, expand the Computer Configuration branch, expand the Administrative Templates branch, expand the System branch, and then click the Logon branch.
  3. In the right pane, double-click Log users off when roaming profile fails.
  4. Click Enabled, and then click OK.

NOTE: When the "Log users off when roaming profile fails" policy is turned on and the hotfix described in this article is installed, if a domain controller does not respond to a client request for a user configuration even after the client tries to rediscover a domain controller, the following event is logged in the Application event log, and the client does not obtain the user configuration from a domain controller.

Event Type: Error
Event Source: Userenv
Event Category: None
Event ID: 1219
Date: 10/30/2002
Time: 2:30:17 PM
User: user_name
Computer: computer_name
Description:
Login rejected for domain_name\user_name. Unable to obtain Terminal Server User Configuration. Error: <Description of the error>

For additional information about how to obtain a hotfix for Windows 2000 Datacenter Server, click the article number below to view the article in the Microsoft Knowledge Base:
265173 The Datacenter Program and Windows 2000 Datacenter Server Product

Properties

Article ID: 331627 - Last Review: February 1, 2007 - Revision: 3.11
APPLIES TO
  • Microsoft Windows 2000 Server SP1
  • Microsoft Windows 2000 Server SP2
  • Microsoft Windows 2000 Service Pack 3
  • Microsoft Windows 2000 Advanced Server SP1
  • Microsoft Windows 2000 Advanced Server SP2
  • Microsoft Windows 2000 Advanced Server SP3
  • Microsoft Windows 2000 Professional SP1
  • Microsoft Windows 2000 Professional SP2
  • Microsoft Windows 2000 Service Pack 3
Keywords: 
kbautohotfix kbhotfixserver kbqfe kbtermserv kbwin2ksp4fix kbbug kbfix kbwin2000presp4fix KB331627

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com