>> nt and 2k only support 2 cards if they're on the same subnet -
>> or I should say they work most of the time... But there are bugs

I have a client with 2 network cards in an NT system on different
subnets.  It works.  And the rush calls when it stops working for
no apparent reason are just unplanned revenue.  I'd rather they
run Linux...


> I have customers with 5 or 6 NICs in their NT machines routing
> across different subnets, and it works like a champ.  Anyone who
> claims you can only have 2 network cards in an NT machine just
> doesn't know what they're talking about, and anyone who would
> suggest having two network cards in the same machine on the same
> subnet just doesn't understand TCP/IP, as there would be very
> little, if any, benefit to such an arrangement, and could cause
> lots of problems.

Actually, the multiple NICs on a single subnet is being suggested
now by Intel and Microsoft.  (Mind you, I'm not contradicting the
above statement "just doesn't understand TCP/IP".)

Only one card is active at a time.  The second NIC is used as a
fall-back for high availability servers.  I suspect the automatic
switch-over to the second NIC fixes random problem(s) while
reinitializing the network stack.

                                                Lee Jones

--
http://www.piclist.com hint: The PICList is archived three different
ways.  See http://www.piclist.com/#archives for details.