How to configure a Terminal Server behind an SBS 2003.

I have a dual-nic SBS 2003 server with a public IP on the
one nic and a private IP on the other nic. I also have a
2003 server on the network behind the SBS 2003 server.
This second server will function as our Terminal Server.
My question is how will public/Internet users access the
Terminal Server. Normally I would port-map 3389 at the
public interface of a router through to the private IP of
the server. I understand port mapping quite well, but I
don't know how to do it on a Windows server, nor do I know
if this is the recommended way. I am guessing that I can
bind a second public IP address to the public nic on the
SBS 2003 server and then port map 3389 for that second IP
address over to the 2003 Terminal Server's private IP.
Having 2 public IP's should allow administrative RDP
traffic to still route to the SBS server on the first IP,
while the 2nd IP traffic is forwarded to the TS server.
Is my concept correct? Is it the recommended way? How do
I put it into effect? I think I know how to bind a second
IP address to the NIC but the rest I need some guidance
with. Sorry for the novel. THANKS in advance!

I assume you are not running ISA, and you have configured RRAS on the SBS
server to provide NAT routing. In this scenario, you do not need a second
IP address. Go to Administrative Tools and open the RRAS console. Expand
IP Routing and click NAT/Basic Firewall. In the right pane right click your
Internet adapter and select Properties. Make sure the firewall is enabled
(this is the default), then click the Services and Ports tab. Check the box
for Remote Desktop - click the Edit button and enter the IP address for the
Terminal Server.

Doug Sherman
MCSE Win2k/NT4.0, MCSA, MCP+I, MVP

"David Maxwell" <(E-Mail Removed)> wrote in message
news:88b901c403c3$f18cd060$(E-Mail Removed)...
> I have a dual-nic SBS 2003 server with a public IP on the
> one nic and a private IP on the other nic. I also have a
> 2003 server on the network behind the SBS 2003 server.
> This second server will function as our Terminal Server.
> My question is how will public/Internet users access the
> Terminal Server. Normally I would port-map 3389 at the
> public interface of a router through to the private IP of
> the server. I understand port mapping quite well, but I
> don't know how to do it on a Windows server, nor do I know
> if this is the recommended way. I am guessing that I can
> bind a second public IP address to the public nic on the
> SBS 2003 server and then port map 3389 for that second IP
> address over to the 2003 Terminal Server's private IP.
> Having 2 public IP's should allow administrative RDP
> traffic to still route to the SBS server on the first IP,
> while the 2nd IP traffic is forwarded to the TS server.
> Is my concept correct? Is it the recommended way? How do
> I put it into effect? I think I know how to bind a second
> IP address to the NIC but the rest I need some guidance
> with. Sorry for the novel. THANKS in advance!

That worked awesome!! Thank you so much!!

>-----Original Message-----
>I assume you are not running ISA, and you have configured
RRAS on the SBS
>server to provide NAT routing. In this scenario, you do
not need a second
>IP address. Go to Administrative Tools and open the RRAS
console. Expand
>IP Routing and click NAT/Basic Firewall. In the right
pane right click your
>Internet adapter and select Properties. Make sure the
firewall is enabled
>(this is the default), then click the Services and Ports
tab. Check the box
>for Remote Desktop - click the Edit button and enter the
IP address for the
>Terminal Server.
>
>Doug Sherman
>MCSE Win2k/NT4.0, MCSA, MCP+I, MVP
>
>"David Maxwell" <(E-Mail Removed)>
wrote in message
>news:88b901c403c3$f18cd060$(E-Mail Removed)...
>> I have a dual-nic SBS 2003 server with a public IP on
the
>> one nic and a private IP on the other nic. I also have
a
>> 2003 server on the network behind the SBS 2003 server.
>> This second server will function as our Terminal Server.
>> My question is how will public/Internet users access the
>> Terminal Server. Normally I would port-map 3389 at the
>> public interface of a router through to the private IP
of
>> the server. I understand port mapping quite well, but I
>> don't know how to do it on a Windows server, nor do I
know
>> if this is the recommended way. I am guessing that I
can
>> bind a second public IP address to the public nic on the
>> SBS 2003 server and then port map 3389 for that second
IP
>> address over to the 2003 Terminal Server's private IP.
>> Having 2 public IP's should allow administrative RDP
>> traffic to still route to the SBS server on the first
IP,
>> while the 2nd IP traffic is forwarded to the TS server.
>> Is my concept correct? Is it the recommended way? How
do
>> I put it into effect? I think I know how to bind a
second
>> IP address to the NIC but the rest I need some guidance
>> with. Sorry for the novel. THANKS in advance!
>
>
>.
>