Microsoft Windows 2000 Server and Windows Server 2003 Common NLB Events
Applies To: Windows Server 2003 with SP1
Event ID: 1
Alert Severity: Unused
Windows Server 2003 Event Text: NLB Cluster %2 %1: %3. %4
Windows 2000 Server Event Text: %4 %1: %2. %3
Event ID: 2
Alert Severity: Unused
Windows Server 2003 Event Text: NLB Cluster %2 %1: %3. %4
Windows 2000 Server Event Text: %4 %1: %2. %3
Event ID: 3
Alert Severity: Unused
Windows Server 2003 Event Text: NLB Cluster %2 %1: %3. %4
Windows 2000 Server Event Text: %4 %1: %2. %3
Event ID: 4
Alert Severity: l
Windows Server 2003 Event Text: NLB Cluster %2 %1: %3 started. %4
Windows 2000 Server Event Text: %4 %1: %2 started. %3
Error Message Explanation: This event is logged to inform you that cluster operations have started in response to a user-initiated action.
User Action (Windows Server 2003): No user action is required.
User Action (Windows 2000 Server): No user action is required.
Event ID: 5
Alert Severity: I
Windows Server 2003 Event Text: NLB Cluster %2 %1: Cluster mode started with host ID %2. %3
Windows 2000 Server Event Text: %4 %1 :cluster mode started with host ID %2. %3
Error Message Explanation: This event is logged to inform you that cluster operations have started in response to a user-initiated action.
User Action (Windows Server 2003): No user action is required.
User Action (Windows 2000 Server): No user action is required.
Event ID: 6
Alert Severity: I
Windows Server 2003 Event Text: NLB Cluster %2 %1: Cluster mode stopped. %3. %4
Windows 2000 Server Event Text: %4 %1: cluster mode stopped. %2. %3
Error Message Explanation: This event is logged to inform you that cluster operations have stopped in response to a user-initiated action.
User Action (Windows Server 2003): No user action is required.
User Action (Windows 2000 Server): No user action is required.
Event ID: 7
Alert Severity: E
Windows Server 2003 Event Text: NLB Cluster %2 %1: Internal error. Please contact technical support. %3 %4
Windows 2000 Server Event Text: %4 %1: Internal error. Please contact technical support. %2. %3
Error Message Explanation: Network Load Balancing Clustering cannot complete the task because an error occurred.
User Action (Windows Server 2003): Contact your product support person. For more information about product support, see Help and Support. Alternatively, see Product Support Services at https://www.microsoft.com/homepage/ms.htm.Under the Resources area in the navigation pane, point to Support, and then click Support Home.
User Action (Windows 2000 Server): Contact Microsoft Product Support Services. For more information about product support, see Help. Alternatively, see Product Support Services at https://www.microsoft.com/homepage/ms.htm. Under the Resources area in the navigation pane, point to Support, and then click Support Home.
Event ID: 8
Alert Severity: E
Windows Server 2003 Event Text: NLB Cluster %2 %1: Error registering driver with NDIS. %3 %4
Windows 2000 Server Event Text: %4 %1: Error registering driver with NDIS. %2. %3
Error Message Explanation: The Network Load Balancing driver cannot register with the Network Driver Interface Specification (NDIS). Therefore, the host will not respond to the TCP/IP traffic on this adapter.
User Action (Windows Server 2003): Restart your computer. If the problem continues, use Network Connections in Control Panel to disable and then re-enable the network adapter. If this does not resolve the problem, contact your product support person. For more information about product support, see Help and Support. Alternatively, see Product Support Services at https://www.microsoft.com/homepage/ms.htm. Under the Resources area in the navigation pane, point to Support, and then click Support Home.
User Action (Windows 2000 Server): Restart your computer. If the problem continues, use Network Connections in Control Panel to disable and then re-enable the network adapter. If this does not resolve the problem, contact Microsoft Product Support Services. For more information about product support, see Help. Alternatively, see Product Support Services at https://www.microsoft.com/homepage/ms.htm. Under the Resources area in the navigation pane, point to Support, and then click Support Home.
Event ID: 9
Alert Severity: E
Windows Server 2003 Event Text: NLB Cluster %2 %1: Driver does not support the media type that was requested by TCP/IP. NLB will not bind to this adapter. %3 %4
Windows 2000 Server Event Text: %4 %1: driver does not support media type that was requested by TCP/IP. %2. %3
Error Message Explanation: In order for Network Load Balancing (NLB) to work, it must bind to an Ethernet network adapter. This event is logged when the NLB driver cannot bind to an Ethernet network adapter because it is not supported.
User Action (Windows Server 2003): Verify that a supported Ethernet network adapter is installed in this computer, and then bind NLB to it.
User Action (Windows 2000 Server): Verify that a supported Ethernet network or Fiber Distributed Data Interface (FDDI) network adapter is installed in this computer, and then bind NLB to it.
Event ID: 10
Alert Severity: E
Windows Server 2003 Event Text: NLB Cluster %2 %1: Driver could not allocate a required memory pool. %3 %4
Windows 2000 Server Event Text: %4 %1: driver could not allocate required memory pool. %2. %3
Error Message Explanation: The Network Load Balancing (NLB) driver could not allocate memory.
User Action (Windows Server 2003): To increase the amount of available memory, try one of more of the following:
Add additional random access memory (RAM) to the host.
Close programs on the host that might be consuming memory.
Force the NLB driver to reload. Reloading will occur if you restart the host or disable all network adapters that are bound to NLB and then re-enable those adapters.
User Action (Windows 2000 Server): To increase the amount of available memory, try one or more of the following:
Add additional random access memory (RAM) to the host.
Close programs on the host that might be consuming memory.
Using Network Connections in Control Panel disable and then re-enable the network adapter that is bound to NLB.
Event ID: 11
Alert Severity: E
Windows Server 2003 Event Text: NLB Cluster %2 %1: Driver could not open device \DEVICE\ %3. %4
Windows 2000 Server Event Text: %4 %1: driver could not open device. %2. %3
Error Message Explanation: Network Load Balancing (NLB) cannot bind to the network adapter. A possible reason is that the medium is not supported.
User Action (Windows Server 2003): Bind NLB to an Ethernet network adapter. If you are already using an Ethernet network adapter, examine the status code of the event message. The returned status code is included in the Data area at the bottom of the Event Properties dialog box.
The status code will correspond to a specific error condition as follows:
0xC0010019 = The adapter specified is not supported. In this case, you need to use a different adapter.
0xC000009A = The requested operation failed because NDIS could not allocate sufficient memory or initialize the state it uses to track an open binding. For this status, try adding additional memory.
If the status code is not listed here or you cannot resolve the problem based on the information provided, contact your product support person. For more information about product support, see Help and Support. Alternatively, see Product Support Services at https://www.microsoft.com/homepage/ms.htm. Under the Resources area in the navigation pane, point to Support, and then click Support Home.
User Action (Windows 2000 Server): Bind NLB to an Ethernet network adapter. If you are already using an Ethernet network adapter, examine the status code of the event message. The returned status code is included in the Data area at the bottom of the Event Properties dialog box.
The status code will correspond to a specific error condition as follows:
0xC0010019 = The adapter specified is not supported. In this case, you need to use a different adapter.
0xC000009A = The requested operation failed because NDIS could not allocate sufficient memory or initialize the state it uses to track an open binding. For this status, try adding additional memory.
If the status code in the message is not listed here or you cannot resolve the problem based on the information provided, contact your product support person. For more information about product support, see Help. Alternatively, see Product Support Services at https://www.microsoft.com/homepage/ms.htm. Under the Resources area in the navigation pane, point to Support, and then click Support Home.
Event ID: 12
Alert Severity: E
Windows Server 2003 Event Text: NLB Cluster %2 %1: Driver could not announce virtual NIC \DEVICE\ %3 to TCP/IP. %4
Windows 2000 Server Event Text: %4 %1: driver could not announce virtual NIC %2 to TCP/IP. %3
Error Message Explanation: This event is logged to inform you that a call to Network Driver Interface Specification (NDIS) in order to bind the TCP/IP protocol to Network Load Balancing failed.
User Action (Windows Server 2003): No user action is required.
User Action (Windows 2000 Server): No user action is required.
Event ID: 13
Alert Severity: W
Windows Server 2003 Event Text: NLB Cluster %2 %1: Driver temporarily ran out of resources. Increase the %3 value under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WLBS\Parameters\{GUID} key in the registry. %4
Windows 2000 Server Event Text: %4 %1: driver temporarily ran out of resources. Increase the %2 value under \SYSTEM\CurrentControlSet\Services\%4\Parameters key in the registry. %3
Error Message Explanation: When the Network Load Balancing (NLB) driver loads, NLB allocates blocks of memory for internal use. While this driver was loading, more memory was required than was initially allocated. Usually this is an indication that the load-balanced program is very heavily utilized.
User Action (Windows Server 2003): NLB does not automatically increase the amount of memory used for its internal processes. Instead, advanced users can manually increase the value in the registry. The path to the registry key specified in the logged event is incorrect. The correct path is: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\WLBS\Parameters\Interface\{GUID}. The registry key to change is specified in the message. The GUID is the globally unique identifier of the network adapter that is experiencing the problem. This is the network adapter that is bound to NLB. If NLB is, or has been, bound to multiple network adapters, you can find the correct adapter by looking at the value for the ClusterIPAddress key for each GUID entry in the registry.
It is recommended that you double the existing value of this registry key. After increasing the value, you must re-bind NLB to the adapter that was experiencing the problem. To do this, do one of the following:
Restart the host,
Disable and then re-enable the appropriate network adapter, or
Remove and then re-add NLB to the appropriate network adapter
If increasing the value does not correct the problem, contact your product support person. For more information about product support, see Help and Support. Alternatively, see Product Support Services at https://www.microsoft.com/homepage/ms.htm.
Under the Resources area in the navigation pane, point to Support, and then click Support Home.
For more information about Windows Registry best practices, see Help and Support.
User Action (Windows 2000 Server): NLB does not automatically increase the amount of memory used for its internal processes. Instead, advanced users can manually increase the value of the specified registry key. It is recommended that you double the existing value. After increasing the value, reload NLB. To do this, do one of the following:
Restart the host,
Remove and then re-add NLB to the network adapter that is bound to NLB, or
Disable and then re-enable the appropriate network adapter.
If increasing the value does not correct the problem, contact Microsoft Product Support Services. For more information about product support, see Help. Alternatively, see Product Support Services at https://www.microsoft.com/homepage/ms.htm.
Under the Resources area in the navigation pane, point to Support, and then click Support Home.
For more information about Windows Registry best practices, see Help.
Event ID: 14
Alert Severity: E
Windows Server 2003 Event Text: NLB Cluster %2 %1: Cluster network address %3 is invalid. Please check the NLB configuration and make sure that the cluster network address consists of six hexadecimal byte values separated by dashes. %4
Windows 2000 Server Event Text: %4 %1: cluster network address %2 is invalid. Please check %4 Setup page and make sure that it consists of six hexadecimal byte values separated by dashes. %3
Error Message Explanation: The cluster network MAC address is not in the following form xx-xx-xx-xx-xx-xx, where x is a hexadecimal value. Leading zeroes are optional.
User Action (Windows Server 2003): To change the MAC address to a valid form, open theProperties dialog box for this Network Load Balancing (NLB) cluster. If the Network address text box is available, NLB is set up for manual configuration of the network address and you should change the address to a correct MAC address.
If the Network address text box is unavailable (it is dimmed), then NLB is configured to calculate the MAC address automatically and there is a problem doing so. Contact Microsoft Product Support Services for assistance. For more information about product support, see Help. Alternatively, see Product Support Services at https://www.microsoft.com/homepage/ms.htm.
Under the Resources area in the navigation pane, point to Support, and then click Support Home.
User Action (Windows 2000 Server): To change the MAC address to a valid form, open the Properties dialog box for this Network Load Balancing (NLB) cluster. If the Network address text box is available, NLB is set up for manual configuration of the network address and you should change the address to a correct MAC address.
If the Network address text box is unavailable (it is dimmed), then NLB is configured to calculate the MAC address automatically and there is a problem doing so. Contact Microsoft Product Support Services for assistance. For more information about product support, see Help. Alternatively, see Product Support Services at https://www.microsoft.com/homepage/ms.htm.
Under the Resources area in the navigation pane, point to Support, and then click Support Home.
Event ID: 15
Alert Severity: W
Windows Server 2003 Event Text: NLB Cluster %2 %1: Dedicated IP address %3 is invalid. The driver will proceed assuming that there is no dedicated IP address. Please check the NLB configuration and make sure that the dedicated IP address consists of four decimal byte values separated by dots. %4
Windows 2000 Server Event Text: %4 %1: dedicated IP address %2 is invalid. Will proceed assuming that there is no dedicated IP address. Please check %4 Setup page and make sure that it consists of four decimal byte values separated by dots. %3
Error Message Explanation: The specified dedicated IP address is not valid. The cluster will continue to converge. However, you will not be able to use the dedicated IP address for such tasks as managing the host or for other non-cluster related communication.
User Action (Windows Server 2003): No user action is required. However, if you want to use a dedicated IP address, you must enter a valid address.
User Action (Windows 2000 Server): No user action is required. However, if you want to use a dedicated IP address, you must enter a valid address.
Event ID: 16
Alert Severity: E
Windows Server 2003 Event Text: NLB Cluster %2 %1: Cluster IP address %3 is invalid. Please check the NLB configuration and make sure that the cluster IP address consists of four decimal byte values separated by dots. %4
Windows 2000 Server Event Text: %4 %1: cluster IP address %2 is invalid. Please check %4 Setup page and make sure that it consists of four decimal byte values separated by dots. %3
Error Message Explanation: This event is logged when the cluster IP address in the registry is not valid because it was manually changed to an incorrect address.
User Action (Windows Server 2003): Use Network Load Balancing Manager to change the cluster IP address to a valid IP address. For more information, see Help and Support.
User Action (Windows 2000 Server): Use Network Load Balancing to change the cluster IP address to a valid IP address. For more information, see Help.
Event ID: 18
Alert Severity: W
Windows Server 2003 Event Text: NLB Cluster %2 %1: Duplicate cluster subnets detected. The network may have been inadvertently partitioned. %3 %4
Windows 2000 Server Event Text: %4 %1: duplicate cluster subnets detected. The network may have been inadvertently partitioned. %2 %3
Error Message Explanation: The hosts in this cluster formed two or more separate clusters. This is usually caused by network partitioning that prevents the Network Load Balancing (NLB) heartbeats of one or more hosts from reaching all of the other hosts in the cluster. This event is logged when the network problem is corrected and the hosts converge back into a single cluster.
User Action (Windows Server 2003): Investigate the cause of the network partitioning. No investigation of NLB is necessary.
User Action (Windows 2000 Server): Investigate the cause of the network partitioning. No investigation of NLB is necessary.
Event ID: 19
Alert Severity: W
Windows Server 2003 Event Text: NLB Cluster %2 %1: Could not allocate additional connection descriptors. Increase the %3 value under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WLBS\Parameters\{GUID} key in the registry. %4
Windows 2000 Server Event Text: %4 %1: could not allocate additional connection descriptors. Increase the %2 value under \SYSTEM\CurrentControlSet\Services\%4\Parameters key in the registry. %3
Error Message Explanation: Descriptors are used to track connections that are being load-balanced by Network Load Balancing (NLB). A fixed number of descriptors (controlled by a registry key value) are allocated when the NLB driver is loaded. This event is logged to warn you that the pool of descriptors has been exhausted. It might be necessary for NLB to reuse descriptors that are currently tracking existing active connections in order to track the state of new connections. This might have unexpected consequences and could result in legitimate connections being reset.
User Action (Windows Server 2003): Advanced users can increase the maximum number of descriptors that are allocated by changing the appropriate key in the registry. The registry key specified in the message is incorrect. Instead, you should increase the value of the following registry key: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\WLBS\Parameters
\Interface\{GUID}\MaxDescriptorAllocs.
The GUID is the globally unique identifier of the network adapter that is experiencing the problem. This is the network adapter that is bound to NLB. If NLB is, or has been, bound to multiple network adapters, you can find the correct adapter by looking at the value for the ClusterIPAddress key for each GUID entry in the registry.
It is recommended that you double the existing value of this registry key. After increasing the value, you must re-bind NLB to the adapter that was experiencing the problem (as identified by the GUID in the message). To do this, do one of the following:
Restart the host,
Disable and then re-enable the appropriate network adapter, or
Remove and then re-add NLB to the appropriate network adapter.
If increasing the value does not correct the problem, contact your product support person. For more information about product support, see Help and Support. Alternatively, see Product Support Services at https://www.microsoft.com/homepage/ms.htm.
Under the Resources area in the navigation pane, point to Support, and then click Support Home.
For more information about Windows Registry best practices, see Help and Support.
User Action (Windows 2000 Server): Advanced users can double the number of descriptors that are allocated by changing the specified key in the registry. After increasing the value, reload NLB. To do this, do one of the following:
Restart the host,
Disable and then re-enable the appropriate network adapter, or
Remove and then re-add NLB to the appropriate network adapter.
If increasing the value does not correct the problem, contact Microsoft Product Support Services. For more information about product support, see Help. Alternatively, see Product Support Services at https://www.microsoft.com/homepage/ms.htm.
Under the Resources area in the navigation pane, point to Support, and then click Support Home.
For more information about Windows Registry best practices, see Help.
Event ID: 20
Alert Severity: E
Windows Server 2003 Event Text: NLB Cluster %2 %1: Port rules with duplicate single host priority %3 detected on the network. Please check the NLB configuration on all hosts that belong to the cluster and make sure that they do not contain single host rules with duplicate priorities for the same port range. %4
Windows 2000 Server Event Text: %4 %1: port rules with duplicate single host priority %2 detected on the network. Please check %4 Setup dialog on all hosts that belong to the cluster and make sure that they do not contain single host rules with duplicate priorities for the same port range. %3
Error Message Explanation: When you configure a port rule as a single host, traffic to the port or ports governed by that port rule is handled exclusively by the host whose priority has the lowest numeric value. This event is logged when the local host's single host priority is identical to the single host priority of another host. The cluster will not converge until the problem is corrected.
User Action (Windows Server 2003): Using Network Load Balancing (NLB) Manager, edit the single host port rule on one of the hosts to give it a unique priority within the cluster. For more information about using NLB Manager to assign a unique priority to a host, see Help and Support.
User Action (Windows 2000 Server): Edit the single host port rule on one of the hosts to give it a unique priority within the cluster. For more information about using Network Load Balancing to assign a unique priority to a host, see Help.
Event ID: 21
Alert Severity: E
Windows Server 2003 Event Text: NLB Cluster %2 %1: Host %3 does not have the same number or type of port rules as this host. Please check the NLB configuration on all hosts that belong to the cluster and make sure that they all contain the same number and type of port rules. %4
Windows 2000 Server Event Text: %4 %1: host %2 does not have the same number or type of port rules as this host. Please check %4 Setup dialog on all machines that belong to the cluster and make sure that they all contain the same number and the same type of port rules. %3
Error Message Explanation: This event is logged when another host in the cluster either contains a different number of port rules from the local host, or its configured port rules conflict with the port rules of the local host. The cluster will not converge until the problem is corrected.
User Action (Windows Server 2003): Using Network Load Balancing (NLB) Manager, edit the port rules as appropriate on each host so that the port rules are consistent on all hosts in the cluster. For more information about editing port rules in NLB, see Help and Support.
User Action (Windows 2000 Server): Edit the port rules as appropriate on each host so that the port rules are consistent on all hosts in the cluster. For more information about editing port rules in Network Load Balancing, see Help.
Event ID: 23
Alert Severity: I
Windows Server 2003 Event Text: NLB Cluster %2 %1: Enabled traffic handling for rule containing port %3 %4
Windows 2000 Server Event Text: %4 %1: enabled traffic handling for rule containing port %2. %3
Error Message Explanation: This event is logged to inform you that, in response to a user-initiated action, this host will handle new load balanced traffic for the specified port rule.
User Action (Windows Server 2003): No user action is required.
User Action (Windows 2000 Server): No user action is required.
Event ID: 24
Alert Severity: I
Windows Server 2003 Event Text: NLB Cluster %2 %1: Disabled ALL traffic handling for rule containing port %3 %4
Windows 2000 Server Event Text: %4 %1: disabled ALL traffic handling for rule containing port %2. %3
Error Message Explanation: This event is logged to inform you that, in response to a user-initiated action, network traffic arriving over ports governed by the specified port rule will no longer be handled by this host.
User Action (Windows Server 2003): No user action is required.
User Action (Windows 2000 Server): No user action is required.
Event ID: 25
Alert Severity: W
Windows Server 2003 Event Text: NLB Cluster %2 %1: Port %3 not found in any of the valid port rules. %4
Windows 2000 Server Event Text: %4 %1: port %2 not found in any of the valid port rules. %3
Error Message Explanation: This event is logged when a user issues a command to control or query the state of a load-balanced port, but not applicable port rule is found. The command was ignored.
User Action (Windows Server 2003): No user action is required unless you expected this port to be governed by a port rule. In that case, you must configure a port rule to govern this port. For more information about configuring a port rule in Network Load Balancing, see Help and Support.
User Action (Windows 2000 Server): No user action is required unless you expected this port to be governed by a port rule. In that case, you must configure a port rule to govern this port. For more information about configuring a port rule in Network Load Balancing, see Help.
Event ID: 26
Alert Severity: W
Windows Server 2003 Event Text: NLB Cluster %2 %1: Port rules cannot be enabled/disabled while cluster operations are stopped. %3 %4
Windows 2000 Server Event Text: %4 %1: port rules cannot be enabled/disabled while cluster operations are stopped. %2 %3
Error Message Explanation: This event is logged when a disable or enable command is issued to a host which has been either stopped or suspended. The command was ignored.
User Action (Windows Server 2003): Before issuing a disable or enable command, you must start (or resume and start) Network Load Balancing on the host.
User Action (Windows 2000 Server): Before issuing a disable or enable command, you must start (or resume and start) Network Load Balancing on the host.
Event ID: 28
Alert Severity: I
Windows Server 2003 Event Text: NLB Cluster %2 %1: Host %3 converged with host(s) %4 as part of the cluster.
Windows 2000 Server Event Text: %4 %1: host %2 converged with host(s) %3 as part of the cluster.
Error Message Explanation: This event is logged to inform you that the specified host has joined the cluster.
User Action (Windows Server 2003): No user action is required.
User Action (Windows 2000 Server): No user action is required.
Event ID: 29
Alert Severity: I
Windows Server 2003 Event Text: NLB Cluster %2 %1: Host %3 converged as DEFAULT host with host(s) %4 as part of the cluster.
Windows 2000 Server Event Text: %4 %1: host %2 converged as DEFAULT host with host(s) %3 as part of the cluster.
Error Message Explanation: This event is logged to inform you that the specified host has joined the cluster. This host is now the default host and will handle all traffic that is not governed by any port rules.
User Action (Windows Server 2003): No user action is required. If you do not want this host to be the default host, reconfigure the host priority settings. For more information about reconfiguring host priorities in Network Load Balancing, see Help and Support.
User Action (Windows 2000 Server): No user action is required. If you do not want this host to be the default host, reconfigure the host priority settings. For more information about reconfiguring host priorities in Network Load Balancing, see Help.
Event ID: 30
Alert Severity: W
Windows Server 2003 Event Text: NLB Cluster %2 %1: Dedicated network mask %3 is invalid. The driver will ignore the dedicated IP address and network mask. Please check the NLB configuration and make sure that the dedicated network mask consists of four decimal byte values separated by dots. %4
Windows 2000 Server Event Text: %4 %1: dedicated network mask %2 is invalid. Will ignore dedicated IP address and network mask. Please check %4 Setup page and make sure that it consists of four decimal byte values separated by dots. %3
Error Message Explanation: This event is logged when the subnet mask entered for the dedicated IP address is not valid. The cluster will continue to operate. However, you cannot use the dedicated IP address, so you cannot use it to manage the host or for other non-cluster-related communication.
User Action (Windows Server 2003): No user action is required. The cluster will continue to operate. However, if you want to use the dedicated IP address, enter a valid subnet mask. For more information about entering a subnet mask in Network Load Balancing, see Help and Support.
User Action (Windows 2000 Server): No user action is required. The cluster will continue to operate. However, if you want to use the dedicated IP address, enter a valid subnet mask. For more information about entering a subnet mask in Network Load Balancing, see Help.
Event ID: 31
Alert Severity: E
Windows Server 2003 Event Text: NLB Cluster %2 %1: Cluster network mask %3 is invalid. Please check the NLB configuration and make sure that the cluster network mask consists of four decimal byte values separated by dots. %4
Windows 2000 Server Event Text: %4 %1: cluster network mask %2 is invalid. Please check %4 Setup page and make sure that it consists of four decimal byte values separated by dots. %3
Error Message Explanation: This event is logged when the subnet mask entered for the cluster IP address is not valid.
User Action (Windows Server 2003): Correct the subnet mask for the cluster IP address. For more information about correcting the subnet mask in Network Load Balancing, see Help and Support.
User Action (Windows 2000 Server): Correct the subnet mask for the cluster IP address. For more information about correcting the subnet mask in Network Load Balancing, see Help.
Event ID: 32
Alert Severity: W
Windows Server 2003 Event Text: NLB Cluster %2 %1: Both the dedicated IP address and network mask must be specified. The driver will ignore the dedicated IP address and network mask. %3 %4
Windows 2000 Server Event Text: %4 %1: both dedicated IP address and network mask have to be entered. Will ignore dedicated IP address and network mask. %2 %3
Error Message Explanation: This event is logged when either the dedicated IP address or its subnet mask was not entered. The cluster will continue to operate. However, you cannot use the dedicated IP address, so you cannot use it to manage the host or for other non-cluster-related communication.
User Action (Windows Server 2003): No user action is required. The cluster will continue to operate. However, if you want to use the dedicated IP address, enter a valid dedicated IP address and subnet mask. For more information about entering a dedicated IP address and subnet mask in Network Load Balancing, see Help and Support.
User Action (Windows 2000 Server): No user action is required. The cluster will continue to operate. However, if you want to use the dedicated IP address, enter a valid dedicated IP address and subnet mask. For more information about entering a dedicated IP address and subnet mask in Network Load Balancing, see Help.
Event ID: 33
Alert Severity: W
Windows Server 2003 Event Text: NLB Cluster %2 %1: Remote control request rejected from %3 due to an incorrect password. %4
Windows 2000 Server Event Text: %4 %1: remote control request rejected from host %2 due to incorrect password. %3
Error Message Explanation: This event is logged when remote control is enabled on this server and a remote control request was received for the cluster. However, the remote control password received is not correct. A legitimate user might have accidentally entered the wrong password, or someone else might have tried to guess the password.
User Action (Windows Server 2003): The source IP address of the remote control request is provided in the message. Use this information to determine the computer from which the remote control command was issued. This might help identify who issued the remote control command.
Warning: The Network Load Balancing remote control option presents many security risks, including the possibility of data tampering, denial of service, and information disclosure. We strongly recommend that you do not enable remote control, and that instead you use NLB Manager or other remote management tools such as Windows Management Instrumentation (WMI).
User Action (Windows 2000 Server): The source IP address of the remote control request is provided in the message. Use this information to determine the computer from which the remote control command was issued. This might help identify who issued the remote control command.
Warning: The Network Load Balancing remote control option presents many security risks, including the possibility of data tampering, denial of service, and information disclosure. We strongly recommend that you do not enable remote control, and that instead you use NLB Manager or other remote management tools such as Windows Management Instrumentation (WMI).
Event ID: 34
Alert Severity: E
Windows Server 2003 Event Text: NLB Cluster %2 %1: Error querying parameters from the registry key \HLKM\SYSTEM\CurrentControlSet\Services\WLBS\Parameters\%3. Please fix the NLB configuration and run wlbs reload followed by wlbs start. %4
Windows 2000 Server Event Text: %4 %1: error querying parameters from the registry key %2. Please run %4 setup dialog to fix the problem and run %4 reload followed by %4 start. %3
Error Message Explanation: This event is logged when there is an error processing the Network Load Balancing settings from the registry. For example, the registry key could not be opened, or a value that is not valid was read from one or more registry parameters. The most likely cause of this error is manual configuration of the registry instead of making configuration changes through the NLB properties dialog box.
User Action (Windows Server 2003): The registry hive specified in the message is incorrect. The correct hive is: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\WLBS\Parameters\Interface\{GUID}. The GUID identified in the message is the correct GUID. The GUID reference is the globally unique identifier of the network adapter that is experiencing the problem.
Advanced users should examine the registry keys in this hive to determine which registry parameter caused the event. To do this, consider comparing the registry entries of a host in the cluster that is working correctly to the registry entries of the host that is reporting the error. Also examine the event log for related events that might indicate more specific problems with the registry.
For more information about Windows Registry best practices, see Help and Support.
User Action (Windows 2000 Server): Refer to the message to determine the registry hive in which the error occurred. Advanced users should examine the registry keys in that hive to determine which registry parameter caused the event. To do this, consider comparing the registry entries of a host in the cluster that is working correctly to the registry entries of the host that is reporting the error. Also examine the event log for related events that might indicate more specific problems with the registry.
For more information about NLB registry settings, see the Windows 2000 Server Resource Kit. For more information about Windows Registry best practices, see Help.
Event ID: 35
Alert Severity: E
Windows Server 2003 Event Text: NLB Cluster %2 %1: Cluster mode cannot be enabled due to parameter errors. All traffic will be passed through to TCP/IP. Restart cluster operations after fixing the problem by running wlbs reload followed by wlbs start. %3 %4
Windows 2000 Server Event Text: %4 %1: cluster mode cannot be enabled due to parameter errors. All traffic will be passed to TCP/IP. Restart cluster operations after fixing the problem by running %4 reload followed by %4 start. %2 %3
Error Message Explanation: This event is probably logged because of incorrectly configured settings that are being read from the registry; in particular, IP addresses, IP subnet masks, or MAC addresses. Until this problem is corrected, this host will remain stopped and will not join the cluster.
User Action (Windows Server 2003): Look for additional Network Load Balancing (NLB) events that indicate errors reading from the registry or other configuration problems. You can also use NLB Manager to diagnose configuration problems. After you determine the specific error, correct the problem, and then run nlb reload' followed by 'nlb start'. If you cannot determine the specific error, contact your product support person.
For more information about product support, see Help and Support. Alternatively, see Product Support Services at https://www.microsoft.com/homepage/ms.htm. Under the Resources area in the navigation pane, point to Support, and then click Support Home.
User Action (Windows 2000 Server): Look for additional Network Load Balancing events that indicate errors reading from the registry or other configuration problems. After you determine the specific error, correct the problem, and then run wlbs reload' followed by wlbs start'. If you cannot determine the specific error, contact Microsoft Product Support Services. For more information about product support, see Help. Alternatively, see Product Support Services at https://www.microsoft.com/homepage/ms.htm. Under the Resources area in the navigation pane, point to Support, and then click Support Home.
Event ID: 36
Alert Severity: I
Windows Server 2003 Event Text: NLB Cluster %2 %1: Registry parameters successfully reloaded. %3 %4
Windows 2000 Server Event Text: %4 %1: registry parameters successfully reloaded. %2 %3
Error Message Explanation: This event is logged to inform you that the registry parameters have been reloaded successfully.
User Action (Windows Server 2003): No user action is required.
User Action (Windows 2000 Server): No user action is required.
Event ID: 37
Alert Severity: W
Windows Server 2003 Event Text: NLB Cluster %2 %1: Version mismatch between the driver and control programs. Please make sure that you are running the same version of all NLB components. %3 %4
Windows 2000 Server Event Text: %4 %1: version mismatch between the driver and control programs. Please make sure that you are running the same version. %2 %3
Error Message Explanation: This event is logged when incompatible Network Load Balancing binaries are installed, for example, if a Windows 2000 version of wlbs.exe is installed with a version of wlbs.sys created for a member of the Windows Server 2003 family of operating systems.
User Action (Windows Server 2003): Replace the conflicting binary.
User Action (Windows 2000 Server): Replace the conflicting binary.
Event ID: 38
Alert Severity: I
Windows Server 2003 Event Text: NLB Cluster %2 %1: Adjusted traffic handling for rule containing port %3. %4
Windows 2000 Server Event Text: %4 %1: adjusted traffic handling for rule containing port %2. %3
Error Message Explanation: This event is logged to inform you that, in response to a user-initiated action, the load weight of a port rule has changed.
User Action (Windows Server 2003): No user action is required.
User Action (Windows 2000 Server): No user action is required.
Event ID: 39
Alert Severity: I
Windows Server 2003 Event Text: NLB Cluster %2 %1: Disabled NEW traffic handling for rule containing port %3. %4
Windows 2000 Server Event Text: %4 %1: disabled NEW traffic handling for rule containing port %2. %3
Error Message Explanation: This event is logged to inform you that, in response to a user-initiated action, new network traffic is disabled for this specific port rule.
User Action (Windows Server 2003): No user action is required.
User Action (Windows 2000 Server): No user action is required.
Event ID: 40
Alert Severity: I
Windows Server 2003 Event Text: NLB Cluster %2 %1: Adjusted traffic handling for all port rules. %3 %4
Windows 2000 Server Event Text: %4 %1: adjusted traffic handling for all port rules. %2 %3
Error Message Explanation: This event is logged to inform you that, in response to a user-initiated action, the load weight of all port rules has changed.
User Action (Windows Server 2003): No user action is required.
User Action (Windows 2000 Server): No user action is required.
Event ID: 41
Alert Severity: I
Windows Server 2003 Event Text: NLB Cluster %2 %1: Disabled NEW traffic handling for all port rules. %3 %4
Windows 2000 Server Event Text: %4 %1: disabled NEW traffic handling for all port rules. %2 %3
Error Message Explanation: This event is logged to inform you that, in response to a user-initiated action, new network traffic is disabled for all port rules.
User Action (Windows Server 2003): No user action is required.
User Action (Windows 2000 Server): No user action is required.
Event ID: 41
Alert Severity: I
Windows Server 2003 Event Text: NLB Cluster %2 %1: Disabled NEW traffic handling for all port rules. %3 %4
Windows 2000 Server Event Text: %4 %1: disabled NEW traffic handling for all port rules. %2 %3
Error Message Explanation: This event is logged to inform you that, in response to a user-initiated action, new network traffic is disabled for all port rules.
User Action (Windows Server 2003): No user action is required.
User Action (Windows 2000 Server): No user action is required.
Event ID: 42
Alert Severity: I
Windows Server 2003 Event Text: NLB Cluster %2 %1: Enabled traffic handling for all port rules. %3 %4
Windows 2000 Server Event Text: %4 %1: enabled traffic handling for all port rules. %2 %3
Error Message Explanation: This event is logged to inform you that, in response to a user-initiated action, this host will handle new load-balanced traffic for all port rules.
User Action (Windows Server 2003): No user action is required.
User Action (Windows 2000 Server): No user action is required.
Event ID: 43
Alert Severity: I
Windows Server 2003 Event Text: NLB Cluster %2 %1: Disabled ALL traffic handling for all port rules. %3 %4
Windows 2000 Server Event Text: %4 %1: disabled ALL traffic handling for all port rules. %2 %3
Error Message Explanation: This event is logged to inform you that, in response to a user-initiated action, network traffic arriving over ports governed by any port rule will no longer be handled by this host.
User Action (Windows Server 2003): No user action is required.
User Action (Windows 2000 Server): No user action is required.
Event ID: 43
Alert Severity: I
Windows Server 2003 Event Text: NLB Cluster %2 %1: Disabled ALL traffic handling for all port rules. %3 %4
Windows 2000 Server Event Text: %4 %1: disabled ALL traffic handling for all port rules. %2 %3
Error Message Explanation: This event is logged to inform you that, in response to a user-initiated action, network traffic arriving over ports governed by any port rule will no longer be handled by this host.
User Action (Windows Server 2003): No user action is required.
User Action (Windows 2000 Server): No user action is required.
Event ID: 44
Alert Severity: I
Windows Server 2003 Event Text: NLB Cluster %2 %1: Connection draining started. %3 %4
Windows 2000 Server Event Text: %4 %1: connection draining started. %2 %3
Error Message Explanation: This event is logged to inform you that, in response to a user-initiated action, this host will stop accepting new network traffic. When there are no more active connections, this host will stop its cluster operations.
User Action (Windows Server 2003): No user action is required. For more information about the drain command, see Network Load Balancing in Help and Support.
User Action (Windows 2000 Server): No user action is required. For more information about the drain command, see Network Load Balancing in Help.
Event ID: 45
Alert Severity: I
Windows Server 2003 Event Text: NLB Cluster %2 %1: Connection draining interrupted. %3 %4
Windows 2000 Server Event Text: %4 %1: connection draining interrupted. %2 %3
Error Message Explanation: This event is logged to inform you that the host was draining when a stop or suspend command was issued by a user.
User Action (Windows Server 2003): No user action is required. For more information about the drain command, see Network Load Balancing in Help and Support.
User Action (Windows 2000 Server): No user action is required. For more information about the drain command, see Network Load Balancing in Help.
Event ID: 46
Alert Severity: I
Windows Server 2003 Event Text: NLB Cluster %2 %1: %3 remote control request received from %4.
Windows 2000 Server Event Text: %4 %1: %2 remote control request received from host %3.
Error Message Explanation: This event is logged when the cluster has received and is processing a remote control command.
User Action (Windows Server 2003): Verify that you know who is issuing the remote control commands and that this person is authorized to do so. The source IP address of the remote control request is provided in the message. Use this to determine the computer from which the remote control command was issued. This might help identify the person who issued the remote control command.
Warning: The Network Load Balancing (NLB) remote control option presents many security risks, including the possibility of data tampering, denial of service, and information disclosure. It is strongly recommended that you do not enable remote control, and that you instead use NLB Manager or other remote management tools such as Windows Management Instrumentation (WMI).
User Action (Windows 2000 Server): Verify that you know who is issuing the remote control commands and that this person is authorized to do so. The source IP address of the remote control request is provided in the message. Use this to determine the computer from which the remote control command was issued. This might help identify the person who issued the remote control command.
Warning: The Network Load Balancing (NLB) remote control option presents many security risks, including the possibility of data tampering, denial of service, and information disclosure. It is strongly recommended that you do not enable remote control, and that you instead use NLB Manager or other remote management tools such as Windows Management Instrumentation (WMI).
Event ID: 47
Alert Severity: I
Windows Server 2003 Event Text: NLB Cluster %2 %1: Cluster mode control resumed. %3 %4
Windows 2000 Server Event Text: %4 %1: cluster mode control resumed. %2 %3
Error Message Explanation: This event is logged to inform you that, in response to a user-initiated action, cluster operations have resumed.
User Action (Windows Server 2003): No user action is required. For more information about the resume command, see Network Load Balancing in Help and Support.
User Action (Windows 2000 Server): No user action is required. For more information about the resume command, see Network Load Balancing in Help.
Event ID: 48
Alert Severity: I
Windows Server 2003 Event Text: NLB Cluster %2 %1: Cluster mode control suspended. %3 %4
Windows 2000 Server Event Text: %4 %1: cluster mode control suspended. %2 %3
Error Message Explanation: This event is logged to inform you that, in response to a user-initiated action, cluster operations have been suspended.
User Action (Windows Server 2003): No user action is required. For more information about the suspend command, see Network Load Balancing in Help and Support.
User Action (Windows 2000 Server): No user action is required. For more information about the suspend command, see Network Load Balancing in Help.
Event ID: 49
Alert Severity: E
Windows Server 2003 Event Text: This error cannot occur on Windows Server 2003 systems.
Windows 2000 Server Event Text: %4 %1: Network Load Balancing can only be installed on systems running Windows 2000 Advanced Server or Datacenter Server. %2 %3
Error Message Explanation: To use Network Load Balancing, you must install Windows 2000 Advanced Server or Windows 2000 Datacenter Server on this computer. NLB is also available on all members of the Windows Server 2003 family.
User Action (Windows Server 2003): This error cannot occur on Windows Server 2003 systems.
User Action (Windows 2000 Server): To use NLB, install Windows 2000 Advanced Server or Datacenter Server. NLB is also available on all members of the Windows Server 2003 family.
Event ID: 50
Alert Severity: E
Windows Server 2003 Event Text: NLB Cluster %2 %1: Cannot add cluster MAC address. The maximum number of multicast MAC addresses are already assigned to the NIC. %3 %4
Windows 2000 Server Event Text: %4 %1: cannot add cluster MAC address. The maximum number of multicast MAC addresses are already assigned to the NIC. %2 %3
Error Message Explanation: The network adapter has the maximum number of multicast MAC addresses assigned to it already. Other programs might have added multicast addresses with the result that Network Load Balancing cannot add the MAC addresses needed to operate an NLB cluster in multicast mode.
User Action (Windows Server 2003): Perform one or more of the following to correct the problem.
Use a network adapter that allows an increased number of multicast MAC addresses to be configured.
Operate the cluster in unicast mode.
For more information about unicast and multicast mode, see Network Load Balancing in Help and Support.
User Action (Windows 2000 Server): Perform one or more of the following to correct the problem.
Use a network adapter that allows an increased number of multicast MAC addresses to be configured.
Operate the cluster in unicast mode.
For more information about unicast and multicast mode, see Network Load Balancing in Help.