Incorrect client names may be displayed for redirected drives in Windows Server 2003 terminal server sessions if both Windows-based and Macintosh-based terminal server clients are used

Consider the following scenario:

• You create terminal server sessions to a Windows Server 2003-based computer.
• Your terminal server clients include both Windows-based and Macintosh-based clients.
• Drive redirection is enabled both on the terminal server and on the terminal server clients.
• You create a terminal server session from a Macintosh-based terminal server client. Then, you disconnect or log off the terminal server session. Later, you create a terminal server session from a Windows-based terminal server client.

In this scenario, you can access the data on the redirected drives. However, the display names for the redirected drives may include incorrect client names.

For example, you create a terminal server session from a Macintosh-based terminal server client that is named Mac1. Then, you disconnect the terminal server session. Later, you resume the same terminal server session from a Windows-based terminal server client that is named PC1. In this situation, the redirected drive C is displayed as "C on Mac1" instead of as "C on PC1."

This problem occurs because Terminal Services in Windows Server 2003 incorrectly maintains client display names.

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. 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, you must have Windows Server 2003 Service Pack 1 or Windows Server 2003 Service Pack 2 installed. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

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 with Service Pack 1, x86-based versions

Windows Server 2003 with Service Pack 2, x86-based versions

Windows Server 2003 with Service Pack 1, Itanium-based versions

Windows Server 2003 with Service Pack 2, Itanium-based versions

Windows Server 2003, x64-based versions

Windows Server 2003 with Service Pack 2, x64-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 software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.