Vista and windows 7 remote assistance

Standard users cannot start the services if they are not enabled. Each can be used to start, stop, and configure remote sessions, including service starts, the opening or bypass of firewall rules, remote function management, and offering remote assistance.

Command line tools, however, are not designed to establish permanent services states for remote access tools. If Remote Desktop or Remote Assistance will be regularly used by support staff, then automatic delayed states should be set for each desired service. Enable the desired remote support programs or features through the Windows or other firewall applications. A standard user should be able to allow Remote Assistance and Remote Desktop features through the standard Windows firewall without a need to understand the firewall ports.

If you are supporting a mixed platform environment, you may need to configure your firewall settings for the range of above ports on both sides of the connection. Choosing this option would either leave the related ports open using an allow rule or closed using a block rule. This would require administrative level rights to change settings, rights the standard user would not likely have in time of need. Windows Firewall with Advanced Security could be controlled through Group Policy, although a policy change to affect an open port is not a timely solution should remote connectivity be desired.

For enhanced security, Windows Firewall with Advanced Security could be configured using connectivity rules, tunneling, or advanced authentication in conjunction with remote connection filters. To launch Windows Remote Assistance, type MSRA in the search line and tap enter or right click and select run as administrator for elevated permissions. 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:. If you do not see your language, it is because a hotfix is not available for that language. For more information about how to obtain a Windows Vista service pack, click the following article number to view the article in the Microsoft Knowledge Base:.

The English United States version of this hotfix installs files that have the attributes that are listed in the following tables. These clouds correspond to two different scopes of IPv6 addresses:. Global cloud Any given computer will be connected to a single Global cloud. In networks where computers do not have IPv6 Internet connectivity but still have Global IPv6 addresses such as firewalled corporate environments , the Global cloud is network-wide.

Link-local clouds One or more clouds, each corresponding to nodes within the same subnet or network link link-local addresses and the link-local address scope. Note that Remote Assistance only uses the Global Internet-wide cloud; link-local clouds are not used by Remote Assistance.

Peer names can be computers, users, devices, groups, services, or anything that can be identified by an IPv6 address and port.

When the issuing peer wants to resolve the name of the targeted peer to its published address and port number, it follows these steps:. The issuing peer first consults its own PNRP cache for this information. If it finds this information, it sends a PNRP Request message to the targeted peer and waits for a response. These Request messages serve the function of enabling peers to communicate to other peers their active involvement within the cloud.

If the issuing peer does not find this information, it sends the Request message to the peer whose ID most closely matches that is, is closest numerically to that of the targeted peer. The peer that receives this message then consults its own cache. If it finds a closer match or the match itself, it returns this information to the requesting peer.

The requesting peer then goes to the returned peer and the process continues until the resolution succeeds or fails. If the peer that receives this message does not find closer information in its cache, it returns the message to the issuing peer, indicating that it does not know the targeted peer.

The issuing peer then repeats the previous step by sending a message to the peer whose ID next most closely matches that of the targeted peer. This process continues until the targeted peer is found if present on the network or not found if no longer present within the cloud. Looping is prevented by including in the Request message the list of peers that have already forwarded requests. The Helper has offered Remote Assistance to the User, but the User has not yet agreed to allow the Helper to connect to his computer.

The User has sent the Helper an invitation but the Helper has not yet responded by opening the invitation, or the Helper has opened the invitation and the User has not yet agreed to allow the Helper to connect to his computer. After the Remote Assistance application has been started and is running in the Waiting For Connect state, the application should not be closed until the other party responds and establishes the connection.

Screen Sharing This state occurs when the User has consented to allow the Helper to connect to his computer—either after the User has sent the Helper an invitation or the Helper has offered Remote Assistance to the User. This warning message is customizable using Group Policy. After a Remote Assistance connection has been established and both computers have entered the Screen Sharing state, the User and Helper are able to perform the tasks listed in Table One challenge this poses is that it can be difficult to establish P2P connections if one or both of the computers involved are behind a gateway or router that uses NAT.

NAT is typically used to map a set of private IP addresses to a single public IP address or to multiple public addresses. Home networks using a wireless or wired router also use NAT technology. To overcome this difficulty, Windows 7 and Windows Vista include built-in support for Teredo, an IPv6 transition technology described in RFC that provides address assignment and automatic tunneling for unicast IPv6 connectivity across the IPv4 Internet.

For most small business and home user environments, Remote Assistance in Windows 7 and Windows Vista will seamlessly traverse a NAT-enabled router with no additional router configuration required. For information on enterprises that need to remotely support users who work from home, see the section titled "Other Possible Remote Assistance Usage Scenarios" later in this chapter.

Beginning with Windows 7, Remote Assistance can also connect across certain types of symmetric NATs, but only if the other computer is not behind a symmetric NAT as well. Remote Assistance will not work if the NAT-enabled router is configured to block the specific ports used by Remote Assistance.

See the section titled "Remote Assistance and Windows Firewall" later in this chapter for more information. To determine the type of NAT a network is using, open an elevated command prompt and type netsh interface teredo show state.

For more information on IPv6 support in Windows 7, including built-in client support for Teredo and other IPv6 transition technologies, see Chapter The ports used by a Remote Assistance session depend on which version of Windows is running on the two computers involved in the session. The Windows Firewall is configured with a group exception for Remote Assistance.

This group exception has multiple properties that are grouped together as part of the Remote Assistance exception. The Remote Assistance exception properties will change depending on the network location of the computer private, public, or domain.

For example, the default Remote Assistance exception when the computer is in a public location is stricter than when the computer is in a private location.

In a domain-based enterprise environment, the Remote Assistance exception is typically managed using Group Policy and is enabled by default in Windows 7; it was disabled by default in Windows Vista.

The default configuration of the Remote Assistance exception in Windows Firewall varies depending on the firewall profile. Specifically, note the following:. Private profile The Remote Assistance exception in the Windows Firewall is enabled by default when the computer location is set to Private.

It is configured for NAT traversal using Teredo by default so that users in a private networking environment for example, the home environment can solicit help from other users who may also be behind NATs.

This profile also includes exceptions needed for PNRP. When using Remote assistance in windows 7 it shows a list albeit a small one of past addresses ip or computername that you have logged into. Is there a registry setting I can change so it will show me this History in chronological order? As far as my knowledge, there is no such changes that you can do in the registry of your system. You might not get the past addresses in chronological order. Although you can ….

Unfortunately that link is for Remote Desktop connection and not Remote Assistance. With windows XP it would list the history for Remote assistance connections on chronological order, now with Windows 7 it seems to do it in Alphabetical order.

Thank you for the help.