why nod32 keep update to the same sig. version

wonder why nod32 keep update to the same sig. version:


Time Module Event User
9/29/2006 17:02:31 PM Kernel The virus signature database has been successfully updated to version 1.1782 (20060928 ).
9/28/2006 22:45:19 PM Kernel The virus signature database has been successfully updated to version 1.1781 (20060928 ).
9/28/2006 21:45:10 PM Kernel The virus signature database has been successfully updated to version 1.1781 (20060928 ).
9/28/2006 17:54:36 PM Kernel The virus signature database has been successfully updated to version 1.1781 (20060928 ).
9/28/2006 16:54:19 PM Kernel The virus signature database has been successfully updated to version 1.1780 (20060927).
9/27/2006 22:29:12 PM Kernel The virus signature database has been successfully updated to version 1.1778 (20060927).
9/27/2006 22:28:57 PM Kernel The virus signature database has been successfully updated to version 1.1778 (20060927).
9/27/2006 22:28:30 PM Kernel The virus signature database has been successfully updated to version 1.1778 (20060927).
9/27/2006 21:57:32 PM Kernel The virus signature database has been successfully updated to version 1.1778 (20060927).
9/27/2006 17:50:52 PM Kernel The virus signature database has been successfully updated to version 1.1778 (20060927).
9/26/2006 22:46:43 PM Kernel The virus signature database has been successfully updated to version 1.1776 (20060926).

 

my guess is that a checksum somewhere on the update servers was incorrect - this would cause the checksum to appear like the update needed to be applied. I would think that it got fixed within 5 hours on the update servers and then the updates stopped downloading themselves each time a check was made.

It's nothing to worry about - you were still running the latest update at each possible instance.

 

same thing happening to me today... is this normal?

 

No , it isn't . Can you provide us with more info about is this permanently happening ot just once , when ... and things like that , possible screenshot

 

As a new NOD user, I have to wonder if it really matters, as long as Nod does its job if it has to.

 

it doesn't happen all the time... I'm not sure if it happened before today but today it updated to ver. 1.1784 about 4 times...

 

I am having the same problem. It is October 1, and the thing has been "updated" to the latest definitions 41 times since September 29. Each time it is the same 1.1784 update dated 9/29/06. I've tried switching update servers and it still doesn't change anything.

Edit: It almost seems to happen every hour.

http://img359.imageshack.us/img359/720/nodupdateov9.th.jpg

 

Can you both contact the Tech Support for more help
Web form Email (support@eset.com) ESET global

 

Happen again:

Time Module Event User
10/4/2006 10:30:39 AM Kernel The virus signature database has been successfully updated to version 1.1788 (20061003).
10/3/2006 23:09:30 PM Update Error connecting to server u4.eset.com.
10/3/2006 22:09:14 PM Kernel The virus signature database has been successfully updated to version 1.1787 (20061002).
10/3/2006 21:09:23 PM Kernel The virus signature database has been successfully updated to version 1.1787 (20061002).
10/3/2006 18:53:51 PM Kernel The virus signature database has been successfully updated to version 1.1787 (20061002).


My auto update setup is set to download update from u7.eset.com.

I tried manual update and set the update server to u7.eset.com, although my Nod is already up to date, but when I click "Update now", sometimes, not all the time, Nod download something from the server and seem update again and popup Nod is update to ..., so I think maybe it is the u7.eset.com server problem.

 

My auto update setup is set to download update from u7.eset.com, because when select Choose automatically, sometimes got "Update Error connecting to server u4.eset.com. " With repeat update problem now is set to Choose automatically. And I'm using trial version.

 

the update error messages are not a problem - you just ignore them! The safest setting is <Choose Automatically> as this is designed to move onto another server in the event of a failure - and failures are to be expected... that's why the system moves onto another server!

 

But what if each server they connect to also fails? Today so far I've had "Error connecting to server u8a.eset.com and u3.eset.com and u2.eset.com and u4.eset.com and www.eset.sk and www.nod32.com. And I do have the setting at "Choose automatically".

 

Do they *all* happen within a few seconds of each other? If so, it sounds like there is some sort of problem with the internet connection. For example, maybe you have a router that must reestablish a DSL connection if you have been offline for a while, or maybe your computer has a wireless connection that has not finished connecting to its router/access point.

Could either one of these apply to you?

 

Time Module Event User

10/9/2006 21:50:15 PM Update Error connecting to server u7.eset.com.
10/9/2006 21:50:11 PM Update Error connecting to server u8a.eset.com.
10/9/2006 21:50:05 PM Update Error connecting to server u3.eset.com.
10/9/2006 21:49:57 PM Update Error connecting to server u2.eset.com.
10/9/2006 21:49:54 PM Update Error connecting to server u4.eset.com.
10/9/2006 14:55:55 PM Update Update attempt failed (Server connection failure)
10/9/2006 14:53:55 PM Update Error connecting to server u8a.eset.com.
10/9/2006 14:36:30 PM Update Error connecting to server www.eset.sk.
10/9/2006 14:36:12 PM Update Error connecting to server www.nod32.com.

