Discussion Locked

Windows 2000 as router

0 helpful
11 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Hi,
I have the following case.
windows 2000 with 3 nic.
1- first nic has 10.0.0.1 IP for internal lan
2-second nic has 213.x.x.x internet connection
3-third nic has 172.0.0.1 DMZ zone.
the problem is the windows 2000 cannot handle the routing. no one in the LAN can ping and pc at DMZ they only can ping the third nic adderss
can you tell me how to make w2k handle routing isuue I did alot configration but didnt work

11 replies

by timwalsh

You can do routing only if you are using Win2K Server. It will not work will Professional.

Routing is enabled through the RRAS service.

by engehab

I,m using windows 2000 server , and there is checkpoint installed on the server how this can help

by engehab

I,m using windows 2000 server , and there is checkpoint installed on the server how this can help

by bazz00

You need to setup RRAS - Routing and Remote Access on the W2k Server this will initiate Nat and allow communication between the 3 Nics thus allowing the users in the DMZ zone to ping/connect to the 1st and 2nd Nics. At the moment you have the 2nd Nic on a public address and the other two on private addresses but on different subnets. The routing part of RRAS will allow comunication between the the different subnets. NAT will resolve the private IP addresses to the public address allowing internet connection another way of doing this is to set up ICS - Internet Connection Sharing.

by nettek

I suspect that responses coming from the 172.0.0.0 network are being sent out on the Internet, and not back onto your 10.0.0.0 LAN. You need to create a routing table.

Add two persistent route statements:
C:\route.exe -p add 10.0.0.0 mask 10.0.0.1
is whatever you are using as the subnet mask for the 10.0.0.0 subnet. The -p makes the route stay after reboot. This statement creates an entry in the server's routing table that states "Send any traffic that comes into the server and is destined for the 10.0.0.0 network out the 10.0.0.1 NIC.
Repeat this for the other subnet:
c:\route.exe -p add 172.0.0.0 mask 172.0.0.1

Set 213.x.x.x as the default gateway. All other traffic will then go out that NIC.

This discussion is closed to new replies.