A: Both a server and a workstation can run Total Network Monitor 2. It’s just a matter of usage convenience, because it's not a client-server application, and you need to have access to the graphical console of the computer it's installed on, either directly or by using a remote desktop utility. However, if you run it under the domain admin account, you’ll be able to run monitors with WINDOWS and FILE sensors as "current user" – otherwise you’d need to specify domain admin credentials explicitly (for example, those of the domain administrator).
However, take note that if you install the program on Windows XP SP2/SP3, Vista or 7 and there are a lot of TCP checks running simultaneously, these checks may return incorrect results. This is caused by a restriction on the maximum number of TCP half-open connections (connection attempts, SYN_SENT socket state) existing in the aforementioned Windows versions, which doesn't allow for more than 10 outbound connections to be in this state at a time. After reaching this limit, all other connections in the system (including those executed by this program) are queued and may reach their timeout, thus producing inconsistent results. This issue is also known as the “Event 4226” issue, because reaching the limitation produces a record in the System Event Log with EventID 4226. Windows 2000 Professional, XP SP0/SP1 and all Windows Server systems don't have such a limitation. Thus, in the general case, we recommend to install the program on server systems.
A: The program revolves around 4 main points:
1. Device: any device in the network with an IP address.
2. Monitor: enables control over various aspects of device operation and execution of actions. It consists of:
2.1. Sensor: an integral part of the monitor; it directly checks the devices. There are 3 groups of sensors (Internet sensors, Windows sensors, File sensors).
2.2. Action(s): enables alerting and taking certain measures according to user-set parameters.
See TNM's operational structure below:
A: Any monitor belongs to a device, which in turn belongs to a group. That's why at first it's necessary to create a group and a device.
More details about operations with monitors here...
A: During its work the monitor is able to assume three colors: black, red and green. Black color means that an error has occurred during sensor operation (e.g. failure to receive authorization on the remote Windows PC). The other two colors display the logical result of a check. For file sensors you can set the rules of color change yourself.
A: TNM maintains 4 logs:
In All monitors log the records on all monitors are displayed. A new record is created only when a monitor changes color.
Current monitor's log only displays the records originating from the monitor selected in the list.
Records on all performed actions are logged in Executed actions. If an action has been executed with an error, an appropriate record is highlighted red, and the error information is included into the entry.
Statistical information about the monitor selected in the list is shown in Current monitor's activity.
More details about logging here...
A: An Activity diagram shows all the color states that the selected monitor has been in during its run. Every check is labeled by a square, its color defined by the result of the check. A multitude of squares of the same color form a block.
A: Choose Help (?) -> Check for updates in the top right corner of TNM's window. If there's a new update press Download. The update will be installed right after TNM exits.
A: If a device obtained a static IP, it will always be used during monitoring. Otherwise, TNM will try to resolve the hostname each time and receive the current IP address.
A: Yes. Select the log. Right-click on it and select one of the export formats.