Remote Assistance connection to a Windows Direct Access client computer fails

Symptoms

Consider the following scenario:
  • You configure a Windows Server 2012-based Direct Access server to use the IP over HTTPS (IP-HTTPS) protocol as the mode of Direct Access connectivity.
  • You assign an IP version 6 (IPv6) prefix for Direct Access client computers. For example, you assign a "2001:FFFF:a::123/64" prefix for the client computers.
  • You push the Direct Access settings to a Windows 8.1, Windows 8, or Windows 7 Service Pack (SP1)-based client computer.
  • You deploy Intra-Site Automatic Tunnel Addressing Protocol (ISATAP) or native IPv6 connectivity for an internal client computer in the corporate network.
  • You establish a Direct Access connection, and you make sure that the Direct Access Manage Out connectivity works.
  • On the internal client computer, you run the following command, and then you type the name of the Windows 8.1, Windows 8, or Windows 7 SP1-based client computer in the Windows Remote Assistance dialog box:
    msra /offerra 
In this scenario, the Remote Assistance connection fails.

Resolution

To resolve this issue for Windows 8.1, install update 2919355.
To resolve this issue for Windows 8 and Windows 7, install the hotfix that is described in this article.

Update information for Windows 8.1

For more information about how to obtain update 2919355, click the following article number to view the article in the Microsoft Knowledge Base:
2919355 Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2 Update April, 2014

Hotfix information for Windows 8 and Windows 7

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 website: 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 be running Windows 8 or Windows 7 SP1.

For more information about how to obtain a Windows 7 or Windows Server 2008 R2 service pack, click the following article number to view the article in the Microsoft Knowledge Base:

976932 Information about Service Pack 1 for Windows 7 and for Windows Server 2008 R2

Registry information

To apply this hotfix, you do not have to make any changes to the registry.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.
File information

Status

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

More Information

For more information about software update terminology, 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

Additional file information
Vlastnosti

ID článku: 2912883 – Posledná kontrola: 10. 3. 2016 – Revízia: 1

Pripomienky