RESOLUTION
Hotfix information
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Windows Server 2003 service pack that contains this hotfix.
To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone 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 usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
Prerequisites
No prerequisites are required.
Restart requirement
You must restart the computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace any other hotfixes.
File information
The English version of this hotfix has the file attributes (or later file attributes) 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 item in Control Panel.Windows Server 2003, 32-bit x86-based versions
|
Mstlsapi.dll | 5.2.3790.385 | 106,496 | 10-Aug-2005 | 03:02 | x86 |
Windows Server 2003, 32-bit x86-based versions with Service Pack 1
|
Mstlsapi.dll | 5.2.3790.2505 | 118,272 | 10-Aug-2005 | 03:13 | x86 |
Windows Server 2003, 64-bit Itanium-based versions
|
Mstlsapi.dll | 5.2.3790.385 | 316,416 | 09-Aug-2005 | 13:09 | IA-64 | Not Applicable |
Wmstlsapi.dll | 5.2.3790.385 | 106,496 | 09-Aug-2005 | 13:09 | x86 | WOW |
Windows Server 2003, 64-bit Itanium-based versions with Service Pack 1
|
Mstlsapi.dll | 5.2.3790.2505 | 347,648 | 09-Aug-2005 | 13:09 | IA-64 | SP1 | Not Applicable |
Wmstlsapi.dll | 5.2.3790.2505 | 118,272 | 09-Aug-2005 | 13:09 | x86 | SP1 | WOW |
Windows Server 2003, 64-bit x64-based versions
|
Mstlsapi.dll | 5.2.3790.2505 | 190,976 | 09-Aug-2005 | 13:09 | x64 | SP1 | Not Applicable |
Wmstlsapi.dll | 5.2.3790.2505 | 118,272 | 09-Aug-2005 | 13:09 | x86 | SP1 | WOW |
WORKAROUND
To work around this problem, use either of the following methods.
Method 1
Install a Terminal Server license server in the same domain or forest as the Terminal Server that is requesting the license.
For more information about license server roles, visit the following Microsoft Web site:
For more information about where to install license servers for each role, visit the following Microsoft Web site:
Method 2
Create a forest trust that supports Kerberos authentication between the two forests.
For more information about forest trusts, visit the following Microsoft Web site: