What's up with the servers? ;-)

I installed v. 2.70.12 RC on Nov. 10th and so far have not had a single failed update. This is miraculous. I just hope I haven't spoken too soon.

 

Same here, every update was successful.

 

I guess they added Win32/failedupdate to the virusdefinitions...

 

There are new update server online and there has been some decent tuning performed to facilitate workload sharing.

 

That's because it's disabled in 2.7
You'll only get an error if it can't reach any of the servers at all.

 

From my Event Log:
Time Module Event User
11/16/2006 15:11:45 PM Kernel The virus signature database has been successfully updated to version 1869 (20061116).
11/16/2006 15:11:07 PM Update Update attempt failed (Server connection failure) xxxxxx/xxxxxxx
11/16/2006 15:09:57 PM Update Update attempt failed (Server connection failure) xxxxxxx/xxxxxxx
11/16/2006 15:04:02 PM Update Update attempt failed (Server connection failure)
11/15/2006 16:00:42 PM Kernel The virus signature database has been successfully updated to version 1868 (20061115).
11/15/2006 14:00:36 PM Kernel The virus signature database has been successfully updated to version 1867 (20061115).
11/14/2006 22:24:29 PM Update Function: gethostbyname, parameters: , return value: 11001
11/14/2006 22:24:28 PM Update Update attempt failed (Server connection failure.)

 

Are you actually using v. 2.7 and have the server set to automatic selection? In such case, these errors should only appear if NOD32 was unable to connect to neither of the update servers. Virtually this would only happen if there was a connectivity problem on your side as the udpate servers have been running fine.

 

I am using v2.7RC1 and have the server set to automatic selection and no connectivity problems on my side.

 

Hello,

Over the past month, ESET has not-quite doubled the number of update servers, as well as introduced dedicated servers for program downloads. This has improved the reliability of downloading both updates and copies of the software.

Also, please note that the he production version of NOD32 has been released. For more information, please see this thread. It should be replace the NOD32 v2.7 RC1 version which is currently on your system.


Regards,

Aryeh Goretsky