Nod start today out of date

This mornig I Nod 32 start up with definition out of date.
You can see what I say:
Time Module Event User
15/12/2006 08:58:31 Kernel Statistical information has been sent to ESET, spol. s r.o.
15/12/2006 08:49:24 Kernel The virus signature database has been successfully updated to version 1923 (20061215).
15/12/2006 08:48:25 Kernel The virus signature database has been successfully updated to version 1861 (20061110).
14/12/2006 17:54:21 Kernel The virus signature database has been successfully updated to version 1922 (20061214).
14/12/2006 11:54:15 Kernel Statistical information has been sent to ESET, spol. s r.o.
14/12/2006 08:54:25 Kernel The virus signature database has been successfully updated to version 1921 (20061214).
13/12/2006 18:57:43 Kernel The virus signature database has been successfully updated to version 1920 (20061213).
13/12/2006 09:57:40 Kernel Statistical information has been sent to ESET, spol. s r.o.
13/12/2006 07:57:06 Kernel The virus signature database has been successfully updated to version 1919 (20061213).
12/12/2006 17:56:12 Kernel The virus signature database has been successfully updated to version 1918 (20061212).
12/12/2006 12:49:21 Kernel The virus signature database has been successfully updated to version 1917 (20061212).
12/12/2006 07:49:18 Kernel The virus signature database has been successfully updated to version 1916 (20061212).
11/12/2006 20:36:49 Kernel The virus signature database has been successfully updated to version 1915 (20061211).


What happen with Nod? I don´t understand?
Again sorry by my english.

 

lol

 

guilijan, perhaps there was an issue with the server your NOD was updating from, as it appears to have downloaded old definitions, then less than a minute later new ones.

Have you tried rebooting your PC to see if the same problem occurs? Could be worth a try, or wait until another definition update is released and see what happens.

 

Is the server set as "Choose Automatically"?

Cheers

 

Yes it is.
But see specially this:
15/12/2006 08:48:25 Kernel The virus signature database has been successfully updated to version 1861 (20061110).

Before it
14/12/2006 17:54:21 Kernel The virus signature database has been successfully updated to version 1922 (20061214).

And after it
15/12/2006 08:49:24 Kernel The virus signature database has been successfully updated to version 1923 (20061215).


It's very strange or unusual.
I watch it by the security center windows icon red on the task bar and a pop that say antivirus database out of date or something like that..

 

Please list all the NOD32 Servers that are mentioned in your "Location> Server" area.

Cheers

 

FWIW-
One client on the LAN (a Win 98 box) had the same issue. The clients ONLY update via the mirror here- no external servers-
Event Id Client Name Date Received Module Type Event Comment
Event 35237 Service 12/15/2006 10:09:16 AM 12/15/2006 10:18:31 AM Kernel Normal The virus signature database has been successfully updated to version 1924 (20061215).
Event 35236 Service 12/15/2006 10:06:42 AM 12/15/2006 10:08:31 AM Kernel Normal The virus signature database has been successfully updated to version 1861 (20061110).
Event 35235 Service 12/15/2006 10:06:02 AM 12/15/2006 10:08:31 AM Kernel Normal The virus signature database has been successfully updated to version 1861 (20061110).
Event 35234 Service 12/15/2006 10:04:56 AM 12/15/2006 10:08:31 AM Kernel Normal The virus signature database has been successfully updated to version 1861 (20061110).
Event 35233 Service 12/15/2006 10:01:05 AM 12/15/2006 10:04:41 AM Kernel Normal The virus signature database has been successfully updated to version 1861 (20061110).
Event 35204 Service 12/15/2006 9:00:05 AM 12/15/2006 9:04:41 AM Kernel Normal The virus signature database has been successfully updated to version 1861 (20061110).
Event 35167 Service 12/15/2006 8:00:05 AM 12/15/2006 8:04:41 AM Kernel Normal The virus signature database has been successfully updated to version 1861 (20061110).
Event 35160 Service 12/15/2006 7:00:05 AM 12/15/2006 7:04:42 AM Kernel Normal The virus signature database has been successfully updated to version 1861 (20061110).
Event 35133 Service 12/15/2006 5:59:58 AM 12/15/2006 6:04:42 AM Update Warning Error occurred while updating program modules (Update file damaged.)
Event 35097 Service 12/15/2006 4:59:06 AM 12/15/2006 5:04:42 AM Kernel Normal The virus signature database has been successfully updated to version 1861 (20061110).
Event 35096 Service 12/15/2006 3:59:07 AM 12/15/2006 4:04:43 AM Kernel Normal The virus signature database has been successfully updated to version 1861 (20061110).
Event 35095 Service 12/15/2006 2:59:07 AM 12/15/2006 3:04:43 AM Kernel Normal The virus signature database has been successfully updated to version 1861 (20061110).
Event 35094 Service 12/15/2006 1:59:08 AM 12/15/2006 2:04:43 AM Kernel Normal The virus signature database has been successfully updated to version 1861 (20061110).
Event 35093 Service 12/15/2006 12:58:10 AM 12/15/2006 1:04:43 AM Kernel Normal The virus signature database has been successfully updated to version 1861 (20061110).
Event 35092 Service 12/14/2006 11:58:10 PM 12/15/2006 12:04:44 AM Kernel Normal The virus signature database has been successfully updated to version 1861 (20061110).
Event 35091 Service 12/14/2006 10:58:12 PM 12/14/2006 11:04:44 PM Kernel Normal The virus signature database has been successfully updated to version 1861 (20061110).
Event 35090 Service 12/14/2006 9:58:13 PM 12/14/2006 10:04:42 PM Kernel Normal The virus signature database has been successfully updated to version 1861 (20061110).
Event 35089 Service 12/14/2006 8:57:11 PM 12/14/2006 9:04:44 PM Kernel Normal The virus signature database has been successfully updated to version 1861 (20061110).
Event 35088 Service 12/14/2006 7:57:08 PM 12/14/2006 8:04:44 PM Kernel Normal The virus signature database has been successfully updated to version 1920 (20061213).
Event 35087 Service 12/14/2006 6:57:08 PM 12/14/2006 7:04:09 PM Kernel Normal The virus signature database has been successfully updated to version 1920 (20061213).


