Article ID: 922499 - Last Review: October 11, 2007 - Revision: 2.5 You cannot connect a terminal server client to a Windows Server 2003-based terminal serverOn This PageSYMPTOMSConsider the following scenario. You
have a terminal server
client that obtains a license from a Terminal Server license server. You try
to connect
the terminal server
client to a Microsoft Windows Server 2003-based
terminal server. However, you cannot establish the connection.
Additionally, the following event may appear in the Application log:
Event ID: 1028 Event Source: TermService Event Type: Information Description: The terminal server client <client name> has been disconnected because its license could not be renewed. RESOLUTIONService pack informationTo resolve this problem, obtain the latest service pack for Windows Server 2003. For more information, click the following article number to view the article in the Microsoft Knowledge Base:889100
(http://support.microsoft.com/kb/889100/
)
How to obtain the latest service pack for Windows Server 2003 Hotfix informationPrerequisitesBecause of file dependencies, this hotfix requires Windows Server 2003.Restart requirementYou must restart the computer after you apply this hotfix.Hotfix replacement informationThis hotfix replaces the KB 905687 hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:905687
(http://support.microsoft.com/kb/905687/
)
A Windows Server 2003-based terminal server in a forest cannot obtain a license from a license server in a different forest
File informationThe 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, x86-based versionsCollapse this table
Windows Server 2003 with Service Pack 1, x86-based versionsCollapse this table
Windows Server 2003, x64-based versionsCollapse this table
Windows Server 2003, IA-64-based versionsCollapse this table
Windows Server 2003 with Service Pack 1, IA-64-based versionsCollapse this table
STATUSMicrosoft
has confirmed that this is a problem in the Microsoft products that are listed
in the "Applies to" section. This problem was first corrected in Windows Server 2003 Service Pack 2. APPLIES TO
| Article Translations
|
Back to the top
