Professional Documents
Culture Documents
KASPERSKY LAB
Kaspersky Network Agent 6.0
Page |1
EXAMPLE
2. Remove the entire remaining antivirus.
3. Your workstation already has the latest critical security patches from the Microsoft.
4.
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
Page |2
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.
Page |3
Page |4
Click YES to agree with the EULA(End User License Agreement) and continue.
Page |5
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\
Page |6
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.
Page |7
This page will show you the review about the setting that you key in before. Click NEXT to continue.
Page |8
Page |9
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.
P a g e | 10
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
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.
P a g e | 12
The network agent log will be create in the c:\ folder. This information is use for the troubleshotting
purpose only.
P a g e | 13
To check whether the policy from the admin kit applied to the Workstation, right-click on the
Kaspersky button and click Setting.
P a g e | 14
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.
P a g e | 15
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:
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
P a g e | 16
P a g e | 17