Article ID: 331627
Article Last Modified on 2/1/2007
APPLIES TO
- Microsoft Windows 2000 Service Pack 1
- Microsoft Windows 2000 Service Pack 2
- Microsoft Windows 2000 Service Pack 3
- Microsoft Windows 2000 Advanced Server
- Microsoft Windows 2000 Advanced Server
- Microsoft Windows 2000 Advanced Server
- Microsoft Windows 2000 Service Pack 1
- Microsoft Windows 2000 Service Pack 2
- Microsoft Windows 2000 Service Pack 3
This article was previously published under Q331627
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 fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem. This fix may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next Windows 2000 service pack that contains this hotfix.
To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:
NOTE: In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The typical support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
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:
- Start the Group Policy snap-in.
- In the left pane, expand the Computer Configuration branch, expand the Administrative Templates branch, expand the System branch, and then click the Logon branch.
- In the right pane, double-click Log users off when roaming profile fails.
- 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.
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
Keywords: kbbug kbfix kbwin2000presp4fix kbqfe kbtermserv kbwin2ksp4fix kbhotfixserver KB331627