Cannot Use Wlbs.exe Remote Control Commands From Load Balanced VPN Servers
Microsoft Knowledge Base Article: 269004 - If you use the Wlbs.exe command line to remotely control a Network Load Balancing (NLB) cluster node that is part of an NLB cluster that is load balancing Point-to-Point Tunneling Protocol (PPTP)
services, you may receive the following error message
L2TP Sessions Lost When Adding a Server to an NLB Cluster
Microsoft Knowledge Base Article: 248346 - When you are using Network Load Balancing (NLB)
to load-balance a cluster of Layer 2 Tunneling Protocol (L2TP)
servers, clients experience broken L2TP sessions when a server
is added to the cluster.
Network Load Balancing Connection to a Virtual IP Address Not Made Across a Switch
Microsoft Knowledge Base Article: 247297 - When you attempt to establish a connection to the virtual IP address of a Network Load Balancing (NLB)
cluster, the connection cannot be made across a switch. When the
cluster is connected to a hub with a client, the client is able
to make a connection without a problem.
Network Load Balancing Component Calls Itself WLBS
Microsoft Knowledge Base Article: 221971 - When you are using the command interface or accessing information in Event Viewer, the Network Load Balancing (NLB) component is called WLBS.
Network Load Balancing Does Not Have a Virtual Network Adapter
Microsoft Knowledge Base Article: 240993 - Microsoft Windows NT Load Balancing Service (WLBS) in Microsoft Windows NT 4.0 creates a "WLBS Virtual NIC"
entry on the on the Adapters tab in the Network tool in Control
Panel.
Network Load Balancing May Stop in Unicast Mode with Some FDDI Network Adapters
Microsoft Knowledge Base Article: 254110 - Describes why Network Load Balancing (NLB) in unicast mode may not work with all Fiber Distributed Data Interface (FDDI)
network adapters.
Network Load Balancing Cluster no Longer Responds to Simple Network Management Protocol Requests
Microsoft Knowledge Base Article: 280307 - Under the following conditions, when all hosts in an Network Load Balancing (NLB)
cluster are stopped and then started again, the cluster no
longer responds to Simple Network Management Protocol (SNMP)
requests:
Network Load Balancing Temporarily Fails in a Switched Environment
Microsoft Knowledge Base Article: 261957 - When you use Network Load Balancing (NLB) with a Layer 2 switch, load balancing clients may experience a brief, temporary disruption of service when a new NLB
server is added to, or an "old" server is removed from the
cluster.
Network Load Balancing Temporarily Fails in a Switched Environment
Microsoft Knowledge Base Article: 261957 - When you use Network Load Balancing (NLB) with a Layer 2 switch, load balancing clients may experience a brief, temporary disruption of service when a new NLB server is added to, or an "old" server is removed from the
cluster.
Network Load Balancing WMI Provider Memory Leak
Microsoft Knowledge Base Article: 266375 - The Network Load Balancing (NLB) Windows Management Instrumentation (WMI) provider leaks significant amounts of memory in the Winmgmt process. In testing scenarios, the leak has been as much as 20 MB in 10
hours.
"NLB Failed to Start" Error Message If NLB Is Not Installed
Microsoft Knowledge Base Article: 268437 - The following error message may be placed in the System log during startup: Event ID: 7000 Event Source: Service Control Manager Description: The Network Load Balancing service failed to start due to the
following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. Network Load Balancing is not installed on the system. Cause: Although Network Load Balancing (NLB) is not currently installed, some NLB
registry keys may be present in the registry.
NLB Operations Affect All Network Adapters on the Server
Microsoft Knowledge Base Article: 222079 - Certain network load balancing (NLB) operations affect all network adapters detected on the computer.
"Proxy Chain Loop" Error Message Using Proxy Server and NLB
Microsoft Knowledge Base Article: 269165 - After you install Network Load Balancing (NLB) with Proxy Server 2.0, you may receive the following error message in your browser:
WLBS Does Not Detect Program or Service Problems
Microsoft Knowledge Base Article: 234151 - Windows NT Load Balancing Service (WLBS) and Windows 2000 Network Load Balancing (NLB) doe 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.
Using Crossover Cable Causes Load Balancing Not to Work
Microsoft Knowledge Base Article: 242248 - Although cluster nodes may be able to ping each other, other devices on the same subnet may not be able to ping the cluster IP address, or may not be able to gain access to TCP services configured for load balancing.
Using the "WLBS QUERY" Command to Determine the State of an WLBS/NLB Cluster
Microsoft Knowledge Base Article: 242242 - The wlbs query command displays the current state of a Windows Load Balancing Service (WLBS)/Network Load Balancing (NLB) cluster. Additionally, it provides host priority information. |
