Is there another way in the firewall to open port ? Thanks EDIT: I forgot about being able to add a port under the exceptions tab of the firewall, but when I tried to open port it said it was already done by the Remote Desktop exception. Tuesday, April 10, PM. Having the same problem, and all forum I could find have not found solution. Now with Vista, I cant. I hope this is a bug, not a feature!! Sunday, May 13, AM. Hi, I realize that this post is old, but I've been searching for the reverse answer to this question.
Tuesday, June 19, AM. Monday, June 25, PM. Has anyone tried to install the following update in their XP computer? Tuesday, June 26, PM. Norris 0. Tuesday, July 3, PM. Thursday, August 2, PM. The last paragraph of the following is pertinent to the specific problem described, tho I have added other info for your perusal. Efficiency Improvements One way that Remote Assistance has been improved is that it is designed to be more efficient. Tuesday, March 18, AM.
Monday, March 24, PM. Hope this helps. Friday, March 28, PM. Wednesday, May 14, PM. Thursday, May 29, PM. Sunday, June 1, PM. Wednesday, June 4, PM. I'm experiencing the same problem i get vista to be host and on my pc from work i have xp sp Thursday, June 5, AM.
Windows XP can not provide remote assistance to Windows Vista. Thursday, July 31, PM. Just a guess. Sunday, April 12, AM. MsoNormal, li. MsoNormal, div. Tuesday, April 28, AM. Open Troubleshooting :. In Icon View, select Troubleshooting.
Windows will automatically create the invitation message, an encrypted " Invitation. Windows will automatically open a screen displaying the connection password. Tell CTI Support which email address you sent your invitation to, and the 12 character password in your Windows Remote Assistance pop-up screen. To allow a Remote Assistance connection, click here. To suspend, change or end a Remote Assistance connection, click here. Click Start. Click Next [or Finish]. 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. Expand your skills.
Get new features first. Was this information helpful? Yes No. Thank you! Any more feedback? The more you tell us the more we can help.
Can you help us improve?
0コメント