Microsoft KB Archive/886199

= You cannot redirect audio to a client computer when you are running a Remote Desktop Connection in Windows XP =

Article ID: 886199

Article Last Modified on 8/29/2007

-

APPLIES TO


 * Microsoft Windows XP Professional
 * Microsoft Windows XP Home Edition

-





SYMPTOMS
When you use the Remote Desktop Connection to log on to a Microsoft Windows XP Remote Desktop Protocol (RDP) 5.1-based or RDP 5.2-based client, and then you connect to a Windows XP-based remote host, audio redirection may not occur.

Note Audio redirection enables the client computer to receive any sound or audio that is played in the remote session. (This scenario assumes that the client computer has a working sound adaptor.)

For additional information about how to let users redirect audio in a Remote Desktop Connection session, click the following article number to view the article in the Microsoft Knowledge Base:

818465 How to use Group Policy to permit users to redirect and play audio in a Remote Desktop session to Terminal Services in Windows Server 2003



CAUSE
This problem may occur when a user logs on to a Remote Desktop Connection session with a different Windows XP user account than the previous user used. For example, user A may use audio redirection during a Remote Desktop Connection session and then log off the Windows XP-based computer. If user B uses a different account to log on to the same Windows XP-based computer, audio redirection will not work during the Remote Desktop Connection session.



RESOLUTION
A supported hotfix is now 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 service pack that contains this hotfix.

To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:

http://go.microsoft.com/?linkid=6294451

Note If additional issues occur or 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. To create a separate service request, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

Prerequisites
You must have Windows XP Service Pack 2 installed to apply this hotfix.

For additional information about how to obtain the latest Windows XP service pack, click the following article number to view the article in the Microsoft Knowledge Base:

322389 How to obtain the latest Windows XP service pack

Restart information
You do not have to restart your computer after you apply this hotfix.

Hotfix replacement information
This hotfix is not replaced by any later hotfix.

Hotfix 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 tool in Control Panel.

  Date         Time   Version        Size    File name -  06-Oct-2004  18:37  5.1.2600.2524  19,968  Rdpsnd.dll



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section.



MORE INFORMATION
For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates

Keywords: kbwinxppresp3fix kbwinxpsp3fix kbfix kbbug kbqfe kbhotfixserver KB886199

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.