Q1:
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?
A1: 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.
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
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.
In the Select Routing Protocol
dialog box, click NAT/Firewall, ... Symptoms: You
have windows 2003 multihomed server with DNS and NAT/Firewall.
...
www.chicagotech.net/nat.htm
Resolution: When establishing VPN
to the office A, the routing table changes. To fix this issue,
disable the "Use default gateway" on the Office A VPN ...
www.chicagotech.net/routingissuesonvpn.htm
3) Also rather than adding static
routes, you could configure the 2 routers to dynamically learn each
others routes via a routing protocol like RIP or OSPF. ...
www.chicagotech.net/routing.htm