Update - what was going on today?

[swoop]

Just a while ago I checked the event log and I saw this:
1.3.2005 16:44:24 Kernel The virus signature database has been updated successfully to version 1.1015 (20050301).
1.3.2005 13:44:19 Kernel The virus signature database has been updated successfully to version 1.1014 (20050301).
1.3.2005 12:51:21 Kernel The virus signature database has been updated successfully to version 1.1014 (20050301).
1.3.2005 11:44:37 Kernel The virus signature database has been updated successfully to version 1.1014 (20050301).
1.3.2005 09:45:41 Kernel The virus signature database has been updated successfully to version 1.1013 (20050301).

3x the same version, but no visible component update. What was updated then? Maybe there was something wrong with my Internet connection or maybe some hotfixes in the definitions have been done.

Can anybody explain?

[webyourbusiness]

I just got 1.1016 as well... looks like a 4 update day!

[auriell]

??? I tired to update, but it still shows VDF version 1.1010. It connects to the serwer and than behave like there is no update available. What the ...???

[Blackspear]

{QUOTE-> ??? I tired to update, but it still shows VDF version 1.1010. It connects to the serwer and than behave like there is no update available. What the ...??? <-QUOTE}Do you have servers set to "Choose Automatically"?

Cheers ;D

[sukarof]

Hmm...I never got som updates?! ( 1.1011, 1.1012, 1.1014 and 1.1015) I have NOD32 checking for updates every hour (connected to the net 24/7) and have not cleaned my log for weeks. I have NOD32 set to choose update server automaticly....Strange.....


Time Module Event User
2005-03-02 13:00:41 Kernel The virus signature database has been updated successfully to version 1.1016 (20050301).
2005-03-02 00:29:02 NOD32 An infiltration has been detected. See the on-demand scanner Log for details. ZIMBA-VVDTD7TEJ\zerba
2005-03-01 09:24:44 Kernel The virus signature database has been updated successfully to version 1.1013 (20050301).
2005-02-28 09:49:08 NOD32 An infiltration has been detected. See the on-demand scanner Log for details. NT AUTHORITY\SYSTEM
2005-02-27 15:56:27 Kernel The virus signature database has been updated successfully to version 1.1010 (20050227).
2005-02-26 06:11:10 Kernel The virus signature database has been updated successfully to version 1.1008 (20050225).
2005-02-25 07:38:41 NOD32 An infiltration has been detected. See the on-demand scanner Log for details. ZIMBA-VVDTD7TEJ\zerba

Btw the infiltration is just the eicar test virus

[auriell]

Blackspear ---> No, I don't. When I had the download was terribly slow (2kb/s). Then I set server manually and transfer was OK and I have no problems with updates till last 2 days (?) when it stacked on 1.1010

[auriell]

Somehow could not edit my previous post.

I will check at home if "Choose Automatically" will help, and if it's not to slow.

[Blackspear]

{QUOTE-> Somehow could not edit my previous post.

I will check at home if "Choose Automatically" will help, and if it's not to slow. <-QUOTE}No worries, let us know how you go...

Cheers ;D

[Blackspear]

{QUOTE-> Hmm...I never got som updates?! ( 1.1011, 1.1012, 1.1014 and 1.1015) I have NOD32 checking for updates every hour (connected to the net 24/7) and have not cleaned my log for weeks. I have NOD32 set to choose update server automaticly....Strange..... <-QUOTE}I have just confirmed what I thought with Eset, if you miss an update, it is caught when you do so next time...

You are fully up-to-date.

Cheers ;D

[sukarof]

{QUOTE-> I have just confirmed what I thought with Eset, if you miss an update, it is caught when you do so next time...

You are fully up-to-date.

Cheers ;D <-QUOTE}

Never doubted that :)
But I appriciate the confirmation though :)

[auriell]

u2.eset.com (my previous setting for download server) - does not update
u5.eset.com (current setting) - update done to 1.1016

So not all of ESET servers have most current VDD

[Marcos]

All update servers are up to date. Since u2.eset.com no longer exists, it's obvious you cannot download updates from it.

The update server should always be set to automatic selection unless you update from a local mirror, otherwise you might not get updates if one of the servers fails !!!

[webyourbusiness]

marcos,

just a suggestion that will help out...

since u2 doesn't exist, change the nameserver record to point to the LEAST loaded server - this will cover the instance where a user has it hard-set to u2.

regards

Greg

[auriell]

Yes, it should be fixed anyhow. The update process on non-existing server looks pretty much like on the running one with no updates available. It should display something like: "can not connect", or some other error message.