Windows Server 2003 acting as router
-
I am trying to setup a Windows Server 2003 server to act as a software router. It has 2 NIC's: NIC1 is the Private Network, with static IP, and null Gateway. NIC2 is the Public Network, with static IP, DNS, Gateway etc. I also runs DNS and DHCP services, along with AD (and aware of all the security issues...) I have run the RRAS wizard, and selected both private and public interface for NAT, as in http://www.windowsnetworking.com/articles_tutorials/NAT_Windows_2003_Setup_Configuration.html[^] The porblem is that only the server is succsfully connecting with outside world, while clients cannot access outside addresses. A ping of external site, by a clients, results in the address being shown of the site, and no reply. It is as if all incomming connings are blocked, or not correctly routed. What am I missing here ?
-
I am trying to setup a Windows Server 2003 server to act as a software router. It has 2 NIC's: NIC1 is the Private Network, with static IP, and null Gateway. NIC2 is the Public Network, with static IP, DNS, Gateway etc. I also runs DNS and DHCP services, along with AD (and aware of all the security issues...) I have run the RRAS wizard, and selected both private and public interface for NAT, as in http://www.windowsnetworking.com/articles_tutorials/NAT_Windows_2003_Setup_Configuration.html[^] The porblem is that only the server is succsfully connecting with outside world, while clients cannot access outside addresses. A ping of external site, by a clients, results in the address being shown of the site, and no reply. It is as if all incomming connings are blocked, or not correctly routed. What am I missing here ?
The clients default gateway is the IP or the interal NIC on the server right? a ping isn't really that good a test either, especially pinging external IPs. Haven't done this with Windows, but having setup PIXs and ASAs I'm not sure you want to enable NAT on the private interface. You want to NAT traffic from your internal LAN out through the public interface, but I'm not sure if this would be accomplished by enabling NAT on the private interface in Windows or not. Just out of curiosity if you type: "route print" at the command line, does it show 0.0.0.0 0.0.0.0 to have the gateway for external traffic? Any reason your not just using a Linksys or similar box to perform this?
-
The clients default gateway is the IP or the interal NIC on the server right? a ping isn't really that good a test either, especially pinging external IPs. Haven't done this with Windows, but having setup PIXs and ASAs I'm not sure you want to enable NAT on the private interface. You want to NAT traffic from your internal LAN out through the public interface, but I'm not sure if this would be accomplished by enabling NAT on the private interface in Windows or not. Just out of curiosity if you type: "route print" at the command line, does it show 0.0.0.0 0.0.0.0 to have the gateway for external traffic? Any reason your not just using a Linksys or similar box to perform this?
Hi, I changed the internal nic to static 192.168.10.3, with DHPC range 192.168.10.x. Public NIC is still the same, only now the DNS shows to the new internal address 192.168.10.3. Firewall is off on private interface. Clients can ping outside interface successfully. No static routes are defined(yet ?) No RIP enabled (yet) All Firewalling is of. No filters are defined. DHCP Router(Option3) set to 192.168.10.3 DHCP DNS Server(Option6) set to 192.168.10.3 DNS Interfaces set to 'ALL' DNS Forwarders set to ISP DNS1 and DNS2 Clients are unable to ping ISP DNS1 and DNS2, although server can. Should we have a look at RIP2 then and what do the settings need to be.
-
Hi, I changed the internal nic to static 192.168.10.3, with DHPC range 192.168.10.x. Public NIC is still the same, only now the DNS shows to the new internal address 192.168.10.3. Firewall is off on private interface. Clients can ping outside interface successfully. No static routes are defined(yet ?) No RIP enabled (yet) All Firewalling is of. No filters are defined. DHCP Router(Option3) set to 192.168.10.3 DHCP DNS Server(Option6) set to 192.168.10.3 DNS Interfaces set to 'ALL' DNS Forwarders set to ISP DNS1 and DNS2 Clients are unable to ping ISP DNS1 and DNS2, although server can. Should we have a look at RIP2 then and what do the settings need to be.
http://www.windowsnetworking.com/articles_tutorials/Configuring-Windows-Server-2003-act-NAT-router.html[^] Maybe this is the article you should be following.