Re: 2 WAN + 1 LAN on 1 box
- From: "Bill Grant" <not.available@online>
- Date: Wed, 21 Feb 2007 09:44:10 +1100
You can only have one default gateway per machine, not one per interface.
Put both IPs on one NIC. Set the default geteway on it. Leave the default
gateway on the LAN NIC blank.
"1388-2/HB" <1@xxxxx> wrote in message
news:P7JCh.15982$O02.2379@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx
I have a 2003 server acting as a webserver. It has 3 nics in it:
WAN #1: 72.18.243.A / 255.255.255.248
WAN #2: 72.18.243.B / 255.255.255.248
LAN: 172.16.2.C / 255.255.255.0
IIS6 is running 2 websites. Website A is listening on WAN .A, and website
B is listening on WAN .B. The LAN nic does not run a website.
Here's what I think I know, stop me where I'm wrong:
I should not assign a default gateway to the LAN nic while either WAN nic
also has a default gateway assigned, because default gateways on different
subnets is "bad".
If I create a 0.0.0.0 route of last resort in RRAS that routes through WAN
.A, requests for WAN .B will appear to come from WAN .A which is
erroneous, and vice versa if 0.0.0.0 routes through WAN .B. A request
sent to WAN .B needs to be returned by WAN .B and a request sent to WAN .A
needs to be returned by WAN .A.
I can assign default gateways to my WAN nics .A and .B because they're on
the same subnet. They both have the same gateway.
Because I cannot assign a default gateway to LAN once a default gateway
has been assigned to WAN, I can create a 172.16.2.0 route in RRAS that
routes local traffic through the LAN nic.
So this is how I configure TCP on each nic:
WAN #1: 72.18.243.A / 255.255.255.248
default gateway 72.18.243.G
WAN #2: 72.18.243.B / 255.255.255.248
default gateway 72.18.243.G
LAN: 172.16.2.C / 255.255.255.0
[no default gateway]
And then in RRAS, one static route is created:
172.16.2.0 / 255.255.255.0
routes to 172.16.2.G via LAN nic 172.16.2.C
The problem is that when I set this up, everything works fine for an
arbitrary period of time (say a week) before the server will spontaenously
decide it doesn't want to route packets over either of it's WAN interfaces
anymore. From the WAN side of the network, I can no longer ping either
WAN nic .A or .B (and I can't visit the website either). However, during
this time of WAN routing failure I can ping and visit the website from the
LAN side of the server. IIS remains functional and as far as I can tell
this is a routing problem.
This is driving me nuts, what am I doing wrong? I don't know how else to
configure this box.
.
- Prev by Date: Re: Burning Win2003 CD, but burned CD is not bootable. Why?
- Next by Date: Re: sorry for the re-post...
- Previous by thread: internet explorer 7, wsus
- Next by thread: Offline Folders
- Index(es):
Relevant Pages
|
