Help - Search - Members
Full Version: clients in remote branches can't get policy and updates
Kaspersky Lab Forum > English User Forum > Protection for Small and Medium Businesses
Tariq Jaber
Hello dears
I have a problem pushing the policy and updates to clients in remote branches.
I have the Admin Kit installed on a server in the data center, the Admin Kit IP is 10.x.x.50/255.0.0.0. In the data center site there are clients with IPs like 172.11.x.x/255.255.0.0. The branches also with the range 172.11.x.x/255.255.0.0. The clients in the data center site with 172.11.x.x IP range have no problems getting the policies and the updates. In the remote branches, only the first PC that I installed Kaspersky Agent and workstation package on it can get the policy update and the updates successfully, the other PCs can't, even I installed them remotely using the Admin Kit console.

What is the main point to start troubleshooting with? Is this issue related to MAC addresses or something like this?

Regards,
Tariq Jaber
dawinci
Hello Tariq Jaber,

i suggest you to read following KB article 'How to create the hierarchy of Administration Servers ' and create slave servers in every branch to avoid such issues.

Regards,
dawinci
mastropizza
Hi,
once said that dawinci already gave you the best suggestion, i only suggest to check on those failing machines if the communication between Net Agent and AK Server is working fine...IMHO, something is missing on that side...you said that the first PC is working fine: what's about its installation? Was it local or remote via AK? Which version of AK are you working with?
M
Tariq Jaber
QUOTE(dawinci @ 10.05.2009 14:03) *
Hello Tariq Jaber,

i suggest you to read following KB article 'How to create the hierarchy of Administration Servers ' and create slave servers in every branch to avoid such issues.

Regards,
dawinci



Thanks dawinci for your suggestion, I already implemented a slave server for some branches but for those in which I'm facing the problem there is no slave server because the number of the clients is small; not more than 5 clients in eache one.
Tariq Jaber
QUOTE(mastropizza @ 11.05.2009 10:44) *
Hi,
once said that dawinci already gave you the best suggestion, i only suggest to check on those failing machines if the communication between Net Agent and AK Server is working fine...IMHO, something is missing on that side...you said that the first PC is working fine: what's about its installation? Was it local or remote via AK? Which version of AK are you working with?
M



Dear mastropizza,
There is a connectivity between the branches and the AK, I can telnet from the clients to the AK on ports 13000 and 14000. I removed KAV from the clients and reinstalled it without the agent, I choose the update source to be \\AK\klshare\update , the client can update from the share, I also can connect remotely from the AK to the clients. The problem is with the policy and updates when the agent is installed.
phr3n1c
QUOTE(Tariq Jaber @ 13.05.2009 07:16) *
Dear mastropizza,
There is a connectivity between the branches and the AK, I can telnet from the clients to the AK on ports 13000 and 14000. I removed KAV from the clients and reinstalled it without the agent, I choose the update source to be \\AK\klshare\update , the client can update from the share, I also can connect remotely from the AK to the clients. The problem is with the policy and updates when the agent is installed.

Please install Network Agent again. Open commandline on the client and switch to "c:\program files\kaspersky lab\networkagent\" and start "klnagchk.exe > klnagchk.txt". Please provide the whole file as an upload or copypaste the content.
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.
Invision Power Board © 2001-2009 Invision Power Services, Inc.