Discussion Locked

Multi-homed NT4.0 Server

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

I have a multi-homed NT4.0 Server. I am attempting to configure it as a router and have not been successful. The setup is as follows:

NT 4.0 Server SP6a
2 NICs (1 intel, 1 3com)
Bridged DSL router configured on intel NIC with a static IP address of 216.87.87.110, 255.255.255.0 (This is the only valid IP given by the ISP)
3com NIC configured with a static IP of 10.0.0.200, 255.255.255.0 connected to an Intel hub.
IP Forwarding has been enabled.

Present Status:
All workstations are receiving the correct IP information from the DHCP Server with a gateway of 10.0.0.200. They can see the server and each other. They can ping both NICs on the server but are unable to ping the router.
The server can ping the router and can surf the internet no problem as well as see all computer on the network.

What am I missing in this config? I have gone through all of the Technet Q articles I can find without success.
Any suggestions??

13 replies

by jaystar

The 10.x.x.x address space is reserved for private networks only. the packets (pings) are mostly likely getting to your DSL router, but it doesn't know how to send them back. It will see that it doesn't have a direct connection and either :
1) realize it is a private address and not forward it on or
2) forward it on to the next router to find it's destination.

The point here is the 10.x.x.x network sceme will not route on the internet. Instead of just routing, you are looking for NAT (Network Address Translation). Windows 2000 comes with NAT, and there are several packages you can purchase (Checkpoint Firewall for one) which will do this on NT.
NAT will take your 10.x.x.x address and turn it into your public range (for you 1 IP) and associate the connections with port numbers. This allows several IP's in the 10.x.x.x range APPEAR as if they are all being requested from your single public IP.

Hope this helps you, and if you need anything else on the topic, feel free to contact me.

Jay Starling
MCSE, ASE

by otto3

The previous poster is right about the non-routable 10.x.x.x address range and the need for NAT. However, depending on your network the Check Point firewall might be an expensive solution. There are other options for a fraction of that cost. You could replace your present DSL router, which would do NAT for about $200. One such product is Linksys Etherfast Four-Port Cable/DSL Router, http://www.linksys.com. It can support up to 253 connections, just use one of the ports to uplink to your switches. It can also serv as a DHCP server. If you decide to use it, then the connections to the Internet don't need to go through your NT server. Then there is all of the software solutions, which can do NAT and you'd install it on your NT server. MS Proxy 2.0 is about $100.00 on Ebay. It all depends on your budget.

Otto

by nettek

When users ping the router, the router is sending responses to the ISP side of router, not back to your network. On your multi-homed server, no gateway should be installed on under TCP/IP properties for the internal NIC. The gateway for the external NIC should be the IP address of the DSL router. You need to tell the multi-homed server where to respond to addresses from the Net ID 10.0.0.0. To do this, add the following route statement from a command prompt on the server: c:\route.exe add -p10.0.0.0 mask 255.255.255.0 10.0.0.200. The -p tells the server to keep the route statement on reboot. 10.0.0.0 is the Net ID of your LAN. 255.255.255.0 is the subnet mask of your LAN. 10.0.0.200 is the gateway for your LAN.

by Former member

YOur NT server is not capable of NAT (in it's native form) as this is what you need, or Internet Connection sharing. A real router with NAT or ICS services is a better idea...Don't get a cheapo Linksys, get a Cisco if this is a serious network...

by it's not easy being green

All of the others are correct, without NAT you can't do this. 2 choices from here. Most routers I have seen come with some type of NATing options. Talk to your ISP or owners manual to find out if your has this option.
Your other choice (just because we all love Microsoft) is Proxy server. If you install Proxy server and turn off IP routing, you will be live on the internet as soon as the client software is installed on your workstations. Good Luck.
Ian

by bill.parks

STOP!!! You can do this without buying anything! I will go out on a limb here, but I am assuming you do as everyone else does instinctly by adding a default gateway on both NIC's. Under TCP/IP Properties, remove the default gateway entry on your internal side, 10.x.x.x. If you do a "route print" at a command box, you should see only one entry for 0.0.0.0 (this is "default" gateway in NT), and it should point to your external NIC. All packets heading towards anything but 10.x.x.x will go your external side. Don't complicate the issue either, if you have added static entries, remove them, and get back to the basic config you started with when composing this question. BTW, this is how MS Proxy is set up, RRAS, and MS Exchange w/a public side.

This discussion is closed to new replies.