Kaspersky Administration Kit 6.0 MP1/MP2

	Useful links
	The klnagchk.exe utility

If

- policies are not deployed on client computers

- the Server is not trying to synchronize to the client computer manually

- the color of the computer is not bright

- its value in the Last connect field does not display the current date and time plus/minus 15-30 minutes (if the workstation is not turned off, of course)

then probably there is no connection between the Agent and the Administration Server.

To know the reasons why the connection fails use the klnagchk.exe utility. It has been developed to analyze connection parameters of the Administration Agent and the Administration Server.

Run the utility on the computer where you have the problem from the Network Agent setup directory (C:\Program Files\Kaspersky Lab\NetworkAgent) under the local administrator rights. It is recommended that you log its work results to the log-file.

The reasons why the connection fails may be the following: 

• Administration Agent is not installed on the client computer. 

• Administration Agent was installed on the client computer locally and either the address or the port of the administration Server was defined incorrectly.

• Kaspersky Network Agent is not running on the client computer. 

• Kaspersky Administration Server is not running on the Administration Server. 

• There are several workstations with the same name in the network and a wrong workstation was added to the group when dragging (by mistake). Use the search command (from the context menu of the Server run the Find computer command) to find computers with the same name – enter the PC name and *: for example, COMPUTER*. 

• This client computer is already connected to another Administration Server of the Windows-network. 

• Client computer is turned off at the moment. 

• The Administration Server computer is not accessible from the client computer. 

• Run the ping command on the client computer to check. 

• TCP-ports 13000 and/or 14000 are blocked on the computer with the Administration Server.

You can check if the ports are open using the following utilities: 

• fport.exe.

Run it on the computer <Administration_Server_name>, to make sure the Administration Server can really open the ports 13000/14000 (name of the Administration Server process is klserver). 

• netstat, if the fport utility failed to display the list of open ports (e.g. it does not maintain Microsoft Windows 2003 Server):

netstat -a 

• telnet (from the computer where you have problem!)

telnet <Administration_Server_name> 13000

or

telnet <Administration_Server_name> 14000

If the telnet command displayed an error message it means the ports are closed (probably they are firewall-protected, etc) 

• UDP-port 15000 is blocked on the client computer.

• Either the name or the IP-address of the Administration Server is reproduced incorrectly on the client computer: i.e. the name and the IP-address of the Server do not correspond to each other.