NOD Updates

When the computer has been idle for a day and NOD does the update why does it not update all the released updates for the past day? Seems to only update the first version and then you have to manualy update for the most recent version.

 

Hi Motherroad, welcome to WIlders.

NOD32 will grab all available updates when it connects, even though you are only seeing the latest update number. Nothing to worry about, it does not skip anything just because it was not online for a few days or weeks.

Cheers

 

Thanks for the reply but as I said NOD updated the first database ok and I had to manually update 2 times to bring it to the current database. It seems it should have updated all 3 released databases.

 

Is this just the once, or ongoing? If ongoing, I would check your connection settings in NOD32, and failing this, an uninstall and reinstall.

Cheers

 

I just noticed it today. I am on dialup connection and set automatic updates. Will keep a eye on it for the next few days and see what happens. Thanks for the help.

 

After going online today NOD did not update to the latest database so checked the settings and tried manually and it said no update needed. Then I switched from automatic to Eset4 and it updated so seems like a problem with the servers.

 

Do you have a Trial version or a Paid version?

Cheers

 

Paid version

 

Do you actually have the "Automatic update after dial-up connection" task scheduled?

 

This is an ongoing issue.
I have had the exact problem stated by Motherroad.
My wifes PC which is on most of the time usually stays up-todate.
But my PC which I fire up when I get home from work has the issue stated.
If there are, say, 3 updates it will get the first 1 and then I have to manually update to the latest.
Manual update does not always work (you are already up todate)
I have gotten used to checking daily at http://www.nod32-av.com/

 

No trying to hog this thread but here is a partial log.
Time Module Event User
24/08/2006 18:45:48 Kernel The virus signature database has been successfully updated to version 1.1723 (20060824).
24/08/2006 18:45:38 Update Error connecting to server u7.eset.com.
24/08/2006 18:45:37 Update Error connecting to server u2.eset.com.
24/08/2006 18:45:35 Update Error connecting to server u3.eset.com.
24/08/2006 18:45:33 Update Error connecting to server u4.eset.com.
24/08/2006 18:45:32 Update Error connecting to server u8.eset.com.
24/08/2006 18:45:32 Update Error connecting to server 82.165.250.33.
24/08/2006 17:44:42 Update Update attempt failed (Server connection failure) DAVID\DavidC
24/08/2006 17:44:06 Kernel Statistical information has been sent to Eset.
24/08/2006 16:43:42 Update Update attempt failed (Server connection failure)
24/08/2006 15:42:50 Update Error connecting to server u3.eset.com.
24/08/2006 15:42:49 Update Error connecting to server u4.eset.com.
24/08/2006 15:42:47 Update Error connecting to server u8.eset.com.
24/08/2006 15:42:45 Update Error connecting to server u2.eset.com.
24/08/2006 15:42:45 Update Error connecting to server 82.165.250.33.
24/08/2006 09:46:21 Kernel The virus signature database has been successfully updated to version 1.1723 (20060824).

As you can see the 1.1723 was successfully updated twice

 

Yes. NOD is set up to update on connection.

 

I have been having the same problem, on and off, for several weeks now (although the past few days have been fine). I posted on here and was told that Eset are aware of the problem and are working on a solution, so I haven't said anything more about it, in case I got accused of trolling.

Regards
Suggers

 

And they are still aware, and still working diligently on the issue; it will be resolved...

Very few people are accused of trolling, and it is only said when it is valid.

If you ever have an issue, speak up loud and clear we'll listen and do our utmost to resolve the issue...

Cheers

 

Just for the record, I have the same problem being on dialup also, do hope they resolve this quickly.

Marc

 

I reset the updates from automatic to Eset4 and I am getting the updates ok now. I will leave it this way untill I hear that the update issue is corrected.