Remote Desktop to multiple PC's

I wrote previously to get Remote Desktop working with my server and
everything works fine.

We have a server (WS2003) and 4 PC's (XP) connected to a router with a
static ISP provided IP address.

As mentioned I can connect remotely from my home to the server. I have
added port forwarding to the server IP (192.168.1.2) thru 3389. When I
tried to add one of the PC's IP address (192.168.1.24) to go thru 3389, I
got an error message saying "either one of the Virtual Servers or Special
Application rules has already been configured for the Service port 3389.
You must delete or modify the existing rule."

I modified the IP address (in the rule) to match the PC address
(192.168.1.24) I was trying to get to and everything worked fine.

The question is "How do set up the router so I can access any of the PC's or
the server on our network without having to modify the setting for port 3389
for a specific IP address?

Thanks again for helping a novice.

You will have to use a different port for each server you want to connect
to, for example 3390. You can have your NAT server do a port translation to
3389 to the inside server.

3389\ /Server1 running RDP 3389
outside 3390- [NAT SERVER] -Server2 running RDP 3389
3391/ \Server3 running RDP 3389



"Emile" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> I wrote previously to get Remote Desktop working with my server and
> everything works fine.
>
> We have a server (WS2003) and 4 PC's (XP) connected to a router with a
> static ISP provided IP address.
>
> As mentioned I can connect remotely from my home to the server. I have
> added port forwarding to the server IP (192.168.1.2) thru 3389. When I
> tried to add one of the PC's IP address (192.168.1.24) to go thru 3389, I
> got an error message saying "either one of the Virtual Servers or Special
> Application rules has already been configured for the Service port 3389.
> You must delete or modify the existing rule."
>
> I modified the IP address (in the rule) to match the PC address
> (192.168.1.24) I was trying to get to and everything worked fine.
>
> The question is "How do set up the router so I can access any of the PC's
or
> the server on our network without having to modify the setting for port
3389
> for a specific IP address?
>
> Thanks again for helping a novice.
>
>

Here's a link too.

http://www.microsoft.com/technet/com...uy/cg0503.mspx

"Emile" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> I wrote previously to get Remote Desktop working with my server and
> everything works fine.
>
> We have a server (WS2003) and 4 PC's (XP) connected to a router with a
> static ISP provided IP address.
>
> As mentioned I can connect remotely from my home to the server. I have
> added port forwarding to the server IP (192.168.1.2) thru 3389. When I
> tried to add one of the PC's IP address (192.168.1.24) to go thru 3389, I
> got an error message saying "either one of the Virtual Servers or Special
> Application rules has already been configured for the Service port 3389.
> You must delete or modify the existing rule."
>
> I modified the IP address (in the rule) to match the PC address
> (192.168.1.24) I was trying to get to and everything worked fine.
>
> The question is "How do set up the router so I can access any of the PC's
or
> the server on our network without having to modify the setting for port
3389
> for a specific IP address?
>
> Thanks again for helping a novice.
>
>

You can't. You can only do one machine at a time. It is the "Laws of
Networking", it is the way the world is.

BTW - Even though the device you use calls it "port forwarding",...there is
no such term. That is just incorrect "slang" terminology made popular by the
SOHO market (like the home user Linksys devices and such). The real term for
it is Static NAT or optionally Reverse NAT. They also call those device
"routers" when they are not routers, but they are rather cheap low cost NAT
Firewalls.

"Emile" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> As mentioned I can connect remotely from my home to the server. I have
> added port forwarding to the server IP (192.168.1.2) thru 3389. When I
> tried to add one of the PC's IP address (192.168.1.24) to go thru 3389, I
> got an error message saying "either one of the Virtual Servers or Special
> Application rules has already been configured for the Service port 3389.
> You must delete or modify the existing rule."

I only want to access one machine at time. All the machines are on the
network side of the same router. Is there not a way in the IP address to
say go to the static IP address supplied by the ISP and then go to the
private address on the network. Again only one at a time.

Example in the computer: box of the Remote Desktop Connection screen type
the ISP address followed by the private IP address as follows:
69.69.169.169//192.168.1.169

Thanks again, sorry about not using the correct terminology.

"Emile" <(E-Mail Removed)> wrote in message
news:%23q%(E-Mail Removed)...
> I only want to access one machine at time. All the machines are on the
> network side of the same router. Is there not a way in the IP address to
> say go to the static IP address supplied by the ISP and then go to the
> private address on the network. Again only one at a time.
>
> Example in the computer: box of the Remote Desktop Connection screen type
> the ISP address followed by the private IP address as follows:
> 69.69.169.169//192.168.1.169

No, that is not possible.
You should examine the Link the Neteng gave you in the other post for some
possible options. But aside from that you can only do one machine at a time
without totally reconfiguring the Static NAT everytime on the Internet
Device.

