Windows 7
- NLB and Winsock error codes are returned in this property.The Values and ValueMap qualifiers map the NLB defined constants, ...
- NLB cluster %2]: A load distribution error was detected during convergence. This might result in client traffic not being ...
- NLB cluster %2]: A port rule operation on port %3 was issued but there is no port rule that contains this port. Please confirm ...
- NLB cluster %2]: A port rule operation was issued while the host was in the stopped state. Such operations can only be performed ...
- NLB cluster %2]: A SYN attack has been detected. During the attack, some connections might fail. If this attack recurs frequently, ...
- NLB cluster %2]: An inconsistent teaming configuration was detected for bi-directional affinity (BDA) on host %5. BDA configuration ...
- NLB cluster %2]: An unsupported legacy host %3 was discovered on the network. The OS version on this host is no longer supported ...
- NLB cluster %2]: Consistent bi-directional affinity (BDA) teaming configuration detected again. The team in which this cluster ...
- NLB cluster %2]: Duplicate dedicated IP (DIP) address %3 was detected on the network. Please check that each of the cluster ...
- NLB cluster %2]: Host %5 converged with host(s)%3. It is now an active member of the NLB cluster and will start load balancing ...
- NLB cluster %2]: Host %5 converged with host(s)%3. It is now an active member of the NLB cluster and will start load balancing ...
- NLB cluster %2]: Host %5 converged with legacy host(s)%3. This is expected during rolling upgrades. Until all hosts are upgraded ...
- NLB cluster %2]: Invalid bi-directional affinity (BDA) team ID detected. Team IDs must be a GUID of the form {xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}. ...
- NLB cluster %2]: Invalid bi-directional affinity (BDA) teaming port rules detected. Each member of a BDA team may have no ...
- NLB cluster %2]: Last known NLB host state was not found in the registry. The state of this host will revert to the user-specified ...
- NLB cluster %2]: NLB can't track TCP connections because it was unable to open the TCP connection callback object. Although ...
- NLB cluster %2]: NLB detected a duplicate host priority %5 that is shared between cluster hosts. Each host in the NLB cluster ...
- NLB cluster %2]: NLB detected an unequal number of dedicated IP (DIP) addresses and network masks. For all DIP's listed for ...
- NLB cluster %2]: NLB detected an unequal number of virtual IP (VIP) addresses and network masks. For all VIP's listed for ...
- NLB cluster %2]: NLB detected duplicate cluster subnets. This may be due to network partitioning, which prevents NLB heartbeats ...
- NLB cluster %2]: NLB failed to add a multicast MAC address to the network adapter it is bound to. This happened because the ...
- NLB cluster %2]: NLB failed to add all the dedicated IP (DIP) addresses to this host. This happened because the maximum number ...
- NLB cluster %2]: NLB failed to converge due to inconsistencies in the port rules between this host and cluster host %5. This ...
- NLB cluster %2]: NLB failed to converge due to port rules with a duplicate single host priority %5 in the cluster. Each single ...
- NLB cluster %2]: NLB failed to initialize bi-directional affinity (BDA) teaming on adapter '%3'. The BDA team in which this ...
- NLB cluster %2]: NLB failed to query parameters from the registry key HKLM\SYSTEM\CurrentControlSet\Services\WLBS\Parameters\Interface\%3. ...
- NLB cluster %2]: NLB failed to register as a WMI provider. As a result, it will not be able to notify applications that are ...
- NLB cluster %2]: NLB failed to update the adapter multicast list. The cluster will converge and operate normally but some ...
- NLB cluster %2]: NLB failed to update the NLB host state in the registry. This will affect the ability of NLB to persist ...
- NLB cluster %2]: NLB failed to verify its parameters. This might be due to an improper configuration. Please use Network ...
- NLB cluster %2]: NLB is initiating convergence on host %5 because host %6 has a configuration that conflicts with other hosts. ...
- NLB cluster %2]: NLB is initiating convergence on host %5 because host %6 is configured with a conflicting number of port ...
- NLB cluster %2]: NLB is initiating convergence on host %5 to synchronize the Extended Affinity configuration between all ...
- NLB cluster %2]: NLB received a heartbeat from a host with an invalid ID %5. Please check the NLB configuration of all hosts ...
- NLB cluster %2]: NLB will not attach to adapter '%3' because it does not support dynamic changing of its MAC address. Replace ...
- NLB cluster %2]: The bi-directional affinity (BDA) team in which this cluster participates has no designated master. The ...
- NLB cluster %2]: The bi-directional affinity (BDA) team which this cluster has attempted to join already has a designated ...
- NLB cluster %2]: The dedicated IP (DIP) address %3 is invalid. The cluster will converge and operate normally without this ...
- NLB cluster %2]: The dedicated network mask %3 is invalid. The cluster will converge and operate normally without this dedicated ...
- NLB cluster %2]: The maximum number of actively serviced connections that could be tracked by NLB is reached. Although NLB ...
- NLB cluster %2]: The maximum number of actively serviced Extended Affinity connections that could be tracked by NLB is reached. ...
- NLB cluster %2]: The NLB cluster IGMP multicast IP address %3 is invalid. Please check the NLB configuration and make sure ...
- NLB cluster %2]: The NLB driver could not allocate enough memory resources to perform driver operations. Close all programs ...
- NLB cluster %2]: The NLB driver failed to attach a network adapter due to error %5. As a result, this host will not be an ...
- NLB cluster %2]: The NLB driver failed to attach to adapter '%3' due to error %5. As a result, this host will not be an active ...
- NLB cluster %2]: The NLB driver failed to bind to the adapter because the maximum transfer unit (MTU) reported by the adapter ...
- NLB cluster %2]: The NLB driver failed to bind to the adapter because the medium type is unsupported. Please confirm that ...
- NLB cluster %2]: The NLB driver failed to initialize because the cluster IP address %3 is invalid. Please check that the ...
- NLB cluster %2]: The NLB driver failed to initialize because the cluster network address %3 is invalid. Please check that ...
- NLB cluster %2]: The NLB driver failed to initialize because the cluster network mask %3 is invalid. Please check that the ...
- NLB cluster %2]: The NLB driver failed to initialize because the number of port rules must be between 0 and %5. It is currently ...
- NLB cluster %2]: The NLB driver failed to open the SYN attack callback object. A SYN attack is a type of denial of service ...
- NLB cluster %2]: The NLB driver failed to open the timer starvation callback object. Although it will continue to operate, ...
- NLB cluster %2]: The NLB driver failed to register for notifications with the IPv4 NSI provider. NLB will continue to operate ...
- NLB cluster %2]: The NLB driver failed to register for notifications with the IPv4 NSI provider. NLB will continue to operate ...
- NLB cluster %2]: The NLB driver failed to register for notifications with the IPv6 NSI provider. NLB will continue to operate ...
- NLB cluster %2]: The NLB driver failed to register the device object. The cluster will converge and operate normally but ...
- NLB cluster %2]: The NLB driver failed to register with the Network Driver Interface Specification (NDIS) with error code ...
- NLB cluster %2]: The NLB driver failed to register/unregister the hook interface. The cluster will converge and operate normally ...
- NLB cluster %2]: The NLB driver has detected an inconsistency in the Extended Affinity configuration between cluster host ...
- NLB cluster %2]: The NLB driver has detected an inconsistency in the Extended Affinity configuration on cluster host %5. ...
- NLB cluster %2]: The NLB driver has detected one or more %3 sessions corresponding to a port rule that is improperly configured. ...
- NLB cluster %2]: The NLB host state was successfully updated in the registry. Current state will persist after the system ...
- NLB cluster %2]: The virtual IP (VIP) address %3 is invalid. The cluster will converge and operate normally without this ...
- NLB cluster %2]: The virtual IP (VIP) address in a port rule is invalid. The cluster will converge and operate normally but ...
- NLB cluster %2]: The virtual network mask %3 is invalid. The cluster will converge and operate normally without this virtual ...
- NLB cluster %2]: This cluster has joined a bi-directional affinity (BDA) team as the designated master. If the rest of the ...
- NLB cluster %2]: This cluster has left a bi-directional affinity (BDA) team in which it was the designated master. If other ...
- NLB cluster %2]: This host has drained all connections for all port rules. It will not handle any new load balanced traffic ...
- NLB cluster %2]: This host has drained all connections for port rule containing port %3. It will not handle any new load ...
- NLB cluster %2]: This host has resumed cluster operations. Once it is started, this host will be an active member of the ...
- NLB cluster %2]: This host has started draining all connections for all port rules. It will not handle any new load balanced ...
- NLB cluster %2]: This host has stopped draining all connections. This may be due to a stop/suspend operation on the host. ...
- NLB cluster %2]: This host has suspended cluster operations. Until it is resumed, this host will not be an active member ...
- NLB cluster %2]: This host is an active member of the NLB cluster. The host priority (unique host identifier) is %5. It will ...