|
With the Sentry-go Quick IIS Web Server Monitor you can easily check to that
web-based services are connected and listening on the appropriate TCP/IP
ports. If they're not, although the service itself may be available,
connectivity may be being affected from external customers as well as other systems.
TCP/IP Port Listen
Checks for Web-based Services
You can monitor any local port to ensure connectivity is available.
Although this check includes basic connectivity, you can also send a text
string and optionally wait for the server to respond. Predefined checks
include ...
|
|
HTTP (web server requests)
|
|
|
HTTPS
(secure web server requests)
|
|
|
FTP
|
|
|
Telnet
|
Why Monitor Your TCP/IP
Ports ?
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.
With the Sentry-go Quick IIS
Web Server Monitor, you can not only verify that the underlying service is
available, but also check to see that the service is working correctly and
waiting for inbound requests on the appropriate port. If it isn't, the
service can either be restarted, or the webmaster/System Administrator(s)
notified as required.
|
Monitoring TCP/IP Listen
Ports
