Windows Forum

Ask something
Discussion Locked

Routing through an NT server

0 helpful
7 replies

by tancred

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
We are trying to set up an NT 4 server with two nics - one connected to the internet and the other to an internal network. The intention is to install a software firewall on this server. Temporarily we are using public ips until everything is set up. We enabled IP forwarding and installed the RIP for Internet service but we cannot ping from the internal network to the internet and vice versa. Pinging from the 'gateway' both internally and externally works but no connectivity exists through the'gateway'. Is there some additional configuration required?

7 replies

by nagazaki

In the IP properties on the computer in your LAN, in gateway set the IP of your router's 'internal LAN NIC'.

You can also add the IP & the name of the router in your hosts file (winnt\system32\drivers\etc).

reboot and have a look

by tancred

That is how the computers are set up and they manage to ping both nics (internal and external) on the gateway but not anything beyond that.

by nettek

I am guessing that responses to your Pings are being sent out the external nic, rather than back onto your network via your internal nic. Try using a Route statement on the server. For example:

c:\route -p add mask

The "-p" makes the route persistant, even after reboot, until you remove it with the Route Delete command. Network-ID is your LANs network ID (207.1.125.0, for example). Subnet mask is your subnet mask for your network (255.255.255.0, for example). Gateway would be the IP address of your internal nic (207.1.125.101, for example). This command basically tells your server that to get to your LANs IP addresses, it must use the internal nic.

Hope that helps.

by tom

I'm doing the same thing with a Win2K macine. One trick I discovered is that I had to leave the 'gateway' field blank on the properties of the internal network NIC.

by tancred

It was a question of settings at the ISP level. They did not tell me what they did exactly but must have been something to do with routers.

This discussion is closed to new replies.