Remote assistance

[Guest]

I am trying to help my father with his computer. I have moved a long
distance away and am trying to get remote assistance working. I have xp
prof. and he has xp home. We are trying to connect through windows messenger.
We both wm 5.1. We both have windows firewall on but allow exceptions.
Windows messenger is checked in exceptions. We both are on Verizon DSL I have
a linksys router and he has Verizon modem/router combo. We both get a messge
that states that "cannot resolve host name" I cannot find anything about the
message in microsofts knowlege base. Any help would be appreciated. Thanks in
advance

VaHenry

 

[Shenan Stanley]

I am trying to help my father with his computer. I have moved a long
distance away and am trying to get remote assistance working. I have
xp prof. and he has xp home. We are trying to connect through windows
messenger. We both wm 5.1. We both have windows firewall on but allow
exceptions. Windows messenger is checked in exceptions. We both are
on Verizon DSL I have a linksys router and he has Verizon
modem/router combo. We both get a messge that states that "cannot
resolve host name" I cannot find anything about the message in
microsofts knowlege base. Any help would be appreciated. Thanks in
advance

Router setup to pass the request through Port 3389 to his PC?

From:
http://www.microsoft.com/technet/prodtechnol/winxppro/deploy/worki01.mspx

Remote Assistance
---------------------------
Remote Assistance uses Remote Desktop Protocol (RDP); this is the same
protocol used by Microsoft Terminal Services. RDP is built on top of a TCP
connection. Windows Messenger sets up the remote assistance session using
the server-based session invite logic-similar to File Transfer. Because of
this, the issue with NAT addresses applies to this scenario as well.

Remote Assistance includes additional logic to deal with the NAT scenario.
This logic simply attempts to create the TCP connection from both clients.
This way, if one of the clients is behind a NAT, the connection can still be
created and remote assistance occurs. If both clients are behind a
(non-UPnP) NAT, the connection cannot be established. The additional SIP
invite logic is only added if a voice session is added in support of Remote
Assistance.

In addition to the issues resulting from NAT addresses, which are only of
concern with multiple NAT devices in the communication path, TCP port 3389
is used for the TCP connection for the Remote Assistance protocol. This
means that port 3389 must be opened on any firewalls between clients.

 

[Robin Walker [MVP]]

I am trying to help my father with his computer. I have moved a long
distance away and am trying to get remote assistance working. I have
xp prof. and he has xp home. We are trying to connect through windows
messenger. We both wm 5.1. We both have windows firewall on but allow
exceptions. Windows messenger is checked in exceptions. We both are
on Verizon DSL I have a linksys router and he has Verizon
modem/router combo. We both get a messge that states that "cannot
resolve host name" I cannot find anything about the message in
microsofts knowlege base. Any help would be appreciated. Thanks in
advance

You will not get Remote Assistance to work unless:

- the router at the Novice end supports UPnP, and UPnP support is enabled;
- the firewall at the novice end has Exceptions defined for "UPnP Framework"
and for "Remote Desktop" and for "Remote Assistance".

There are no special router or firewall requirements at the Expert end.

The "Novice" is the person requesting Remote Assistance, the "Expert" is the
one responding to the call.

UPnP is required at the Novice end so that the WAN IP address can be
detected and written into the Remote Assistance request ticket: it is not
sufficient to just port-forward port 3389.

 

[Guest]

I disabled all virus protection and firewalls in both computers. I opened
port 3389 in my router under port triggering. I still get "cannot resolve
host name".