Client virus signature Updates Fails

Most if not all Nod32 clients are getting this error message "ESET NOd32 Antivirus has not been able to connect to the update server recently to check for the latest virus signature updates. Please check your network connectivity and then try to update the virus signature again.

Client version: 4.0.4670.0
virus signature: 4587 (20091109)

ERAS ver: 3.1.11
virus signature DB: 4590 (20091109)

We have to reboot the ERAS server then updating resumes to normal. However, we need to figure out what is trigerring this recurring failure.


Thanks.

 

Are your clients updating using http or a network share?
The http server from ERA is known to have issues.

 

On the client machine, they are pointing to the update server using http://nod32server:2221.

If we opt to use updating via network share, how do I setup that on the client machine?

Thanks for the reply.

 

Try to restard ERA HTTP Server services. In your browser on a client, type http://http://nod32server:2221/update.ver (or maybe it's http://http://nod32server:2221/mirror/update.ver sorry i'm not sure ...)

If the page doesn't load, then you have a communication problem (firewall? cable? port not opened?)

If you see a page full of characters then everything should work.

To set mirror with share just uncheck "Provide update trough HTTP server"

Then here is the server path for update \\COMPUTERNAME\Your_Mirror_Path

If you setup your mirror directory to C:\UPDATE_NOD32 (Don't forget to share this directory with the appropriate rights for clients) and your server is called "SERVER" then it will be \\SERVER\UPDATE_NOD32

Then it will be \\SERVER\UPDATE

 

As I said, ERA http server has issues.
Depending of your number of clients, it will stop serving clients at random intervals. The more clients you have the intervals between "crashes" are shorter.

We used to schedule a task every 24 hours, then every 12 hours, to restart the ERA http server, but in the end we switched to update through network share.

IF you must use http for updates you can configure IIS as http server for client updates. You will find articles on how to configure IIS for serving NOD32 updates here on forums and I think there is a KB article on ESET web site as well.

EDIT: I actually found the kb article here