RDP Yes, Assistance No

[Guest]

I have a rock-solid RDP connection between my remote PC and my office PC, but
we can never establish a Remote Assitance connection, be the invitation via
MSN or in an email. We have the passwords right, on examing the contents of
the Request the correct port 3389 is identified therein, the correct address
for that PC at the office is shown...192.168.0.2:3389;viglen:3389... but when
the connection is attempted it is always unsuccessful. With my remote PC, I
can do Remote Assistance to a friend's PC at his house so it would appear
that my remote laptop PC is OK for RA. When I connect my laptop to the
network when I am in the office (plugged into the router) I still cannot RA
the PC in question on the office network. The Netgear router has port 3389
open and enabled as a service full-time. So frustrating, read lots of posts
here, no joy. Anyone? $25 by PayPal gladly to the expert who can solve this.
All yours.

 

[Robin Walker [MVP]]

I have a rock-solid RDP connection between my remote PC and my office
PC, but we can never establish a Remote Assitance connection, be the
invitation via MSN or in an email. We have the passwords right, on
examing the contents of the Request the correct port 3389 is
identified therein, the correct address for that PC at the office is
shown...192.168.0.2:3389;viglen:3389... but when the connection is
attempted it is always unsuccessful. With my remote PC, I can do
Remote Assistance to a friend's PC at his house so it would appear
that my remote laptop PC is OK for RA.

This is straight-forward. The address "192.168.0.2" is a private IP address
which will only work within the context of the office LAN. It will not work
from the global internet. To make it work, you would have to replace
"192.168.0.2" with the WAN address of your office router, which is
impossible with MSN, and tedious with e-mail.

You can make this work automatically if you enable UPnP in the configuration
of the office router. Then Remote Assistance automatically detects the
presence of the router, sets up an incoming port-mapping, and sends the
external WAN address of the router in any RA ticket. It all "just works"
with no human intervention.

If your office router does not support UPnP, then get a new one that does.

When I connect my laptop to
the network when I am in the office (plugged into the router) I still
cannot RA the PC in question on the office network.

Now, *that* is more of a mystery - check for PC firewall configuration
problems.

The Netgear
router has port 3389 open and enabled as a service full-time.

This won't be necessary for RA if you get UPnP working. You might need it
for RDP to a dedicated PC within the LAN.

 

[Guest]

Thank you Robin, and to answer your points:-
the full RA request ticket reads.....

<?xml version="1.0" encoding="Unicode" ?><UPLOADINFO
TYPE="Escalated"><UPLOADDATA USERNAME="Reg" PROBLEMDESCRIPTION="test RA
request"
RCTICKET="65538,1,174.168.135.153:38861;192.168.0.2:3389;viglen:3389,*,SG/pN7KXhKLHpuxym9zBGolf1a3zVtNV7kMw3sMYKj4=,*,*,IonUr5yfI+YNX/jG8G/yg6Zmy54="
RCTICKETENCRYPTED="0" DtStart="1183606009" DtLength="60" PassStub="" L="0"
/></UPLOADINFO>

so the WAN address of the router is there is it not, with the request being
guided thereafter to the correct PC on the LAN, namely 192.168.0.2 You will
note that port 3389 is also mentioned. This is the port opened as a service
in the router configuration. I further checked the Registry "PortNumber" and
it does correctly list 3389.

As to UPnP, this is configured and active in the router configuration.

Windows firewall is set to OFF in the PC that issued the request (ie the PC
on the office LAN attached to the router). That PC is Pro SP2, the laptop is
Home SP2.

As a further test, on the office PC I sent a request from one user to
another user (on that PC), but that other user cannot RA connect either.

Over to you. And thanks.

 

[Guest]

Thank you Robin, and to answer your points:-
the full RA request ticket reads.....

