Has anyone ever assisted a customer by using Windows Remote Connection? It's easy to do on the same LAN, just wondering if it can be done across networks.

Thanks in advance

Yes, it can be done. It requires port forwarding at the router. Normally port number 3389.The connecting to the customers external IP plus port.For instance you would put 24.92.226.11:3389 into RDP. Individual internal connections can be made by changing the port the PC uses to connect. Done by editing the registry.
Really not practical unless you are the network admin.

Check out croosloop
That may work for you.
Hope I understood the question.

quote:

Originally posted by Snowbelt:
Yes, it can be done. It requires port forwarding at the router. Normally port number 3389.The connecting to the customers external IP plus port.For instance you would put 24.92.226.11:3389 into RDP. Individual internal connections can be made by changing the port the PC uses to connect. Done by editing the registry.
.

If anybody's considering this please DON'T use the default port (3389) - it's a HUGE target unless you absolutely have to.

I would recommend NOT changing this through the registry. Instead use a router with port redirection. It makes it easer to administer on the LAN since the default port is still used internally. With port redirection you configure the router to accept a connection on another port - like 5000 for example that redirects to port 3389 on LAN address 192.168.1.87...

Sorry, I should have been more clear. I was trying to discourage RDP use over the WAN.
Had a customer that was setup to use the default port. Somebody from Russia was remoting(how is that spelled) and playing online poker with her computer. Extra profiles the whole the whole bit.
P.S. Disable or password protect the default administrator account in XP. Rarely done!