Remote Assistance Vista 6. Re: Remote Assistance Vista 6. I just solved the problem. It was that theinvitations were being sent as Vista only, and by luck of the draw the remotemachines were Windows 7 Beta and Windows 2.
Windows Vista Remote Assistance Router Port
When it workedinside, it was from a Vista machine. Now it works from the outside. Thanks."Robert L. MS- MVP)" wrote: > Can you telnet port 3. Bob Lin, MS- MVP, MCSE & CNE> Networking, Internet, Routing, VPN Troubleshooting on> http: //www. Chicago. Tech. net> How to Setup Windows, Network, VPN & Remote Access on> http: //www. How. To. Networking.
Larry Heimendinger" < > wrote in> message news..> > I have been unable to get a Remote Assistance invitation through a> > firewall/router to a destination machine. I opened ports 1. I also> > put the computer into the DMZ on the router and still no luck.> > > > I checked the software firewalls, and I remote assistance was enabled as> > an> > exception. To back that up read the next paragraph.> > > > However, if I use Remote Desktop to reach another computer on the same> > network (behind the firewalls), and use the SAME invitation file, the> > remote> > assistance connection works great.> > > > I opened the invitation with notepad, and I found this looking rather> > correct: > > > > RCTICKET="6. X. 2. 3X. 1. XX. XX7: 1. I modified the actual IP address by replacing some characters with X.> > However, the internal address looks fine.
Is that port 1. 55. Does remote assistance take some additional port handling I> > am> > not accounting for?> >.
I have been unable to get a Remote Assistance invitation through a firewall/router to a destination machine. I opened ports 135 and legacy 3389.
Supporting Users Using Remote Assistance (Part 1) : : Windows Vista : : Articles & Tutorials : : Windows. Networking. com. If you would like to read the other parts in this article series please go to: Windows Vista Resource Kit Chapter 2. Supporting Users Using Remote Assistance (Part 2)Windows Vista Resource Kit Chapter 2.
Supporting Users Using Remote Assistance (Part 3)Remote Assistance (RA) in Windows Vista includes a number of improvements in connectivity, performance, usability, and security along with feature enhancements that make it even more useful than RA in Windows XP. With increased Group Policy support, command- line scripting capabilities, session logging, bandwidth optimization, and more, Remote Assistance is now an essential tool for enabling enterprises to support users in Help Desk scenarios. This chapter examines how Remote Assistance works in Vista, how to use it to support end users, and how to manage it using Group Policy and scripts. Get the Windows Vista Resource Kit today! Understanding Remote Assistance Supporting end users is an essential function of IT departments and the corporate Help Desk.
You can use Windows Remote Assistance to connect to someone's computer and help that person with a computer problem, even if you're not nearby. Remote Desktop is disabled by default in Windows, but it’s easy enough to turn it back on. If you need to access your Windows PC from another box, it’s an. I have a novice running Vista Home Premium, behind a Linksys router that passed all of the Vista tests. When she creates a Remote Assistance invitation file, it does.
Windows Vista Remote Assistance Router Configuration
Unfortunately, conventional technical support provided over the telephone or using chat tools is generally cumbersome and inefficient. As a result, supporting users is often both time- consuming and costly for large enterprises to implement. For example, end users often have difficulty describing the exact nature of the problem they are having. Because of their general inexperience and lack of technical knowledge, end users may try to describe their problem using non- technical, inexact language. As a result, Help Desk personnel are generally reduced to asking a series of simple questions to try and isolate the problem the user is having. The methodical nature of these questions sometimes causes users to feel as if Help Desk personnel are being condescending, and such misunderstanding can reduce the effectiveness of the support experience and can make users tend to avoid contacting support personnel when future problems arise. End users also often have difficulty following instructions given to them by Help Desk personnel who are trying to assist them.
DLink DIR-655 router and Remote Assistance Windows Vista Networking & Sharing. Hi, If it's behind a router, then the invite contains the machine's local IP and not the one that is exposed to the outside world. You would need to edit the. Home; Articles & Tutorials; Windows Vista; Windows Vista Resource Kit Chapter 23: Supporting Users Using Remote Assistance (Part 1) by Mitch Tulloch [Published on. Remote Assistance Vista 64-bit - probable firewall/router issues. Discussion in 'Windows Vista Networking' started by Larry Heimendinger, Mar 2, 2009.
Well- trained support personnel will try to avoid using technical jargon when communicating with end users, but although using plain language can improve the support experience, it may also mean that resolution steps become long and tiresome. For example, telling a user how to use Disk Cleanup from System Tools in Accessories can require several sentences or more, and this kind of communication can add time to support incidents, making them more costly to the company.
Remote Assistance (RA) solves these problems by enabling support personnel to view the user’s desktop in real time. The user seeking assistance can demonstrate the nature of the problem to the support person. This is a quicker and more efficient way to communicate a problem than using words or e- mail. If necessary, the user can also give the support person permission to assume shared interactive control of the user’s computer to show the user how to resolve the problem.
The result of using Remote Assistance is faster problem resolution, an improved support experience, and a lower Total Cost of Ownership (TCO) for supporting end users in large, corporate environments. Remote Assistance vs. Remote Desktop. Remote Assistance and Remote Desktop are different features of Vista that have entirely different uses. Remote Desktop is based on Microsoft’s Terminal Services and is a tool for remotely logging on to remote computers. When you use Remote Desktop to connect to a remote computer, a new user session is established.
Remote Desktop can also establish sessions with computers that have no interactive sessions running (no users logged on locally) such as headless servers. For more information on Remote Desktop, see Chapter 2. Connecting Remote Users and Networks.” Remote Assistance, on the other hand, is a tool for interactively helping users troubleshoot problems with their computers.
To use Remote Assistance, both the User (also called the Novice) and the Helper must be present on their computers. Unlike Remote Desktop, Remote Assistance does not create a new session. Instead, Remote Assistance allows the Helper to work in the existing session of the User.
The User’s desktop gets remoted to the Helper, who can then view the User’s desktop and, with the User’s consent, share control of the desktop. Here is another way to summarize the difference between these two features: In Remote Assistance, both users involved are looking at the same desktop using the same logon credentials (those of the interactively logged- on User) and can share control of that desktop; in Remote Desktop, when the remote person logs on, the interactively logged- on user (if there is one) is logged out. Improvements to Remote Assistance in Windows Vista. Windows Vista includes a number of new features and enhancements for Remote Assistance compared to the Remote Assistance available in Windows XP, including: Connectivity improvements with transparent NAT traversal using Teredo and IPv. An improved user interface that is easier to launch and use. A standalone executable (msra. Improved overall performance with a smaller footprint, quicker startup and connect times, and optimized bandwidth usage for screen updates.
Enhanced security with mandatory password and integration with UAC. New Offer RA via IM scenario and an open API for integration with peer- to- peer applications. Additional Group Policy settings for improved manageability. Remote Assistance in Vista deprecates the following features that were available on XP: No more support for the MAILTO method of solicited Remote Assistance.
No more support for voice sessions For information on interoperability between the XP and Vista versions of Remote Assistance, see the section titled “Interoperability with Remote Assistance in Windows XP” later in this chapter. How Remote Assistance Works. In Remote Assistance, the person needing help is referred to as the User (or Novice) and the support person providing assistance is called the Helper (or Expert).
RA is launched from the Start Menu by navigating to All Programs, clicking Maintenance, and then selecting Windows Remote Assistance. It can also be launched from a command prompt by typing msra. Remote Assistance has two basic modes of operation: Solicited RA. In Solicited RA (also known as Escalated RA) the User requests assistance from the Helper by initiating the RA session using e- mail, instant messaging, or by providing the Helper with a saved copy of an invitation file (*.
Ms. Rc. Incident). Each of these methods uses a different underlying mechanism: Solicited RA Using E- mail.
This method requires that the e- mail clients being used by the User support Simple Mail Application Programming Interface (SMAPI). An example of an e- mail client that supports SMAPI is Windows Mail, which is included with Windows Vista. Other examples of SMAPI- compliant e- mail clients include Microsoft Outlook and other third- party clients. In this approach, the User launches the RA user interface to create an email message that has an RA invitation file (*. Ms. Rc. Incident) attached to the message.
The User must enter a password for the RA session, which must be communicated to the Helper using an out- of- band (OOB) method such as calling the Helper on the telephone. When the Helper receives the User’s RA invitation, she opens the attached ticket, enters the password that was conveyed by the User, and the RA session starts. The Helper must respond to the invitation from the User within a specified time limit (default is 6 hours) or the invitation will expire and a new one will need to be sent. In a domain environment this ticket lifetime can also be configured using Group Policy.
See the section titled “Managing Remote Assistance Using Group Policy” later in this chapter. Solicited RA Using File Transfer. This method requires that both the User and Helper have access to a common folder (such as a network share on a file server) or that they use some other method for transferring the file (for example, by using a USB key to manually transfer the file or by uploading the file to an FTP site).
The user creates an RA invitation file and saves it in the shared folder. The User must provide a password that must be communicated to the Helper using an out- of- band (OOB) method such as a telephone call.
The Helper retrieves the ticket from the shared folder, opens it, enters the password, and the RA session starts. Again, the Helper must respond to the invitation within a specified time or the invitation will expire and a new one will be needed (the expiration time is configurable using Group Policy). Solicited RA Using Instant Messaging.
This method for soliciting assistance requires that the instant messaging (IM) applications being used by both the User and the Helper support Microsoft’s new Rendezvous API. Windows Live Messenger is an example of an IM application that supports Rendezvous. Windows Live Messenger is available as a download.
In this approach, the User requests assistance from someone on his buddy list. To ensure that the remote person is really the User’s buddy (and not someone masquerading as the buddy), Remote Assistance requires that a password be relayed from the User to the Helper by other means (such as a phone call) before the Helper can connect. For more information on the Rendezvous API, see the Windows SDK on MSDN at http: //windowssdk. Unsolicited RA. In Unsolicited RA (also known as Offer RA) the Helper offers help to the User by initiating the RA session. Offer RA using DCOM. This is a typical corporate Help Desk scenario in which all the users are in a domain.
The Helper enters either the fully qualified name (FQDN) or IP address of the User’s computer to connect to the User’s computer.