Discussion Locked

Multihomed Win2K server

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

I need to have 3 NICs with 3 different gateways..
#1 - 192.168.1.xx >>> router >>> Internet IP
#2 - 192.168.2.xx >>> router >>> Local LAN
#3 - 192.168.3.xx >>> router >>> Internet IP
2 NICs are for 2 web site & 1 for local LAN, but
all 3 use different routers so must have different gateways. W2K does not work properly
and gives warning when you set uo differnet gateways.. Any Ideas ??
( NT4 works fine in this configuration )

5 replies

by mford66215

You'd better have the perfect mask to go with this or they'll end up being the same LAN. If your mask is only 24 bits, then they WOULD all be the same Lan and W2k should complain about the different gateways. What's the mask your using for these nics?

by kenlevy

Win2K will only allow one default gateway per OS. If you issue a "route print" command, it will show you the default gateway. Multiple gateways can be defined (i.e., one gateway per NIC), but only one will be active at a time. If you do a search on MSFT's site for "dead gateway detection" you'll find a couple of articles detailing on how the gateways get migrated.

If you know all the Local LAN subnets accessd by the router attached to NIC #2, you can set up static route table entries on the server (use the "route add" command) to and set the next hop/gateway address for each of the local subnet entries to the router giving access to the Local LAN.

See next response for handling the Internet gateway issue.

by kenlevy

See my other answer for handling the Local LAN traffic. The issue is then how to handle the Internet traffic. Problem is when you have the two different web sites on the same machine serviced by two different routers.

If that traffic is coming from a wide variety of addresses, a static route table solution won't work.

What I've come up with (but haven't completed the testing) involves the use of content-based routing facility in the routers. I'm testing using a couple of very low end Cisco 87x units, where we'll let the routers sort out the traffic to the correct ISP.

Here is the setup:
Router 1: NATs public traffic to 192.168.1.x subnet and 1.x web site
Router 2: NATs public traffic to 192.168.3.x subnet and 3.x web site

Router 1 and 2 are connected together through a 192.168.4.x address for inter-router traffic.

Set up the Win2K gateway to one of the two routers (lets use 1.x for this example). Now, all external addressed traffic will be routed to that router.

Use content-based routing command to examine the "source address" of the outbound traffic on the 1.x router. The source address is the address of the web server that handled the original request to the web server. It will be either from the 1.x subnet or the 2.x subnet). Set the next hop address in the content-based routing rule depending on the source. If the source is from the 1.x subnet, set the next hop to the 1.x routers normal gateway. If the source is from the 2.x address, set the next hop address to the dedicated inter-router 4.x address of the 2.x router. The packets for that ISP will have to transit the 1.x router first, but will go out through the 2.x router. On outbound traffic, NAT address translation is handled after the content based routing in the Cisco stack, so the NAT should work just fine.

I'm still experimenting with this (as well as Win2003 server Network Load Balancing). I think it might work for you, though.

by jhoward501

You lost me on the "content based routing"..
I'm using 3 Linksys BEFSR81 routers..so I don't
have much flexibility there. It appears that the only way to connect to the IP assigned to a specific router is to use that routers address
as the gateway for the NIC..
The basic problem is that Windows is a terrible OS
and I may have to use Linux but don't want the learning time required.

This discussion is closed to new replies.