The klnagchk.exe utility is designed to analyze parameters of connection between Network agent and Administration server.
The utility allows to determine which parameters Network agent uses to connect to the administration server and run a basic connection troubleshooting.
Important. The klnagchk.exe utility should be run on a client PC by an account having local administrator permissions. The utility will not work if run from another folder due to a lack of access to Network agent libraries.
The utility is included into Network agent distribution package and is located in Network agent installation folder (C:\Program Files\Kaspersky Lab\NetworkAgent).
When run from the command prompt the
klnagchk utility performs the following actions depending on the switches in use:
- Displays or logs to an event report values of connection settings of the Administration Agent installed on a client computer to Administration Server.
- Logs statistics of Administration Agent (since it last start) and results of the utility execution to a report or displays the information on the screen.
- Makes an attempt to establish connection of Administration Agent to Administration Server. If the utility failed to establish the connection, it ICMP-packet to check the computer status on which Administration Server is installed.
In order to check connection of a client computer with Administration Server using the klnagchk utility, run the klnagchk utility from the command prompt on a client computer from the command prompt.
The utility syntax:
klnagchk [-logfile <file_name>] [-sp] [-savecert <path_to_certificate file>] [- restart] [-sendhb]
where:
-logfile LOGFILE – write all information into a report file LOGFILE, by default the information is displayed via a standard output stream, i.e. on the screen.
-sp – outputs symbols of the password for proxy server access, by default the password is not displayed.
-savecert CERTFILE – save the certificate used by Network agent to connect to the Administration server into a CERTFILE file.
-restart – restart Network Agent once the utility work is over.
-sendhb – send a heartbeat.
When started, the utility will immediately access Network agent configuration files and output connection parameters:
- Server address – Administration server address
- Use SSL – use of a secure connection with Administration server, can be 0 or 1
- Server SSL ports – allowed port numbers for secure connection to the Administration server; only one port is used usually
- Server ports – allowed port numbers for standard (non-secure) connection to the Administration server; only one port is used usually
- Certificate – availability of an Administration server certificate on the client PC; it might be absent for some reason, for example if Network agent has never established a connection to the Administration server, can be 0 or 1
- Use proxy – usage of a proxy server, can be 0 or 1
- Proxy location – proxy server address and port number, separated with a two-spot
- Proxy login – user name to access the proxy server
- Proxy password – password to access the proxy server, is displayed only when using sp switch
- Open UDP port – usage of a UDP port by Network agent for receiving Administration server synchronization requests
- UDP ports – UDP port numbers available for use by Network agent
- Ping period – standard time interval between synchronizations, in seconds
- Conn timeout – connection time-out
- RW timeout – read/write operation time-out
- Computer ID - unique ID in the network.
When started on a PC with installed Administration server, instead of making a connection attempt the utility will report that there is a local Administration server.
Regardless of the result of an attempt to connect to the Administration server, the utility tries to determine if Network agent is started. If there is no Network agent service running, the utility will terminate. If the Network agent service is running, the utility will output connection statistics:
- Ping count – number of attempts to connect to the Administration server
- Succ. pings – number of successful connection attempts
- Sync count – number of synchronization attempts
- Succ. syncs – number of successful synchronization attempts
- Last ping – last connection date and time
