You are on page 1of 17

AVP (SEA) SDN BHD

KASPERSKY LAB
Kaspersky Network Agent 6.0

Red For Threats. Green For You.

Page |1

AVP (SEA) SDN BHD

Kaspersky Administration Agent (or Network Agent) Installation.


Administration Agent (or Network Agent) interacts between Administration Server and Kaspersky
Lab anti-virus applications installed on the definite net node (Workstation or server).
Network Agent should also be installed for anti-virus local control via Administration Console (e.g. to
manage locally Kaspersky Antivirus 5.0 for Windows File Servers)
Network Agent is installed on the client computer to provide connection between Administration
Server and the client and/or to manage Antivirus locally.

Before the installation please make sure that:


1. Your systems date is correct with the current date.

EXAMPLE
2. Remove the entire remaining antivirus.
3. Your workstation already has the latest critical security patches from the Microsoft.
4.

System requirements to install Network agent are the following:

Operating systems:
- Microsoft Windows 98
- Microsoft Windows ME
- Microsoft Windows NT Server / Workstation 4.0 SP 6a and above
- Microsoft Windows 2000 Server / Professional SP1 and above
- Microsoft Windows XP Professional / Home SP1 and above
- Microsoft Windows Server 2003
Processor: Intel Pentium 233 MHz and faster
System memory: 32 MB
Available hard drive space: 10 MB

Red For Threats. Green For You.

Page |2

AVP (SEA) SDN BHD

EXAMPLE

Use the ping command to check whether the workstation could establish the connection to the
admin kit or not.

EXAMPLE

To check whether there is a connection between the adminkit and workstation you can telnet to
the Administrator Kit IP using port 13000 from the Workstation.

Red For Threats. Green For You.

Page |3

AVP (SEA) SDN BHD

Run the setup.exe located at Kaspersky Anti-virus Installation CD.

The InstallShield Wizard will be run.

Red For Threats. Green For You.

Page |4

AVP (SEA) SDN BHD

Click NEXT to continue with the installation for Network Agent

Click YES to agree with the EULA(End User License Agreement) and continue.

Red For Threats. Green For You.

Page |5

AVP (SEA) SDN BHD

Type in the username and company name in the field. Click NEXT to continue.

By default the Kaspersky Network Agent will be install in C:\Program Files\Kaspersky Lab\
NetworkAgent\

Red For Threats. Green For You.

Page |6

AVP (SEA) SDN BHD

EXAMPLE

Type the Kaspersky Adminkit Server IP address inside Server address. As an example : 172.16.16.202
and click Next. Please refer to your network administrator about your Kaspersky Admin Kit Server
Address.

Click NEXT to continue.

Red For Threats. Green For You.

Page |7

AVP (SEA) SDN BHD

Click NEXT to continue.

This page will show you the review about the setting that you key in before. Click NEXT to continue.

Red For Threats. Green For You.

Page |8

AVP (SEA) SDN BHD

The installation begin.

Click Finish to finish the installation.

The Network Agent will automatically run.

Red For Threats. Green For You.

Page |9

AVP (SEA) SDN BHD

To make sure that the Network Agent is already running you can check it using the Windows Task
Manager. The process running is klagent.exe.

Red For Threats. Green For You.

P a g e | 10

AVP (SEA) SDN BHD

After the installation the kaspersky will automatically create the Kaspersky Administration Kit
exception.

This is the right configuration of the exception which is open the UDP 15000 port.
Red For Threats. Green For You.

P a g e | 11

AVP (SEA) SDN BHD

After the installation, to check whether the connection between the Network Agent and the Admin
Kit is going well go to the command prompt and enter to the Network Agent Folder:
C:\Program Files\Kaspersky Lab\NetworkAgent\
Type klnagchk.exe and press Enter.
Please make sure that the Administrator Server address is correctly point to the Administrator Kit
address.

Red For Threats. Green For You.

P a g e | 12

AVP (SEA) SDN BHD

How to export the Network Agent communication statistics.

The network agent log will be create in the c:\ folder. This information is use for the troubleshotting
purpose only.

Red For Threats. Green For You.

P a g e | 13

AVP (SEA) SDN BHD

To check whether the policy from the admin kit applied to the Workstation, right-click on the
Kaspersky button and click Setting.

Before Network Agent Installation. User can change the setiing.

Red For Threats. Green For You.

P a g e | 14

AVP (SEA) SDN BHD

After the Network Agent Installation. As you can see from the screen shot above, all the setting has
been lock(prevent user from doing changes and exiting the antivirus ) after being applied policy from
Kaspersky Administrator Kit.
*Please refer to Kaspersky Administrator Kit manual on group policies(settings) and group task.

Troubleshotting issues : Why does the Administration Agent fail to connect the
Administration Server?
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.

Red For Threats. Green For You.

P a g e | 15

AVP (SEA) SDN BHD

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 Windowsnetwork.
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:
-

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

Red For Threats. Green For You.

P a g e | 16

AVP (SEA) SDN BHD


*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.

Red For Threats. Green For You.

P a g e | 17

You might also like