REMOTE DESKTOP CONNECTION : A common problem?

First of all, scrap using Remote Desktop Connection. Use a variation of VNC instead...

http://www.realvnc.com/
http://www.tightvnc.com/
http://www.uvnc.com/


Then you need to set up port forwarding on your routers/networks. The default VNC port is 5900.

PC-A needs to be assigned a static internal IP, lets say 192.168.2.5. Then you need to go into the DSL gateway's settings and set up any incoming requests on port 5900 to be forwarded internally to 192.168.2.5

You then need to do the same with PC-B

Then when you want to connect to the other you have to use their WAN IP (the IP of the internet connection and not the internal one).

http://www.realvnc.com/support/portforward.html

could the remote machines ip address have changed? that would be my guess are you using windows remote desktop or VNC if so that is the problem

If you want A to be able to control B, you need to configure the router in B to forward TCP request on port 3389 which Remote Desktop requires to the IP address of computer B.

The problem is that if you are using DHCP on the router to dynamically assign IP addresses to computers, you might end up with different IP address at different time. The solution to this issue is to reserve the IP address to the computer at location B, or use static IP address.

Alternatively, you can try the free version of LogMeIn to control computer B. The use of LogMeIn requires no setup on the router, but you will need to install an ActiveX client on both computers.