Partager via

Immediately stop handling all Network Load Balancing cluster traffic

  • Article

Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2

To immediately stop handling all Network Load Balancing cluster traffic

  • Using the Windows interface

  • Using a command line

Using the Windows interface

  1. Open Network Load Balancing Manager.

  2. If Network Load Balancing Manager does not already list the cluster, connect to the cluster.

  3. If you want to stop cluster operations on all cluster hosts, right-click the cluster, and then point to Control Hosts.

    Or, if you want to stop the cluster service on only a particular host, right-click the host, and then point to Control Host.

  4. Click Stop

Cluster operations are immediately stopped and all existing connections are immediately closed.

Important

  • To start Network Load Balancing Manager, open a Command prompt. From the command window, type NLBMgr, and then press ENTER.

Notes

  • When using Network Load Balancing Manager, you must be a member of the Administrators group on the host that you are configuring, or you must have been delegated the appropriate authority. As a security best practice, consider using Run as to perform this procedure. If you are configuring a cluster or host by running Network Load Balancing Manager from a computer that is not part of the cluster, you do not need to be a member of the Administrators group on that computer. For more information, see Default local groups, Default groups, and Using Run as.

  • To start Network Load Balancing Manager, open a Command prompt. From the command window, type NLBMgr, and then press ENTER.

  • When you use the stop command, either through Network Load Balancing Manager or the command prompt, any client connections already in progress are interrupted. To avoid interrupting active connections, consider using the drainstop cluster-control command, which allows the host to continue servicing active connections, but disables all new traffic to that host. For more information, see "Disable new traffic handling and stop Network Load Balancing" in Related Topics.

  • For information on how to restart cluster operations, see "To start Network Load Balancing" in Related Topics.

  • The stop command differs from the suspend command in that suspend stops Network Load Balancing on the host and also suspends all Network Load Balancing cluster-control commands on the host, except for the resume and query commands. Stop only stops Network Load Balancing on the host, but does not affect the other Network Load Balancing cluster-control commands. For more information on the suspend command, see "To suspend Network Load Balancing".

Using a command line

  1. Open Command Prompt.

  2. Type:

    nlb.exe stop

    Cluster operations are immediately stopped on the local cluster host and all existing connections are immediately closed.

    Or, if you want to stop cluster operations on all cluster hosts, type:

    nlb.exe stopcluster IP address | cluster name

Notes

  • To run nlb.exe from a remote computer, you must enable remote control on the host that is running Network Load Balancing. The Network Load Balancing remote control option presents many security risks, including the possibility of data tampering, denial of service and information disclosure. Only use remote control on a secure computer within your firewall. Because of the many security risks remote control presents, it is recommended that you do not enable the remote control feature. Instead, use other remote management tools such as Network Load Balancing Manager or Windows Management Instrumentation (WMI).

  • To open a command prompt, click Start, point to All programs, point to Accessories, and then click Command prompt.

  • To run nlb.exe from a remote computer, you must enable remote control on the host that is running Network Load Balancing. The Network Load Balancing remote control option presents many security risks, including the possibility of data tampering, denial of service and information disclosure. Only use remote control on a secure computer within your firewall. Because of the many security risks remote control presents, it is recommended that you do not enable the remote control feature. Instead, use other remote management tools such as Network Load Balancing Manager or Windows Management Instrumentation (WMI).

  • When you use the stop command, either through Network Load Balancing Manager or the command prompt, any client connections already in progress are interrupted. To avoid interrupting active connections, consider using the drainstop cluster-control command, which allows the host to continue servicing active connections, but disables all new traffic to that host. For more information, see "Disable new traffic handling and stop Network Load Balancing" in Related Topics.

  • For information on how to restart cluster operations, see "To start Network Load Balancing" in Related Topics.

  • The stop command differs from the suspend command in that suspend stops Network Load Balancing on the host and also suspends all Network Load Balancing cluster-control commands on the host, except for the resume and query commands. Stop only stops Network Load Balancing on the host, but does not affect the other Network Load Balancing cluster-control commands. For more information on the suspend command, see "To suspend Network Load Balancing" in Related Topics.

Information about functional differences

  • Your server might function differently based on the version and edition of the operating system that is installed, your account permissions, and your menu settings. For more information, see Viewing Help on the Web.

See Also

Concepts

Suspend Network Load Balancing
Nlb
Disable new traffic handling for specific ports and stop Network Load Balancing
Restart handling Network Load Balancing cluster traffic
Nlbmgr