What is wrong with Nod32 updater?

The other day when people were having problem with update 1.1087, I posted that "My experience was a bit different. I got the 1.1147 update three (3) times (at 5:01:37 a.m., 17:01:42, 18:01:39) and then finally the 1.1150 update at 19:07:37 U.S. time."
Today, which is June 24th here in US, I just got an automatic update, but it was for v. 1.1152 which was the update for yesterday, June 23rd. According to my event log - The virus signature database has been successfully updated to v. 1.1152 (20050623). Same update as yesterday.

 

I just got the 1.1153 here

 

Hi
Tried manual update(10 min ago), all I get is same def repeated
Time Module Event User
24.6.2005 23:24:32 Kernel The virus signature database has been successfully updated to version 1.1152 (20050623).
24.6.2005 23:09:26 Update Update attempt failed (Server connection failure)
24.6.2005 23:08:07 Update Error connecting to server 213.215.116.226.
24.6.2005 13:48:59 Update Error connecting to server u3.eset.com.
23.6.2005 22:00:57 Kernel The virus signature database has been successfully updated to version 1.1152 (20050623).
23.6.2005 21:57:59 Update Update attempt failed (Server connection failure)

 

I just got 1.1152 a second time as well. I then ran a manual update and received 1.1153 successfully. This is not the first time it has happened, I have no idea why NOD sometimes does this, its rare but still annoying.

 

<Mine has gone crazy 4*1.1152

Time Module Event User
24.6.2005 23:38:56 Kernel The virus signature database has been successfully updated to version 1.1152 (20050623).
24.6.2005 23:38:46 Update Error connecting to server u4.eset.com.
24.6.2005 23:38:25 Update Error connecting to server 213.215.116.226.
24.6.2005 23:36:55 Kernel The virus signature database has been successfully updated to version 1.1152 (20050623).
24.6.2005 23:36:49 Update Error connecting to server u4.eset.com.
24.6.2005 23:24:32 Kernel The virus signature database has been successfully updated to version 1.1152 (20050623).
24.6.2005 23:09:26 Update Update attempt failed (Server connection failure)
24.6.2005 23:08:07 Update Error connecting to server 213.215.116.226.
24.6.2005 13:48:59 Update Error connecting to server u3.eset.com.
23.6.2005 22:00:57 Kernel The virus signature database has been successfully updated to version 1.1152 (20050623).
23.6.2005 21:57:59 Update Update attempt failed (Server connection failure)

 

I just got the 1.1153 update from an auto dwl.

 

Maybe this came from the archive module which was updated in date of 2005/06/23 (v1.032)
In 2 computers that I just start to check this, they first download the v1.1152 and then the v.1153 (they was not updated since 2 days- they were offline)

 

crazy enough 9*1.1152

This trigger a crazy question in my head. my stupid and crazy question is:
Does updates depend on the geographical area.

 

Didn't know what to do.I'm shutting down
NOD Has gone beyond control. over 25*1.1152

 

The servers are the same for everybody, not depending of your area.

 

No problems here!!

Time Module Event User
24/06/2005 16:33:57 PM Kernel The virus signature database has been successfully updated to version 1.1153 (20050624).
23/06/2005 17:33:49 PM Kernel The virus signature database has been successfully updated to version 1.1152 (20050623).
22/06/2005 16:06:10 PM Kernel The virus signature database has been successfully updated to version 1.1151 (20050622).
22/06/2005 15:11:21 PM Kernel The virus signature database has been successfully updated to version 1.1150 (20050621).


Cheers,

 

Except those who use warez servers Also, large corporate networks usually use a mirror for central updating.

 

Of course Marcos, I only mean Eset servers
And even some small company use mirrors

 

I have also been having intermittent problems today with the NOD32 updater. I've also been having trouble with the Microsoft Antispyware Updater, but I do not think the problems are related. Microsoft Antispyware came out with a new build yesterday. The latest definition patterns are 5727. Clicking Help-About shows that 5727 is installed. If I update MSAS by choosing File - Update, it tries to update from 5725 to 5727, like it's trying to install 5727 again. It never used to do that before I installed the new version today.

 

At 2/24/2005 -16:03:00 I received update 1.1152 (same as yesterday). At 2/24/2005 - 17:03:59 I received the correct update l.1153. And I am not using warez Marcos.

 

Time Module Event User
6/24/2005 17:03:59 PM Kernel The virus signature database has been successfully updated to version 1.1153 (20050624).
6/24/2005 16:05:11 PM Kernel The virus signature database has been successfully updated to version 1.1152 (20050623).
6/24/2005 16:03:00 PM Kernel The virus signature database has been successfully updated to version 1.1152 (20050623).
6/23/2005 14:03:08 PM Kernel The virus signature database has been successfully updated to version 1.1152 (20050623).

(It is now 12:38 a.m. on June 25 and the Eset web site still lists the latest update definitions as 1.1152 - June 23 rd. Strange way to run a business).

 

This morning only got the update 1.1153 (all the night b4 was repeated 1.1152)
http://img139.echo.cx/img139/5802/updatet9yq.th.jpg
I'm using trial version
http://img139.echo.cx/img139/9121/update6ec.th.jpg

 

Hmm... i just noticed in my logs, 1.1152 is showing up multipule times also before getting 1.1153.


snowbound

 

Here it shows that the current version is 1.1152
http://www.nod32.com/home/home.htm
strange! the page hasn't been updated yet

 

Hadi,

different Eset/distributor sites update at different times - I don't know who/when they get updated, but being a reseller, we grab that information just as fast as we can find it - an publish it on our site here:

http://www.nod32usa.com/nod32-updates/

When NOD32.COM doesn't update, either:

nod32.sk or nod.it or nod32.ch will have the most recent information

hth

Greg