Windows 2000 NLB Network Adapter Limits

This article covers the network adapter limitations and configurations available in Microsoft Windows 2000 Network Load Balancing (NLB). It examines the maximum number of adapters NLB can bind to per host, the standard deployment models supported by the operating system, and the distinction between individual host adapter limits and overall cluster capacity.

In Microsoft Windows 2000 Advanced Server and Datacenter Server, Network Load Balancing can bind to a maximum of one network adapter per host. The NLB driver cannot be bound to multiple network adapters on the same machine to load-balance multiple virtual clusters across distinct interfaces on that single host.

While NLB only binds to a single network interface card (NIC), Windows 2000 supports two distinct physical adapter architectures on each cluster host:

• Single-Adapter Configuration: The host uses only one network adapter. In this topology, the single adapter handles both NLB cluster traffic and dedicated point-to-point network traffic (such as remote management, domain communication, and file sharing). This setup requires using multicast mode if dedicated host-to-host communication within the cluster is necessary.
• Dual-Adapter Configuration: The host uses two network adapters. This is the Microsoft-recommended deployment architecture. The first adapter is dedicated entirely to handling NLB cluster traffic, while the second adapter manages standard point-to-point host traffic, internal communication, and administrative tasks.

Although a Windows 2000 server can physically contain multiple network adapters for other networking purposes, NLB itself will only bind to and operate over one adapter per cluster node. Additionally, while each individual node is restricted to a single NLB-bound adapter, an entire Windows 2000 NLB cluster supports a maximum of 32 participating host computers.