Technical White Paper


TNM: stands for Total Network Monitor and represents its name and trademark.

Minimum system requirements

CPU: 1000 Mhz.
Memory: 512 Mb.
Disk space: 30 Mb for the installation plus 1-5 Mb for the monitoring project.
Network: TCP/IP.
Operating system: Windows 2000 / Windows 2000 Server.

Requirements for remote devices

Sensor type
Internet sensors Appropriate protocol support and deployed TCP port availability
Windows sensors Windows NT4 / 2000 / XP Pro / Vista / 2000 Server / 2003 Server / 2008 Server / Windows 7; administrator rights; ipc$, admin$ resources
Registry state "Remote registry" service
System performance RPC protocol, open TCP port 135, "Windows management Instrumentation" (WMI) service
File sensors NetBIOS and SMB protocols, open TCP ports 139 and 445

Description of technology

The monitoring project consists of a network hierarchy (a tree-like device group hierarchy), manually created by the user and/or by means of scanning tools, and of monitors representing the basic element of network monitoring.

Network monitoring involves a variety of checks for each device in the network and an appropriate response according to the results of these checks. Each device includes monitors manually created by the user.

A Моnitor is a combination of a specific sensor with its parameters, of a list of actions that are executed according to the results of the sensor check, and of authorization credentials for certain kinds of sensors.

Network monitoring includes management of all project monitors and logging of their operations. Monitor operation consists of the execution of sensor checks at certain time intervals and of the execution of actions according to the conditions and check results. Every sensor check or action is logged.

Here's a diagram showing how TNM operates:


Potential risks

There are some rare problems in operation of TCP sensors. At the moment they are under examination and debugging process. The problems are related to large numbers of monitors deploying TCP sensor checks.

Encrypted passwords (for authorization in computers or services) are stored in the monitoring project file. Symmetrical proprietary block cipher is deployed in the program.

Page last modified 08:17, 19 Dec 2015 by Armo


Files (0)