I'm on a laptop that doesn't have wireless capability, am connected directly via cable to the internet, with the Vonage Linksys RPT300 in between the cable and the computer. Just tried to update SAS and NOD - SAS updated, NOD is still saying that my 10-06-06 version is up-to-date.

Just to add: on Comodo "ps_upd.dll" (reading as the NOD32 Update Module) is allowed.

 

The Eset update server proble mis not just discussed here, it is discussed in many forums I seen. Why just assume the user connection has problem? could the users around thw world have internet connection problem too?

 

BerserkerPup,

Can you please visit http://spiderweb.com.au/cgi-bin/proxytest and http://www.lagado.com/proxy-test then post back with the responses (eg. 'NO PROXY' or 'The proxy server has announced itself as') - just to rule out a proxy as one possible cause.

Thinking out loud, I'm wondering why you have not just permitted NOD32 in general instead of 'ps_upd.dll' as you say...

Cheers

 

ps_upd.dll has nothing to do with updates, it's the updater dll itself. The module that downloads updates is the kernel service nod32krn.exe

 

Thanks to all of you for the help so far.

I did both tests and they both showed "no proxy".

Comodo is in the learning mode and it hasn't popped up any messages about allowing NOD32. There are only entries about NOD32 in the "Component Monitor" section which seems to contain just .dll's.

This morning, after I started the computer, the following was in the log:

Time Module Event User
10/10/2006 10:39:49 AM Kernel The virus signature database has been successfully updated to version 1.1796 (20061010).
10/10/2006 10:38:44 AM Update Error connecting to server u8.eset.com.
10/10/2006 2:28:54 AM Update Update attempt failed (Server connection failure)

So it has managed to update itself somehow, though how it did so if it needed the NOD32krn.exe service authorized to get through the FW I don't know.

I just went into Comodo's "Application Monitor" and added "nod32krn.exe" as an allowed appliction, allowing TCP/UDP both in/out. Hope that's correct, since I'm learning as I go about this stuff. I formerly had EZ Armor running but like the NOD/Comodo combo better - loads faster and seems to use less resources on this computer.

 

The first in 2:28 means that NOD32 tried to connect to a server which was down so it was impossible to establish a connection with it.Nothing to worry about . The second in 10:38 means that NOD32 tried to connect to server u8 which was very busy at that particular moment and 20 seconds later NOD32 tried to update from another not-busy server and in 10:39 successful update was established . You are well-protected from all the latest threats

Yes , it is correct . You are fine

 

Mabye.But this is not an answer to the thread main question !

 

Usually use of Registry cleaners has been found to be the culprit.

Cheers

 

Right! The main question is Eset's update server problem.

Time Module Event User
10/10/2006 16:02:28 PM Kernel The virus signature database has been successfully updated to version 1.1796 (20061010).
10/10/2006 12:02:57 PM Update Update attempt failed (Server connection failure)
10/10/2006 12:02:28 PM Update Error connecting to server u8.eset.com.
10/10/2006 12:02:05 PM Update Error connecting to server u2.eset.com.
10/10/2006 12:02:03 PM Update Error connecting to server u7.eset.com.
10/10/2006 12:02:03 PM Update Error connecting to server u3.eset.com.
10/9/2006 20:15:22 PM Update Error connecting to server u8.eset.com.
10/9/2006 19:23:05 PM Kernel The virus signature database has been successfully updated to version 1.1795 (20061009).
10/9/2006 19:15:05 PM Update Error connecting to server u8.eset.com.
10/9/2006 9:31:55 AM Update Error connecting to server 82.165.250.33.

I use only Windows Firewall, no application control what ever, and if my router has problem or I has connection problem to Internet do you guys think I can still post here?

Busy server is good thing, that could mean more users use Nod32, more business, more profits; or the server capacity is not enough. I see update server connection error in other AV too, e.g. Antivir, Kav.

 

Today, it happened to me for the first time on update 1.1796. I haven't touched the registry. (My update interval is set to 3 hours.)

Time Module Event User
10/10/2006 17:09:21 PM Kernel The virus signature database has been successfully updated to version 1.1797 (20061010).
10/10/2006 14:09:02 PM Kernel The virus signature database has been successfully updated to version 1.1796 (20061010).
10/10/2006 11:08:54 AM Kernel The virus signature database has been successfully updated to version 1.1796 (20061010).
10/10/2006 8:08:23 AM Update Update attempt failed (Server connection failure)
10/9/2006 14:31:37 PM Kernel The virus signature database has been successfully updated to version 1.1795 (20061009).

 

I usually use three different reg cleaners and never had such problems.
So it could be something else.

 

So long as I see a notification bubble on average once a day I am happy. I never ever go looking in the logs, too much looking will make you go blind, like staring at the sun

Cheers