Remote Desktop to more than one server

Hi,

I have opened port 3389 on our firewall and routed that to the IP address of
a server. It works fine and there have been no problems. Now a supplier
wants remote desktop access to a different server. I don't know how to set
that up so that that they are sent to one server and the original server
access is unchanged. Do I use a different port? Or do I just add another
entry in the routing table on the same port? How would it work?

Your help is appreciated - greatly!

Thanks in advance

SW

Hi Steve,

If you only have one public IP then you will need to use different port. In
this case you will have to notify your partner to use different port when
connecting to the server. You can even leave the server to run on TCP port
3389 and just translate the TCP port (e.g. if some connects on TCP port 3340
on your public IP it could translate to internal IP of your TS on TCP port
3389).

If you have more then one IP available then you could use default TCP port.

How to Change Terminal Server's Listening Port
http://support.microsoft.com/default...roduct=win2000

Mike

"Steve" <(E-Mail Removed)> wrote in message
news:413e249d$0$51061$(E-Mail Removed)...
> Hi,
>
> I have opened port 3389 on our firewall and routed that to the IP address
of
> a server. It works fine and there have been no problems. Now a supplier
> wants remote desktop access to a different server. I don't know how to set
> that up so that that they are sent to one server and the original server
> access is unchanged. Do I use a different port? Or do I just add another
> entry in the routing table on the same port? How would it work?
>
> Your help is appreciated - greatly!
>
> Thanks in advance
>
> SW

Thank you Mike,

I have just the one public IP. You've made it sound nice and easy. I'll give
it a try!

SW

Miha Pihler wrote:

> Hi Steve,
>
> If you only have one public IP then you will need to use different port.
> In this case you will have to notify your partner to use different port
> when connecting to the server. You can even leave the server to run on TCP
> port 3389 and just translate the TCP port (e.g. if some connects on TCP
> port 3340 on your public IP it could translate to internal IP of your TS
> on TCP port 3389).
>
> If you have more then one IP available then you could use default TCP
> port.
>
> How to Change Terminal Server's Listening Port
>
http://support.microsoft.com/default...roduct=win2000
>
> Mike
>
> "Steve" <(E-Mail Removed)> wrote in message
> news:413e249d$0$51061$(E-Mail Removed)...
>> Hi,
>>
>> I have opened port 3389 on our firewall and routed that to the IP address
> of
>> a server. It works fine and there have been no problems. Now a supplier
>> wants remote desktop access to a different server. I don't know how to
>> set that up so that that they are sent to one server and the original
>> server access is unchanged. Do I use a different port? Or do I just add
>> another entry in the routing table on the same port? How would it work?
>>
>> Your help is appreciated - greatly!
>>
>> Thanks in advance
>>
>> SW

Quick note:

If you use an alternate port, make sure you specify the port number on
the server line of the Remote Desktop connection client (i.e.,
servernameort ) and that the standard web client does not support
alternate ports...