After unsuccessfully trying to maual update- got the same OLD def files, I had the user reboot and manually update and all was well.

 

u1.eset.com
u3.eset.com
u20.eset.com
u21.eset.com
u22.eset.com
u23.eset.com
u24.eset.com
u25.eset.com
u26.eset.com
u27.eset.com
u28.eset.com
u29.eset.com
82.165.250.33

 

Everything seems ok until something happened and NOD32 had to download the definitions again . System Restore ? Registry cleaner ? You touched the NOD32's folder / reg keys ?

No matter what the problem was , if this worries you , just reinstall . If you want instructions , post back .

 

I didn't do anything, just start the pc, I'm just worried about the behave of Nod and a possible security failure.
You can see that a statical information has been sent after the problem. I hope it can help Nod with this problem.

Time Module Event User
15/12/2006 08:58:31 Kernel Statistical information has been sent to ESET, spol. s r.o.
15/12/2006 08:49:24 Kernel The virus signature database has been successfully updated to version 1923 (20061215).
15/12/2006 08:48:25 Kernel The virus signature database has been successfully updated to version 1861 (20061110).

 

Hi ! Yes , guilijan , I noticed about the Statistical info but it won't help ESET because it is not related to problems . Moreover NOD32 itself doesn't treat that as a problem , it noticed older definitons and it fixed it by applying the new ones

Just to mention , hopefully , I have never had such problems . Anyway , my previous words are still valid

 

Well I'm not alone, gerrya has a similar problem as I can understand and as you can see in this thread.

 

Sorry , I just now noticed gerrya's post . I read only your post and tried to answer .

 

Hi Blackspear you asked for the servers and no answer after that. Any idea about the problem?
Thanks in advance.

 

Hi guilijan, no, other than it having a non Eset server listed, which is not the case from your list.

Put it down to a full moon and keep an eye on it for a few days.

Cheers

 

What happens with Nod Update

Please look the event log specially the dated 17/01/2007 13:05:27

Can somebody explain it?

Time Module Event User
17/01/2007 13:06:01 Kernel The virus signature database has been successfully updated to version 1985 (20070117).
17/01/2007 13:05:27 Kernel The virus signature database has been successfully updated to version 1928 (20061219).
17/01/2007 08:05:04 Kernel The virus signature database has been successfully updated to version 1984 (20070117).
17/01/2007 04:06:25 Kernel Statistical information has been sent to ESET, spol. s r.o.
16/01/2007 23:05:14 Kernel The virus signature database has been successfully updated to version 1983 (20070117).

 

"Please list all the NOD32 Servers that are mentioned in your "Location> Server" area"

 

Also PM me your username so that I can check your license.

 

Hi Marcos I've sent you by PM my user name. My licence expires 08/23/2008
To Bubba
82.165.250.33
u20.eset.com to u29.eset.com
And set to choose automatically.

It did not remember the other thread that you have joined but as you can see it's not the first time.

 

Hi Marcos, something new?
Have you recived my PM?

 

Yep, but I have no clue as to why it's happening on your pc.

 

Perhaps Eset can send by an update, an exorcist to my pc

Have you sent this thread to Eset? May be they have something to do about this in future. My english is very bad and I can't explain correctly to Eset this problem so can you do?

Thank you Marcos

 

Same thing happened to me a while ago.


Time Module Event User
1/12/2007 20:22:35 PM Kernel The virus signature database has been successfully updated to version 1975 (20070113).
1/12/2007 19:58:49 PM Kernel The virus signature database has been successfully updated to version 1860 (20061109).
1/12/2007 16:58:08 PM Kernel Statistical information has been sent to ESET, spol. s r.o.
1/12/2007 14:58:14 PM Kernel Statistical information has been sent to ESET, spol. s r.o.
1/12/2007 10:57:40 AM Kernel The virus signature database has been successfully updated to version 1974 (20070112).
1/12/2007 7:57:31 AM Kernel The virus signature database has been successfully updated to version 1973 (20070112).
1/11/2007 17:38:00 PM Kernel The virus signature database has been successfully updated to version 1972 (20070111).

 

Ok, then this is not only my problem, at least this happened to three users.
I think it's a server problem, for some reason, perhaps some delay in the network, the server assumes something that I don't know and do this bad update but after it have done this it corrects immediately to a good update.
So if I'm in the correct way, it's a problem that Eset has to solve because this is not a correct operation.

 

Do you use a Registry cleaner?

Does the time of your system reset itself / lose or gain time, as in maybe your need to replace the CMOS battery on your motherboard?

Please list your servers again.

Cheers