NLB Problems

I have created 2 servers in Hyper-V both are Windows Server 2003 x64
Standard. Each has one NIC Card. I walked through the setup of NLB and was
able to create the NLB name, and join a host to the NLB, however after the
Host was added, each of the servers are unable to see other network
resources, and no other resources can seen them.

NLB Cluster = xxx.xxx.202.129
Server A = xxx.xxx.202.130
Server B = xxx.xxx.202.131

In NLB Manager, both hosts have a red circle with a white x, and they log
states "Host unreachable, error contacting to "server a"

I am in NLB Manager on a remote machine, and after enabling the NLB on
Server A and Server B, the third machine (where nlb manager is running) is
unable to see either of the hosts, or the nlb name via ping.

I found the problem, and I had left the default of "unicast" mode in the NLB
setup. By changing this to multicast mode, it appears to have resolved the
problem. I also changed the NIC card to a "Legacy Network Adapter", but am
not sure if this had something to do with it either.

--
-Nick


"NickDS" wrote:

> I have created 2 servers in Hyper-V both are Windows Server 2003 x64
> Standard. Each has one NIC Card. I walked through the setup of NLB and was
> able to create the NLB name, and join a host to the NLB, however after the
> Host was added, each of the servers are unable to see other network
> resources, and no other resources can seen them.
>
> NLB Cluster = xxx.xxx.202.129
> Server A = xxx.xxx.202.130
> Server B = xxx.xxx.202.131
>
> In NLB Manager, both hosts have a red circle with a white x, and they log
> states "Host unreachable, error contacting to "server a"
>
> I am in NLB Manager on a remote machine, and after enabling the NLB on
> Server A and Server B, the third machine (where nlb manager is running) is
> unable to see either of the hosts, or the nlb name via ping.