A Windows Server 2003-based terminal server that is added to the Terminal Services Computers group cannot obtain a license from a terminal licensing server that has the "License server security group" setting enabled

Consider the following scenario.

• On a Windows Server 2003-based terminal licensing server, you enable the Licensing server security group Group Policy setting. This automatically creates a Terminal Services Computers group on the terminal licensing server.
• You add a Windows Server 2003-based terminal server to the Terminal Services Computers group.
• You have installed hotfix 905687 on both the terminal licensing server and the terminal server.

In this scenario, the terminal server may be unable to obtain a license from the terminal licensing server. This issue occurs more frequently on terminal servers that use Gigabit Ethernet network adapters.

After the Licensing server security group Group Policy setting is enabled, the terminal licensing server requires credentials from the terminal server to establish a connection. Additionally, the licensing server rejects connection requests if the terminal server uses an anonymous account to make connections.

After you install hotfix 905687, the terminal server may use an anonymous account to connect to the terminal licensing server. Therefore, the connection is rejected, and the terminal server cannot obtain a license from the terminal licensing server.

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 the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

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, contact 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: 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.

Prerequisites

To apply this hotfix, the computer must be running Windows Server 2003 Service Pack 1.

Restart requirement

You have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other previously released hotfixes. 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, x86-based versions

Windows Server 2003, x64-based versions

Windows Server 2003, Itanium-based versions

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

For more information about terminal servers and licensing servers, click the following article numbers to view the articles in the Microsoft Knowledge Base: For more information, click the following article number to view the article in the Microsoft Knowledge Base: