Windows 2003 network load balance

ok - i have 2 servers that I want to cluster using NLB.
Each server has 3 network cards.
1 NIC is for the external (clustered) IP
1 NIC for internal traffic
1 NIC for management - the cluster heartbeat should go on this one.
I configured a static ip for the cluster - and the private IPs were the
existing static ip of the cards that are clustered.
the problem is where do i tell it to use another nic for the heartbeat? it
appears from looking at the activity light on the system that it is doing the
heartbeat on the cluster IP -- which is an external IP and that's not good
networking...

thanks for the help.
Sandy

3 NICs? That doesn't sound right. Often, there is not even a business need
for 2 NICs and you are wanting to go with 3. If I were you I would ask over
in microsoft.public.windows.server.clustering. However, I'll leave you with
this for now.

Quoted from:
http://www.microsoft.com/technet/pro...ing/nlbbp.mspx

Multiple NICs in cluster nodes

Windows 2000:

. If you have 2 NICs on different subnets then the NIC to which NLB is
bound should have default gateway and the routing tables need to be
reconfigured to make all traffic go thru the NLB NIC. Default gateway
setting on the other NIC should be blank.

. If you have 2 NICs on the same subnet you will need to configure the
NIC to which NLB is bound with the default gateway. The other NIC should not
have a default gateway configured. No need to hack routing tables.

. Recommendation is to use one NIC in each node unless there is a
business need for 2 NICs


Windows Server 2003

. If you have 2 NICs different subnets you can choose to bind NLB to
either or both NICs without any issues. All traffic will go thru the correct
NIC (subnet)

. If you have 2 NICs on the same subnet traffic will be routed
accordingly.

--
Todd J Heron, MCSE
Windows Server 2003/2000/NT
----------------------------------------------------------------------------
This posting is provided "as is" with no warranties and confers no rights