Article ID: 234151 - Last Review: December 5, 2007 - Revision: 3.7 The load balancing service does not detect program or service problems in Windows 2000, in Windows NT, in Windows Server 2003This article was previously published under Q234151 On This PageSUMMARY
Windows NT Load Balancing Service (WLBS), Windows 2000 Network Load Balancing (NLB), and Windows Server 2003 NLB do not provide failover at the service, program, or port level because both WLBS and NLB are TCP/IP load balancers and are not designed to detect when a program or service is not working correctly.
MORE INFORMATION
For example, if Microsoft Internet Information Server (IIS) does not work on a cluster node and WLBS or NLB is still running on the node, port 80 or Web packets continue to be routed to the WLBS or NLB node. You may receive program error messages on the host because the program is not running there, but the service does not failover to the other hosts because of WLBS and NLB design limitations.
When a program does not work, the cause is usually more complex than the service not responding on a port. WLBS and NLB rely on external monitoring tools for decision-making processes and remote control if a host needs to be removed from the cluster. Some independent monitoring tools can control cluster membership based on the availability of content. You can use these tools to monitor programs and services and send a command to stop WLBS or NLB on the node with the unsuccessful program or service. The program or service is removed from the WLBS or NLB cluster and does not receive any further traffic until it rejoins the cluster. Examples of monitoring tools
Third-party monitoring tools
For more information, click the following article number to view the article in the Microsoft Knowledge Base: 233178
(http://support.microsoft.com/kb/233178/
)
Third-party monitoring programs monitor applications and ports
| Article Translations
|
Back to the top
