We’ve had a few calls from customers who have run into a particular issue when they’ve deployed NLB on a Windows Server 2008 cluster. Most of them have had older NLB deployments and thought we made a change to 2008 NLB to cause a problem. The installations with the issue have dual-NIC nodes with the default gateway on the Cluster NIC. This is the reported behavior:
Incoming search terms:
- netsh forwarding enabled (10)
- netsh forwarding (10)
- netsh ip forwarding (9)
- windows nlb default gateway (5)
- multiple network adapter for nlb (3)
- nlb 0x8004100a (2)
- windows server 2008 nlb configuration (2)
- nlb dual homed (2)
- nlb windows 2008 in two different subnets (1)
- windows 2008 nlb with 2 nics with differnet subnets (1)