--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com

Think about it from the outside. If you want to talk to 69.69.69.169 on port
3389, you send a packet and it gets to the firewall and you ask if you can
talk on port 3389. The firewall looks at the ACL and sees that it's OK, then
looks and sees where, if not local to the firewall, that that port goes to.
Let's say it goes to 192.168.1.1. The firewall then allows communication
through on port 3389 to 192.168.1.1. Now you want to talk to 192.168.1.2,
but your still on the outside. You hit the firewall again and your still
looking to talk on port 3389. The firewall does the lookup again and sends
it to 192.168.1.1 again. That's normal because you can not communicate on
one port (3389 in this case) from the outside to multiple servers on the
inside. How would the firewall know which server you want to talk too? It
can't! If you use a different port for each server, when you ask to talk to
69.69.69.169 on port 3390, the firewall looks it up and sees that you want
to talk to server2 at 192.168.1.2 and either allows the traffic, or better
yet, changes the port to 3389 and sends it to server2.


"Emile" <(E-Mail Removed)> wrote in message
news:%23q%(E-Mail Removed)...
> I only want to access one machine at time. All the machines are on the
> network side of the same router. Is there not a way in the IP address to
> say go to the static IP address supplied by the ISP and then go to the
> private address on the network. Again only one at a time.
>
> Example in the computer: box of the Remote Desktop Connection screen type
> the ISP address followed by the private IP address as follows:
> 69.69.169.169//192.168.1.169
>
> Thanks again, sorry about not using the correct terminology.
>
>

This is the page you are looking for. Change ports on all clients you
are accessing 3389, 3390,3391 ,etc. Modify your "port forwarding"
(NAT) tables to reflect correct ports to client settings.

http://support.microsoft.com/?id=187623

Unless you employ this method you will have to reconfigure NAT tables
each time you wanted to connect to a different client.

OK, what Neteng said will work for what you are wanting. Configure
incoming port for 3389 , IP of server, out going port for 3390, 3391,
etc. You say you only wait to do one at a time, I contend that in the
future you will be interested in multiple sessions. Neteng's method
should still work via WAN but I would think it would place unnecessary
load on the NAT via LAN because you would Still have to enter the
domain name in the connect to dialogue box So that NAT would translate
the port mappings. Your client computer Can only have one session open
on a particular port making what I suggested the optimal choice by
being able to enter IP's or NetBios names when connected via LAN or
VPN. Personally I connect VPN before connecting RDP. Oh yeah, when
connected via VPN you do not have to configure anything in NAT.
> Note to Phillip & Neteng: I have read your stuff for some time now, and have a respect for your knowledge. If you've got this handled and want me to shut-up say the word.
Later, Zach

all you have to do is chnge the default 3389 port on 2 of the 3 computer
leave 1 computer the default 3389 and change the rdp port on the xp
workstations to something differnt you have to do this in the registry. once
they are change say 192.168.1.10=rdp port 3390 then 192.168.1.11=rdp port
3370 then just configure your router to foward the change ports to those
ip's. now when you connect to the computers use publicip:3370 for example.

or you can just connect to the one server at 3389 and once in your lan just
open up rdp connect and type in private ip and connect to the machines that
way.

"Neteng" wrote:

> Think about it from the outside. If you want to talk to 69.69.69.169 on port
> 3389, you send a packet and it gets to the firewall and you ask if you can
> talk on port 3389. The firewall looks at the ACL and sees that it's OK, then
> looks and sees where, if not local to the firewall, that that port goes to.
> Let's say it goes to 192.168.1.1. The firewall then allows communication
> through on port 3389 to 192.168.1.1. Now you want to talk to 192.168.1.2,
> but your still on the outside. You hit the firewall again and your still
> looking to talk on port 3389. The firewall does the lookup again and sends
> it to 192.168.1.1 again. That's normal because you can not communicate on
> one port (3389 in this case) from the outside to multiple servers on the
> inside. How would the firewall know which server you want to talk too? It
> can't! If you use a different port for each server, when you ask to talk to
> 69.69.69.169 on port 3390, the firewall looks it up and sees that you want
> to talk to server2 at 192.168.1.2 and either allows the traffic, or better
> yet, changes the port to 3389 and sends it to server2.
>
>
> "Emile" <(E-Mail Removed)> wrote in message
> news:%23q%(E-Mail Removed)...
> > I only want to access one machine at time. All the machines are on the
> > network side of the same router. Is there not a way in the IP address to
> > say go to the static IP address supplied by the ISP and then go to the
> > private address on the network. Again only one at a time.
> >
> > Example in the computer: box of the Remote Desktop Connection screen type
> > the ISP address followed by the private IP address as follows:
> > 69.69.169.169//192.168.1.169
> >
> > Thanks again, sorry about not using the correct terminology.
> >
> >
>
>
>