|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Sentry-go®
3Ds (UK) Limited
© 2000-2008 |
|
|
|
|
|
|
The Sentry-go Plus! TCP/IP monitor allows you to periodically verify that
access to well-known TCP/IP listen ports can be established on the local server.
In addition, data can be sent to and analysed from an established connection,
thus ensuring the correct protocol is being performed. Well known ports include
Web (HTTP & HTTPS), SMTP, POP3, IMAP4, DNS & WINS etc., although any port,
including custom ports can be monitored. If a connection cannot be established
or the data returned does not match expected results, automatic action can be
taken and/or alerts raised.
|
|
Facts & Features |
In order to function, web-based servers and services listen for inbound requests
via TCP/IP ports. If the service is not listening on it's standard (or so-called
"well known") port, external access to that service will be unavailable.
|
|
For example, if IIS is not listening on port 80, standard browser requests to it
will result in an error, while SMTP e-mail servers normally listen on port 25 etc.
Using the Sentry-go Plus! Port Monitor, you can not only verify that the underlying service is
available, but also check to see whether the service is working correctly and
waiting for inbound requests by sending an initial request and/or waiting for it's
response on the appropriate port.
If it isn't, the underlying system can either be restarted, or the webmaster or System Administrator(s) notified as
required.
|
|
|
|
|
|
TCP/IP Port Monitoring 
