Hi everyone.

I'm having several problems with the Administration Kit 6.0 changing the IPs of the workstations, deploying KAV, and running tasks.

Recently I've had to change our IP scope and for a week, the admin kit kept reading the old IPs for the computers. Needless to say, this caused them to not be updated. I read around and tried re-scanning the network for it to read the new IPs, which didn't work. Finally I've resolved the problem by deleting all computers from the groups, and the network in the admin kit and having it re-add them.

Now all workstations and servers show up and have the new IPs. Although, the only one that is "current"/updates/shows information is the server the admin kit is on. All other servers and workstations are represented in critical condition and don't show any of what's installed, or the tasks they should have. I've redeployed to all workstations in hopes that this would fix the problem and re-coordinate to the server.. Avast, nay. I even ran an experiment on my workstation completely uninstalling KAV Workstation 6.0.3.837 and re-deploying it via the admin kit, now instead of having my definitions last updated 5/21/2009, they are 11/19/2007. I can't update because that's controlled through the admin kit which although the admin kit communicates to the workstations, it seems to not think it does.

Another problem that has recently occurred since the admin kit isn't registering the computers, is that the local KAV on each workstation is every now and then "there" and then "not". As if it doesn't feel like running all the time when it's not being watched. So frequently workstations are even without out-dated definitions.

I'd like to avoid re-installing the administration kit and uninstalling KAV from every workstation, but I've tried everything else I can think of and every option that has the slightest relevance in the admin kit.

Your help with this is greatly appreciated. Thank you.

Hi,

Please run the klnagchk.exe utility from a remote computer having Network Agent installed.
This file is stored in the installation folder of Kaspersky Network Agent, and will help to troubleshoot communication issues.
Post results shown by the execution of this tool.

Starting utility 'klnagchk'...
Checking command line options...OK
Initializing basic libraries...OK
Current host is Domain\ComputerName


Reading the settings...OK
Settings verification...OK
Network Agent settings:
Administration Server address: '192.168.1.8'
Use SSL connection: 1
Numbers of the Administration server SSL ports: '13000'
Numbers of the Administration server ports: '14000'
Administration Server certificate: available
Use proxy server: 0
Open UDP port: 1
Numbers of UDP ports: '15000'
Synchronization period, min.: 15
Connection timeout, sec.: 30
Send/receive timeout, sec.: 180

Attempt to connect to the Administration server...
-----------------------------------------------------------------

This is what the check pulls up. It hangs for a few seconds trying to connect to the server and closes.

Edit: When trying to synchronize, it brings an error saying that it couldn't connect to the host and that it'll try again when the host becomes available.

Is 192.168.1.8 the old or the new IP Address of your Kaspersky Administration Server ?

Old. I'm not sure why, this is after I made a new Administration Server with the new IP and redeployed the network agent and AV.

Ok it makes sense.

At first, look at your Administration Console, in the Installation Package node you will find the network agent installation package.
Right click on it and open properties to check which IP Address is configured, I guess it's still the old IP Address. Fix this if necessary then you won't have this problem for your future deployments.

Also you don't have to reinstall network agent on all your hosts, you just need to change the IP Address of the Administration Server they should connect to. To perform this operation run this command on your hosts :

klmover -address xxx.xxx.xxx.xxx (where xxx.xxx.xxx.xxx is the new IP Address of your Kaspersky Administration Server)

After it will be ok, your should be able to synchronize your hosts from the console.
Also you can deploy a batch file with this specific command on all your hosts to change this settings using Adminsitration Kit, then you won't have to change it manually on each computers.

Thank you very much Tybilly. I can't believe it was such an easy fix and I didn't even think about looking there for the problem.

Edit: I feel kinda silly, but I don't have much experience with batch files.. Could you point me to a link or inform me how to create a batch file that allows me to remotely run klmover on each host?