Jeffrey Randow (Windows Networking & Smart Display MVP)
jeffreyr-(E-Mail 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

On Tue, 07 Sep 2004 22:44:42 +0100, Steve <(E-Mail Removed)>
wrote:

>Thank you Mike,
>
>I have just the one public IP. You've made it sound nice and easy. I'll give
>it a try!
>
>SW
>
>Miha Pihler wrote:
>
>> Hi Steve,
>>
>> If you only have one public IP then you will need to use different port.
>> In this case you will have to notify your partner to use different port
>> when connecting to the server. You can even leave the server to run on TCP
>> port 3389 and just translate the TCP port (e.g. if some connects on TCP
>> port 3340 on your public IP it could translate to internal IP of your TS
>> on TCP port 3389).
>>
>> If you have more then one IP available then you could use default TCP
>> port.
>>
>> How to Change Terminal Server's Listening Port
>>
>http://support.microsoft.com/default...roduct=win2000
>>
>> Mike
>>
>> "Steve" <(E-Mail Removed)> wrote in message
>> news:413e249d$0$51061$(E-Mail Removed)...
>>> Hi,
>>>
>>> I have opened port 3389 on our firewall and routed that to the IP address
>> of
>>> a server. It works fine and there have been no problems. Now a supplier
>>> wants remote desktop access to a different server. I don't know how to
>>> set that up so that that they are sent to one server and the original
>>> server access is unchanged. Do I use a different port? Or do I just add
>>> another entry in the routing table on the same port? How would it work?
>>>
>>> Your help is appreciated - greatly!
>>>
>>> Thanks in advance
>>>
>>> SW

Hi Mike

I set it up to use a different port number, and edited the registry to make
the server listen on that non-standard port. I did a search for port
registrations first, and used a non-registered port.
Works fine!

Thanks for your help
Steve
"Miha Pihler" <mihap-(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Hi Steve,
>
> If you only have one public IP then you will need to use different port.
In
> this case you will have to notify your partner to use different port when
> connecting to the server. You can even leave the server to run on TCP port
> 3389 and just translate the TCP port (e.g. if some connects on TCP port
3340
> on your public IP it could translate to internal IP of your TS on TCP port
> 3389).
>
> If you have more then one IP available then you could use default TCP
port.
>
> How to Change Terminal Server's Listening Port
>
http://support.microsoft.com/default...roduct=win2000
>
> Mike
>
> "Steve" <(E-Mail Removed)> wrote in message
> news:413e249d$0$51061$(E-Mail Removed)...
> > Hi,
> >
> > I have opened port 3389 on our firewall and routed that to the IP
address
> of
> > a server. It works fine and there have been no problems. Now a supplier
> > wants remote desktop access to a different server. I don't know how to
set
> > that up so that that they are sent to one server and the original server
> > access is unchanged. Do I use a different port? Or do I just add another
> > entry in the routing table on the same port? How would it work?
> >
> > Your help is appreciated - greatly!
> >
> > Thanks in advance
> >
> > SW
>
>

Hi Jeffrey,

I have told the partner to be sure to insert the port number after the
servername, otherwise they will go to the wrong server!
Not too sure what you mean by "the standard web client does not support
alternate ports"?

Thanks for your help
Steve
"Jeffrey Randow (MVP)" <jeffreyr-(E-Mail Removed)> wrote
in message news:(E-Mail Removed)...
> Quick note:
>
> If you use an alternate port, make sure you specify the port number on
> the server line of the Remote Desktop connection client (i.e.,
> servernameort ) and that the standard web client does not support
> alternate ports...
>
> Jeffrey Randow (Windows Networking & Smart Display MVP)
> jeffreyr-(E-Mail 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
>
> On Tue, 07 Sep 2004 22:44:42 +0100, Steve <(E-Mail Removed)>
> wrote:
>
> >Thank you Mike,
> >
> >I have just the one public IP. You've made it sound nice and easy. I'll
give
> >it a try!
> >
> >SW
> >
> >Miha Pihler wrote:
> >
> >> Hi Steve,
> >>
> >> If you only have one public IP then you will need to use different
port.
> >> In this case you will have to notify your partner to use different port
> >> when connecting to the server. You can even leave the server to run on
TCP
> >> port 3389 and just translate the TCP port (e.g. if some connects on TCP
> >> port 3340 on your public IP it could translate to internal IP of your
TS
> >> on TCP port 3389).
> >>
> >> If you have more then one IP available then you could use default TCP
> >> port.
> >>
> >> How to Change Terminal Server's Listening Port
> >>
>
>http://support.microsoft.com/default...3&Product=win2
000
> >>
> >> Mike
> >>
> >> "Steve" <(E-Mail Removed)> wrote in message
> >> news:413e249d$0$51061$(E-Mail Removed)...
> >>> Hi,
> >>>
> >>> I have opened port 3389 on our firewall and routed that to the IP
address
> >> of
> >>> a server. It works fine and there have been no problems. Now a
supplier
> >>> wants remote desktop access to a different server. I don't know how to
> >>> set that up so that that they are sent to one server and the original
> >>> server access is unchanged. Do I use a different port? Or do I just
add
> >>> another entry in the routing table on the same port? How would it
work?
> >>>
> >>> Your help is appreciated - greatly!
> >>>
> >>> Thanks in advance
> >>>
> >>> SW
>

Hi,

If you will use TSWEB (web client) to connect to remote server then you also
need to apply this.

How to Change the Listening Port in the Windows Terminal Server Web Client
http://support.microsoft.com/default...uct=winsvr2003

Mike

"Steve W" <SteveW@=No=Spam.org> wrote in message
news:eDXeU$(E-Mail Removed)...
> Hi Jeffrey,
>
> I have told the partner to be sure to insert the port number after the
> servername, otherwise they will go to the wrong server!
> Not too sure what you mean by "the standard web client does not support
> alternate ports"?
>
> Thanks for your help
> Steve
> "Jeffrey Randow (MVP)" <jeffreyr-(E-Mail Removed)>
wrote
> in message news:(E-Mail Removed)...
> > Quick note:
> >
> > If you use an alternate port, make sure you specify the port number on
> > the server line of the Remote Desktop connection client (i.e.,
> > servernameort ) and that the standard web client does not support
> > alternate ports...
> >
> > Jeffrey Randow (Windows Networking & Smart Display MVP)
> > jeffreyr-(E-Mail 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
> >
> > On Tue, 07 Sep 2004 22:44:42 +0100, Steve <(E-Mail Removed)>
> > wrote:
> >
> > >Thank you Mike,
> > >
> > >I have just the one public IP. You've made it sound nice and easy. I'll
> give
> > >it a try!
> > >
> > >SW
> > >
> > >Miha Pihler wrote:
> > >
> > >> Hi Steve,
> > >>
> > >> If you only have one public IP then you will need to use different
> port.
> > >> In this case you will have to notify your partner to use different
port
> > >> when connecting to the server. You can even leave the server to run
on
> TCP
> > >> port 3389 and just translate the TCP port (e.g. if some connects on
TCP
> > >> port 3340 on your public IP it could translate to internal IP of your
> TS
> > >> on TCP port 3389).
> > >>
> > >> If you have more then one IP available then you could use default TCP
> > >> port.
> > >>
> > >> How to Change Terminal Server's Listening Port
> > >>
> >
>
>http://support.microsoft.com/default...3&Product=win2
> 000
> > >>
> > >> Mike
> > >>
> > >> "Steve" <(E-Mail Removed)> wrote in message
> > >> news:413e249d$0$51061$(E-Mail Removed)...
> > >>> Hi,
> > >>>
> > >>> I have opened port 3389 on our firewall and routed that to the IP
> address
> > >> of
> > >>> a server. It works fine and there have been no problems. Now a
> supplier
> > >>> wants remote desktop access to a different server. I don't know how
to
> > >>> set that up so that that they are sent to one server and the
original
> > >>> server access is unchanged. Do I use a different port? Or do I just
> add
> > >>> another entry in the routing table on the same port? How would it
> work?
> > >>>
> > >>> Your help is appreciated - greatly!
> > >>>
> > >>> Thanks in advance
> > >>>
> > >>> SW
> >
>
>