TNM minimum specs

Terms

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

Minimum system requirements


CPU	1000 MHz
RAM	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	Requirements
Windows sensors	Windows NT4, 2000, XP Pro, Vista, 7, 8, 8.1, 10, Server 2000/2003/2008/2012(incl R2)/2016; administrator rights; ipc$, admin$
Internet sensors	Appropriate protocol support and deployed TCP port availability
System performance	RPC protocol, open TCP port 135, "Windows management Instrumentation" (WMI) service
Registry state	"Remote registry" service
File sensors	NetBIOS and SMB protocols, open TCP ports 445 and 139

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.