Third-Party Monitoring Programs Monitor Applications and Ports

Article translations Article translations
Article ID: 233178 - View products that this article applies to.
This article was previously published under Q233178
This article has been archived. It is offered "as is" and will no longer be updated.
Expand all | Collapse all


This article discusses some third-party monitoring tools you can use to monitor applications and ports.


Windows NT Load Balancing Service (WLBS) monitors cluster integrity using the periodic exchange of heartbeats between cluster members. Heartbeat exchange ensures the server is available on the network, but does not include any checking at the port or application level.

You can use third-party monitoring tools to control cluster membership based on content availability. Some tools allow a command to be executed after detecting an application failure at a server. For example, if an application being load balanced on a server fails, the monitoring tool could execute the following command
wlbs stop IPaddress:HostID
where IPaddress is the IP address for that cluster and HostID is the host ID or dedicated IP address of that server.

For information about the command line syntax, type wlbs at an MS-DOS prompt.

Some examples of third-party tools that monitor cluster membership are listed in the following table.

Collapse this tableExpand this table
ProgramWeb Address
Freshwater Software SiteScope
NetIQ AppManager
Ipswitch WhatsUp Gold


Article ID: 233178 - Last Review: February 28, 2014 - Revision: 3.3
  • Microsoft Windows NT Server 4.0 Enterprise Edition
  • Microsoft Windows NT Load Balancing Service
kbnosurvey kbarchive kbinfo kbnetwork KB233178

Give Feedback


Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from