Remote desktop routing through W2k3 server HOW

Hi
I just installed a new sbs2003 with two networks.

NIC #1 192.168.1.1 = is local to all clients
NIC #2 192.168.2.2 = is connected to the Internet DSL router

This means the Server firewall is between clients and internet.

The DSL router forwards port 3389 to a client with a static IP of
192.168.1.100
I can attach remote connection from the server to the client
(Proving client is ready)

I can remote connect from the internet to the server
(proving the server is ready)

==================================================
I cannot connect from the internet through the server to the client!
==================================================

Surely some form or routing must be setup. But where and how.
I am not familiar with routing an example would be appreciated.
Or is it just a firewall setting?


Thanks
Dekaya

In news:(E-Mail Removed),
(E-Mail Removed) <(E-Mail Removed)> typed:
> Hi
> I just installed a new sbs2003 with two networks.

NB: SBS questions are best asked in microsoft.public.windows.server.sbs. SBS
is its own beast and does a lot of things its own way.

>
> NIC #1 192.168.1.1 = is local to all clients
> NIC #2 192.168.2.2 = is connected to the Internet DSL router
>
> This means the Server firewall is between clients and internet.

I don't recommend using that, myself. I would suggest a hardware firewall
appliance if you aren't using Premium (with ISA), and in that case, I
wouldn't use two NICs
at all.

>
> The DSL router forwards port 3389 to a client with a static IP of
> 192.168.1.100
> I can attach remote connection from the server to the client
> (Proving client is ready)
>
> I can remote connect from the internet to the server
> (proving the server is ready)
>
> ==================================================
> I cannot connect from the internet through the server to the client!
> ==================================================

What errors do you get?
>
> Surely some form or routing must be setup. But where and how.
> I am not familiar with routing an example would be appreciated.
> Or is it just a firewall setting?
>
>
> Thanks
> Dekaya

One question first - why are you using this rather than Remote Web
Workplace, which makes remote desktop available via a web page, and no
individual computer needs to be addressed directly via 3389 from there?
Using 443 and 4125, and https://my.publicdomain.com/remote or
https://mypublicIP/remote will get you there.

You should enable NAT on the SBS since it has two NICs. Then do port forwarding to point port 3389 to the 192.168.1.100.

You also have another two options: RWW and VPN.

NAT and Firewall How to enable NAT How to enable NAT name resolution How to enable inbound connections How to configure 2000/2003 NAT services and ports ...
http://www.chicagotech.net/nat.htm



Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
<(E-Mail Removed)> wrote in message news:(E-Mail Removed)...
Hi
I just installed a new sbs2003 with two networks.

NIC #1 192.168.1.1 = is local to all clients
NIC #2 192.168.2.2 = is connected to the Internet DSL router

This means the Server firewall is between clients and internet.

The DSL router forwards port 3389 to a client with a static IP of
192.168.1.100
I can attach remote connection from the server to the client
(Proving client is ready)

I can remote connect from the internet to the server
(proving the server is ready)

==================================================
I cannot connect from the internet through the server to the client!
==================================================

Surely some form or routing must be setup. But where and how.
I am not familiar with routing an example would be appreciated.
Or is it just a firewall setting?


Thanks
Dekaya

Hi Robert;
Thanks for responding.

I was pretty sure port forwarding was the answer but I just don't know
where on the server to go to do that.

I already did it and NAT on the Internet hub and it works when I point
it to the Server 192.168.2.2 So I know it is right
I of course then change it back to the client 192.168.1.100.



But where on the server do I port forward?

And in case I can't find it where do I enable NAT on the server?


Thanks
Dekaya






On Sat, 16 Sep 2006 10:02:59 -0500, "Robert L [MVP - Networking]"
<(E-Mail Removed)> wrote:

