Re: RDP Yes, Assistance No

Simon <Simon@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:

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.

--
Robin Walker [MVP Networking]
rdhw@xxxxxxxxx


.

Relevant Pages

  • Re: Setting up Remote Desktop web connection in winxp mce to work
    ... Many consumer grade routers do not support that so called loopback test, ie. call the public IP of the router from a PC on the internal LAN. ... The best test is from a remote location. ... Also keep in mind your work network admins may block TCP ... > clicked on default web site and properties. ...
    (microsoft.public.windowsxp.work_remotely)
  • Re: Wireless networking: allowing remote computer access to printe
    ... The way I read your response it appears you have 2 PCs on a LAN (Local Area Network), not via WAN. ... Your XP is the main PC as you state it and the Win2K is the remote PC. ... The PCs connect locally to each other on your LAN via wireless router. ...
    (microsoft.public.windowsxp.general)
  • Re: netopia 3346 and site to site vpn with sbs 2003 premium
    ... everythime its an issue with the route from the remote site router. ... SBS 2003 SP 1 with ISA 2004 installed. ... View the properties of the remote site network connection and click ...
    (microsoft.public.windows.server.sbs)
  • Re: Adding a 3rd NIC to an SBS2003 Premium server.
    ... network bridge between the main office and the two remote offices. ... networking game for a few years, I don't trust Windows with stuff like VPN ... Exchange, Domain Control and Fileserving for a whole network is enough load, ... Main Internet gateway router: 10.0.0.1 ...
    (microsoft.public.windows.server.sbs)
  • Re: PLEASE HELP!! Can connect within network, but not anywhere els
    ... Al Jarvi (MS-MVP Windows Networking) ... which is the assigned IP from my router. ... I really didn't know what i was doing when I switched my TCP port from ... I used the IP my remote computer uses ...
    (microsoft.public.windowsxp.work_remotely)