The purpose of ipMonitor is to probe computers, devices, and resources using the appropriate protocol required to determine that the probed entity is accessible via the network. Since ipMonitor must be installed on Microsoft NT, networking transactions used to probe entities are handled by NT's networking layers. Even though NT takes care of low level networking you might need to know exactly what activities on your network result because of ipMonitor.
The following table outlines ipMonitor network activity.
| ipMonitor Function |
Comments |
| Configuration |
Configuration falls into two categories.
- ipM security and service parameters are set using the ipMonitor Configuration program. The ipM service must be stopped. IP address, Port, public access parameters are set from this interface.
- ipM monitoring configuration must be done from a Web Browser. The HTTP protocol is used on port 8080 (default unless changed). TCP is the parent protocol used to send and receive HTTP packets.
|
| Monitor Status Viewing |
A Web Browser is used to display Monitor Status. HTTP protocol is used on port 8080 (default unless changed). TCP is the parent protocol used to send and receive HTTP packets. |
| Email Alert |
SMTP is used to send email alerts. Alerts are forwarded to your mail server or secondary mail server if possible. If not possible email is sent directly to the recipient. TCP is the parent protocol used to send and receive SMTP packets. |
| NT Network Broadcast Alert |
NetBEUI is used to broadcast NT network messages. |
| NT System Log Alert |
NetBEUI is used to append NT Event Logs. |
| Text Log Alert |
SMB is the underlying protocol. UNC paths are used to write to file(s) on Network computers. Local paths are used to write to file(s) on the local computer. NT permissions apply to each transaction via the SMB protocol. |
The following table outlines how Monitors configured within ipMonitor use network protocols supported by NT to probe computers, devices, and resources on the network.
| Parent Protocol |
Protocol |
Comments |
| TCP |
HTTP, LDAP, POP3, NNTP, Notes Transport, SMTP, FTP, TELNET, GOPHER, IRC, FINGER, DNS, WHOIS, RHWOIS |
Without TCP/IP ipMonitor is unable to operate. TCP/IP is required as the underlying protocol used by ipMonitor to probe Internet software and services. Probes take place every <x> number of seconds using the configuration parameters provided at the time the Monitor is created in order to report the current state of the entity being watched. |
| IP |
PING |
The ICMP protocol within the IP parent protocol is used to PING network IPs. ipMonitor uses the PING protocol to determine that there is an active device on the network representing an IP address. Devices such as Internet Routers are often pinged to ensure that they are alive at their IP. |
| UDP |
DNS, SNMP, SNMP TRAP, Kerberos 5, RADIUS |
DNS is used to associate domain names with IP addresses when Monitors such as HTTP, SMTP, FTP, etc. are configured using domain names rather than IP addresses. |
| SMB |
FILE, Drive Space |
SMB is the underlying protocol used by NT for file and printer sharing. When the protocol is employed by ipMonitor to watch files, sufficient permissions to access the files is required to probe the files. |
| NT SPECIFIC |
ODBC |
ODBC is used to ensure that SQL database(s) is/are available via the network. An ODBC driver must be installed on the ipMonitor computer. The ODBC driver configuration determines what protocol will be used to communicate. |
|