2003 DC Multihomed - 1 Nic won't answer - help!!

I have a new installation of windows standard sp1 + all svc paks, dc,
multihomed, with one nic talking to a public network and one to an internal
network. Different services on the server are tied to the 2 different nics,
service a runs on nic a, svc b runs on nic b - you get the idea. When one of
the nics has a default gateway setup, lets say nic a, then nic b won't answer
for the services that are tied to it. If I change the default gateway to one
on nic b's subnet instead then nic b will answer but it is like nic a has
gone to sleep, no answer. I have disabled the automatic metric on each of the
nics, set them both equal to 1, w/ 2 default gateways and I have created
routing table entries for each of the networks and both nics will answer
about 1/2 the time, the other half the nic that isn't listed in the routing
table as the default gateway is as if it is asleep, and it won't wake up with
incoming port hits. Does anyone have any suggestions please!! Thanks

You can only have one default gateway per machine, not one per
interface. So delete the default gateway address from one of the NICs. If
this machine is connected to a public network, that is where the default
route should point.

Services which run on your LAN should all be tied to the private NIC.

Jeff wrote:
> I have a new installation of windows standard sp1 + all svc paks, dc,
> multihomed, with one nic talking to a public network and one to an
> internal network. Different services on the server are tied to the 2
> different nics, service a runs on nic a, svc b runs on nic b - you
> get the idea. When one of the nics has a default gateway setup, lets
> say nic a, then nic b won't answer for the services that are tied to
> it. If I change the default gateway to one on nic b's subnet instead
> then nic b will answer but it is like nic a has gone to sleep, no
> answer. I have disabled the automatic metric on each of the nics, set
> them both equal to 1, w/ 2 default gateways and I have created
> routing table entries for each of the networks and both nics will
> answer about 1/2 the time, the other half the nic that isn't listed
> in the routing table as the default gateway is as if it is asleep,
> and it won't wake up with incoming port hits. Does anyone have any
> suggestions please!! Thanks