Click Select Users. Click Add. Step 2 -- Remotely Connect to Another Computer 1. Click Start Control Panel. Click on System and Security. Click on Windows Firewall. Click OK. We love feedback! Please Help us improve this article. 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. Public profile The Remote Assistance exception is disabled by default and no inbound Remote Assistance traffic is permitted. Windows Firewall is configured this way by default to better protect users in a public networking environment such as a coffee shop or airport terminal. Domain profile The Remote Assistance exception when the computer is in a domain environment is geared toward the Offer RA scenario.
This exception is enabled by default in Windows 7 and is typically managed via Group Policy. Table summarizes the state of the Remote Assistance firewall inbound exception for each type of network location. The Remote Assistance exception has outbound properties as well; however, outbound exceptions are not enabled in Windows Firewall by default.
When a User consents to having a Helper share control of her computer during a Remote Assistance session, the User has the option of allowing the Helper to respond to UAC prompts Figure Typically, UAC prompts appear on the Secure Desktop which is not remoted , and consequently the Helper cannot see or respond to Secure Desktop prompts.
The User must provide consent to a UAC prompt to return to her normal desktop and continue working. This consent requires either clicking Continue if the user is a local administrator on her computer or by entering local administrative credentials if she is a standard user on her computer.
Enforcing this limitation is essential to ensure the security of Windows 7 desktops. Remote Assistance can generate a session log of Remote Assistance-associated activity.
Session logging is enabled by default and consists of timestamped records that identify Remote Assistance-related activities on each computer. Session logs only contain information about activities that specifically relate to Remote Assistance functionality, such as who initiated the session, if consent was given to a request for shared control, and so on. Session logs do not contain information on actual tasks that the User or Helper performed during a session. Session logs do include any chat activity performed during a Remote Assistance session.
The log generated during a session is also displayed within the chat window so that both the User and the Helper can see what is being logged during the session. Session logs also include any file transfer activity that occurs during the session, and they also record when the session has been paused. Session logs for Remote Assistance are mainly intended for enterprises that are required to maintain records of system and user activity for record-keeping purposes. A typical environment in which session logging might be required would be in a banking environment, where a financial institution is required by law to maintain records of who accessed a computer and at what time.
The logs created on each side of a Remote Assistance session are similar but not identical. In an enterprise environment, Group Policy can be used to enable or disable session logging.
If session logging is not configured using Group Policy, both the User and Helper are free to disable session logging on their own computers. Session logs are XML-formatted documents so that they can be easily integrated into other data sets—for example, by importing them into a database managed by Microsoft SQL Server A unique session log file is created for each Remote Assistance session on the computer. For example, a session log created at P.
The main Remote Assistance scenario within a corporate networking environment is supporting desktop computers that are on the corporate network and joined to a domain. Additionally, the Remote Assistance exception in the Windows Firewall must be enabled. For more information, see the section titled "Remote Assistance and Windows Firewall" earlier in this chapter. Because most corporate networks have a perimeter firewall blocking access from outside the internal network, supporting remote users who are connecting from outside the corporate network can be more difficult.
However, most enterprises now use virtual private network VPN technologies to allow remote users to connect to their corporate networks over the Internet, and this kind of scenario generally poses no problem to Remote Assistance functionality. The standard approach to using Remote Assistance in an enterprise environment is for Help Desk personnel to offer Remote Assistance to users who telephone to request assistance. A typical scenario might be as follows:. User Jane Dow the User is having problems configuring an application on her computer.
She phones Help Desk, explains her problem briefly, and asks for help. She responds with the information, which she can get from computer properties or by running ipconfig.
Jane then explains the problem she is having, either by using the Chat feature of Remote Assistance, or more likely over the telephone.
Jacky asks Jane to perform a series of steps to correct the problem and watches her screen in his own Remote Assistance window as she does this.
If the instructions Jacky provides are too complex or if time is limited, Jacky can ask Jane if he can share control of her computer. Jacky then proceeds to perform the steps needed to resolve the problem, either correcting the issue or demonstrating to Jane how to fix the problem if it occurs again in the future. If at any time Jane wants to force Jacky to relinquish control of her computer, she can click the Stop Sharing button or the Disconnect button, or she can press the Panic key Esc.
Hands-on experience with projects ranging from small to enterprise-level companies, starting from the communication with the customers and ending with the transformation of business requirements to the final deliverable. Passionate G r eek with experience in digital analytics projects and website implementation. Panagiotis Tzamtzis. Execute the file install. You should see a screen similar to the one below, if everything works fine. After the end of the patching process the remote desktop connection of your pc provides multi-user support.
Sign up to receive updates about new posts!
0コメント