<?xml version="1.0" encoding="Unicode" ?><UPLOADINFO
TYPE="Escalated"><UPLOADDATA USERNAME="Reg" PROBLEMDESCRIPTION="test RA
request"
RCTICKET="65538,1,174.168.135.153:38861;192.168.0.2:3389;viglen:3389,*,SG/pN7KXhKLHpuxym9zBGolf1a3zVtNV7kMw3sMYKj4=,*,*,IonUr5yfI+YNX/jG8G/yg6Zmy54="
RCTICKETENCRYPTED="0" DtStart="1183606009" DtLength="60" PassStub="" L="0"
/></UPLOADINFO>

so the WAN address of the router is there is it not, with the request being
guided thereafter to the correct PC on the LAN, namely 192.168.0.2 You will
note that port 3389 is also mentioned. This is the port opened as a service
in the router configuration. I further checked the Registry "PortNumber" and
it does correctly list 3389.

As to UPnP, this is configured and active in the router configuration.

Windows firewall is set to OFF in the PC that issued the request (ie the PC
on the office LAN attached to the router). That PC is Pro SP2, the laptop is
Home SP2.

As a further test, on the office PC I sent a request from one user to
another user (on that PC), but that other user cannot RA connect either.

Over to you. And thanks.

 

[Guest]

Thank you Robin, and to answer your points:-
the full RA request ticket reads.....

<?xml version="1.0" encoding="Unicode" ?><UPLOADINFO
TYPE="Escalated"><UPLOADDATA USERNAME="Reg" PROBLEMDESCRIPTION="test RA
request"
RCTICKET="65538,1,174.168.135.153:38861;192.168.0.2:3389;viglen:3389,*,SG/pN7KXhKLHpuxym9zBGolf1a3zVtNV7kMw3sMYKj4=,*,*,IonUr5yfI+YNX/jG8G/yg6Zmy54="
RCTICKETENCRYPTED="0" DtStart="1183606009" DtLength="60" PassStub="" L="0"
/></UPLOADINFO>

so the WAN address of the router is there is it not, with the request being
guided thereafter to the correct PC on the LAN, namely 192.168.0.2 You will
note that port 3389 is also mentioned. This is the port opened as a service
in the router configuration. I further checked the Registry "PortNumber" and
it does correctly list 3389.

As to UPnP, this is configured and active in the router configuration.

Windows firewall is set to OFF in the PC that issued the request (ie the PC
on the office LAN attached to the router). That PC is Pro SP2, the laptop is
Home SP2.

As a further test, on the office PC I sent a request from one user to
another user (on that PC), but that other user cannot RA connect either.

Over to you. And thanks.

 

[Guest]

Thank you Robin, and to answer your points:-
the full RA request ticket reads.....

<?xml version="1.0" encoding="Unicode" ?><UPLOADINFO
TYPE="Escalated"><UPLOADDATA USERNAME="Reg" PROBLEMDESCRIPTION="test RA
request"
RCTICKET="65538,1,174.168.135.153:38861;192.168.0.2:3389;viglen:3389,*,SG/pN7KXhKLHpuxym9zBGolf1a3zVtNV7kMw3sMYKj4=,*,*,IonUr5yfI+YNX/jG8G/yg6Zmy54="
RCTICKETENCRYPTED="0" DtStart="1183606009" DtLength="60" PassStub="" L="0"
/></UPLOADINFO>

so the WAN address of the router is there is it not, with the request being
guided thereafter to the correct PC on the LAN, namely 192.168.0.2 You will
note that port 3389 is also mentioned. This is the port opened as a service
in the router configuration. I further checked the Registry "PortNumber" and
it does correctly list 3389.

As to UPnP, this is configured and active in the router configuration.

Windows firewall is set to OFF in the PC that issued the request (ie the PC
on the office LAN attached to the router). That PC is Pro SP2, the laptop is
Home SP2.

As a further test, on the office PC I sent a request from one user to
another user (on that PC), but that other user cannot RA connect either.

Over to you. And thanks.

 

[Guest]

Robin, HI. Apolgies for posting my reply to you FOUR times identically. I see
another use John Deane .Remote Access Not Working. sails in my boat too (just
above me here). Any further ideas to throw light on my penumbra?