>You should enable NAT on the SBS since it has two NICs. Then do port forwarding to point port 3389 to the 192.168.1.100.
>
>You also have another two options: RWW and VPN.
>
>NAT and Firewall How to enable NAT How to enable NAT name resolution How to enable inbound connections How to configure 2000/2003 NAT services and ports ...
> http://www.chicagotech.net/nat.htm
>
>
>
>Bob Lin, MS-MVP, MCSE & CNE
>Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
>How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
> <(E-Mail Removed)> wrote in message news:(E-Mail Removed)...

On Sun, 17 Sep 2006 14:49:20 GMT, (E-Mail Removed) wrote:
On the SBS Server I found " Routing and Remote Access"
under NAT/firewal/Network Connection (192.168.2.2) properties I double
checked NAT was indeed enabled and on the Services and Ports Tab I
set the RemoteDesktop port to forward to 192.168.1.100
With the DSL router forwarding to 192.168.2.2 and the server
forwarding to 192.168.1.100 ..
Voila! IT worked.

Thanks so much!












>Hi Robert;
>Thanks for responding.
>
>I was pretty sure port forwarding was the answer but I just don't know
>where on the server to go to do that.
>
>I already did it and NAT on the Internet hub and it works when I point
>it to the Server 192.168.2.2 So I know it is right
> I of course then change it back to the client 192.168.1.100.
>
>
>
>But where on the server do I port forward?
>
>And in case I can't find it where do I enable NAT on the server?
>
>
>Thanks
>Dekaya
>
>
>
>
>
>
>On Sat, 16 Sep 2006 10:02:59 -0500, "Robert L [MVP - Networking]"
><(E-Mail Removed)> wrote:
>
>>You should enable NAT on the SBS since it has two NICs. Then do port forwarding to point port 3389 to the 192.168.1.100.
>>
>>You also have another two options: RWW and VPN.
>>
>>NAT and Firewall How to enable NAT How to enable NAT name resolution How to enable inbound connections How to configure 2000/2003 NAT services and ports ...
>> http://www.chicagotech.net/nat.htm
>>
>>
>>
>>Bob Lin, MS-MVP, MCSE & CNE
>>Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
>>How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
>> <(E-Mail Removed)> wrote in message news:(E-Mail Removed)...

Thank you for the update.

Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
<(E-Mail Removed)> wrote in message news:(E-Mail Removed)...
On Sun, 17 Sep 2006 14:49:20 GMT, (E-Mail Removed) wrote:
On the SBS Server I found " Routing and Remote Access"
under NAT/firewal/Network Connection (192.168.2.2) properties I double
checked NAT was indeed enabled and on the Services and Ports Tab I
set the RemoteDesktop port to forward to 192.168.1.100
With the DSL router forwarding to 192.168.2.2 and the server
forwarding to 192.168.1.100 ..
Voila! IT worked.

Thanks so much!












>Hi Robert;
>Thanks for responding.
>
>I was pretty sure port forwarding was the answer but I just don't know
>where on the server to go to do that.
>
>I already did it and NAT on the Internet hub and it works when I point
>it to the Server 192.168.2.2 So I know it is right
> I of course then change it back to the client 192.168.1.100.
>
>
>
>But where on the server do I port forward?
>
>And in case I can't find it where do I enable NAT on the server?
>
>
>Thanks
>Dekaya
>
>
>
>
>
>
>On Sat, 16 Sep 2006 10:02:59 -0500, "Robert L [MVP - Networking]"
><(E-Mail Removed)> wrote:
>
>>You should enable NAT on the SBS since it has two NICs. Then do port forwarding to point port 3389 to the 192.168.1.100.
>>
>>You also have another two options: RWW and VPN.
>>
>>NAT and Firewall How to enable NAT How to enable NAT name resolution How to enable inbound connections How to configure 2000/2003 NAT services and ports ...
>> http://www.chicagotech.net/nat.htm
>>
>>
>>
>>Bob Lin, MS-MVP, MCSE & CNE
>>Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
>>How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
>> <(E-Mail Removed)> wrote in message news:(E-Mail Removed)...