I want have two W2K3 Terminal Servers that will run behind
my corp. firewall. The firewall currently uses port
forwarding to the correct internal server. I am using the
RDP Web Connection. As I understand, there is no way for
the RDP Web Connection to connect to another port other
than 3389. If I am wrong, please let me know how to
change the port. If the port cannot be changed, how can I
specify which server a user should connect to. There will
be two seperate groups I could use to distinguish between
the servers.

You certainly can change the port. The problem is that if you have only 1
public IP, you may need to change the listening port on one of the servers,
and that means it needs to be modified for local connections as well.
If your firewall supports redirecting a port on the outside to a different
port number internally, then just pick a high port number - something above
49000 or so to make sure it's not a registered port - and you don't need to
do anything off the firewall.

Here's how, assuming the firewall works for this. Let's assume you're going
to use 49001 as the port on the outside that listens for connections to the
2nd TS.

First, set up a rule for the firewall that redirects 49001 on the outside to
port 3389 on the TS.

Second, make a copy of the TSWeb page. Open it in a text editor, and look
for the line
MsRdpClient.Connect
Somewhere shortly before that line, insert a line that says
MsRdpClient.AdvancedSettings2.RdpPort = 49001
and the new page will now connect to port 49001.



Scott Goldman wrote:
> I want have two W2K3 Terminal Servers that will run behind
> my corp. firewall. The firewall currently uses port
> forwarding to the correct internal server. I am using the
> RDP Web Connection. As I understand, there is no way for
> the RDP Web Connection to connect to another port other
> than 3389. If I am wrong, please let me know how to
> change the port. If the port cannot be changed, how can I
> specify which server a user should connect to. There will
> be two seperate groups I could use to distinguish between
> the servers.

Alex,

Thank you very much. Your solution is perfect.

Scott
>-----Original Message-----
>You certainly can change the port. The problem is that if
you have only 1
>public IP, you may need to change the listening port on
one of the servers,
>and that means it needs to be modified for local
connections as well.
>If your firewall supports redirecting a port on the
outside to a different
>port number internally, then just pick a high port
number - something above
>49000 or so to make sure it's not a registered port - and
you don't need to
>do anything off the firewall.
>
>Here's how, assuming the firewall works for this. Let's
assume you're going
>to use 49001 as the port on the outside that listens for
connections to the
>2nd TS.
>
>First, set up a rule for the firewall that redirects
49001 on the outside to
>port 3389 on the TS.
>
>Second, make a copy of the TSWeb page. Open it in a text
editor, and look
>for the line
> MsRdpClient.Connect
>Somewhere shortly before that line, insert a line that
says
> MsRdpClient.AdvancedSettings2.RdpPort = 49001
>and the new page will now connect to port 49001.
>
>
>
>Scott Goldman wrote:
>> I want have two W2K3 Terminal Servers that will run
behind
>> my corp. firewall. The firewall currently uses port
>> forwarding to the correct internal server. I am using
the
>> RDP Web Connection. As I understand, there is no way
for
>> the RDP Web Connection to connect to another port other
>> than 3389. If I am wrong, please let me know how to
>> change the port. If the port cannot be changed, how
can I
>> specify which server a user should connect to. There
will
>> be two seperate groups I could use to distinguish
between
>> the servers.
>
>
>.
>