yes - it's true, you cannot have multiple default gateways when you have
multiple nic's connected to different networks.
http://www.microsoft.com/technet/pro...g/tcpip03.mspx explains this. Specifically, it says:
When a computer is multihomed with NICs attached to disjoint networks
(networks that are separate from and unaware of each other, such as a private
network using private addressing and the Internet), routing problems may
arise. It is often necessary to set up static routes to the private networks
in this situation.
When configuring a computer to be multihomed on two disjoint networks, the
best practice is to configure the default gateway on the interface connected
to the largest and least-known network, in which the default route summarizes
the most destinations. Then, either add static routes or use a routing
protocol to provide connectivity to the hosts on the smaller or better-known
network. Avoid configuring a different default gateway on each side; this can
result in unpredictable behavior and loss of connectivity. For more
information, see Default Gateway Behavior for Windows TCP/IP.
"Marc Hoffman" wrote:
> We're trying to put a second NIC into a Server 2003 Standard box. The reason
> is as follows:
>
> NIC 1 is on our DMZ
> NIC 2 is on our LAN for access by our backup server
>
> After putting in the second NIC we receive a warding that Windows does not
> play well with multiple, default gateways. This is apparently true, as
> Windows gets "confused", and connections are dropped intermittently between
> computers on the LAN and the server itself. It's as if it doesn't know which
> NIC to send replies through. Is there something that I'm missing here? There
> has to be a way to use multiple NICs on multiple network segments on a
> Server operating system, right??
>
> Thanks in advance.
>
>
Similar Threads
Linear Mode
