Kaspersky problem

[RJcreatives]

Hi Guys,

First off, I have only been working as an apprentice technician in a school for about 3 weeks now. I have been tasked with updating the Kaspersky anti virus on 229 computers which need it. However I am having a problem.

 

I have physically turned on all the machines which need updating, and then I will use Kaspersky to remotely update them all. The problem is, 95-100% of the time, Kaspersky is unable to communicate with the computers, and also I am unable to ping them. They are definately turned on and are all plugged in as they should be. They can even log on to the network. So then why can't the anti virus find them?

 

Using windows 7 on all computers and windows 2008 R2 for the network.

 

Any help or advice would be hugely appreciated.

 

Thanks

Edited August 8, 2012 by Dos_Box
Changed thread title to make more obvious what the problem is.

[Dos_Box]

Moving to Enterprise Software.

[kmount]

Is the Windows 7 firewall configured to ignore ping? (can you browse to them with \\nameofpc\c$)

 

I'm not too versed in Kaspersky management, does it need a port open on the client side to talk over? (maybe you need an exception added to the windows 7 firewall if it's on to let it connect)

[rich_tech]

I have had an issue with Kaspersky very similar to this too, the "Anti-Hacker" feature if enabled also acts as a firewall and stops the program registering with the AV Server, we found this out when we went initially from Symantec to them, after the grace period, certain machines wouldnt register the correct product key, this was usually because that feature was enabled on the AV software, our network, we have windows firewall disabled as default on the workstations and found that this feature if enabled (which it was by default by our initial LEA installation script) would also act as a firewall.

 

Check by removing the feature on a machine and seeing if it will work.

 

-Rich

Edited August 8, 2012 by rich_tech

[RJcreatives]

Thanks for your help guys. Unfortunately it has turned out that it is a problem with our server and cannot currently be fixed as we are virtualising.