Remote Desktop to a Client of a Windows Server network

[Kelbury]

I am trying to get a RD connection to one of our office
computers. We are running Server 2000 in the office. I
also want to maintain my terminal services on the server
box. We use a linksys router and run no-ip on our server
to solve the dynamic ip problem. I currently have 3389 on
the router forwarded to the server. How do I get access
to the office machine now? I am thinking to remap the
Terminal Services UDP port to something different i.e.
4900 and then when I try to logon, specify 4900 as the
port I want to use. I will then set the router to
forward 4900 to the client box I am trying to connect to.

Am I way off base here?

 

[Guest]

Huh? What do you mean by "We use a linksys router and run no-ip on our server to solve the dynamic ip problem"

If the Terminal Server has a static IP Address, you forward TCP Port 3389 to the Private Static IP Address of your Server, then use Remote Desktop from an Internet computer to connect to the WAN IP Address of your Linksys router, which forwards the traffic to your TS

Picture of the port forwarding here

http://www.workthin.com/images/LinksysPortForwarding.JP

In this picture, 192.168.1.2 is the "Private Static IP Address of your Server". Nothing else to do to make it work

Patrick Rous
Microsoft MVP - Terminal Serve
http://www.workthin.co

----- Kelbury wrote: ----

I am trying to get a RD connection to one of our office
computers. We are running Server 2000 in the office. I
also want to maintain my terminal services on the server
box. We use a linksys router and run no-ip on our server
to solve the dynamic ip problem. I currently have 3389 on
the router forwarded to the server. How do I get access
to the office machine now? I am thinking to remap the
Terminal Services UDP port to something different i.e.
4900 and then when I try to logon, specify 4900 as the
port I want to use. I will then set the router to
forward 4900 to the client box I am trying to connect to

Am I way off base here

 

[Bill Sanderson]

Your idea is one way to make this work, but how many clients do you have?
Picture a sieve, if you have very many clients, and a chart remembering
which client is which port number.

If you do choose this approach, one trick with a Linksys, or any router
which can change the port as it forwards, is to leave the listening port on
the client machine at the default 3389, and use Plug and Play forwarding to
change the external port. This means that on the internal LAN the machines
keep the standard port.

When there are multiple machines you might wish to reach in this situation,
I prefer a VPN connection. You've got 2000 server, so you can set up
multiple inbound VPN connections, and each VPN can reach any client on the
network.

Once the VPN connection is established, you can run Remote Desktop and
connect to the client machine through the VPN.

 

[Jeffrey Randow (MVP)]

Bill's suggestion is the best way to do this - use a VPN...

I have a similar setup, though, at the office forwarding TCP 3389 to
server 1, 3390 to server 2, 3391 to server 3, etc....

Jeffrey Randow (Windows Net. & Smart Display MVP)
(e-mail address removed)

Please post all responses to the newsgroups for the benefit
of all USENET users. Messages sent via email may or may not
be answered depending on time availability....

Remote Networking Technology Support Site -
http://www.remotenetworktechnology.com
Windows XP Expert Zone - http://www.microsoft.com/windowsxp/expertzone