NOD updated to same version twice!

Anyone else seen this?

 

Found the same here.

Cheers

 

I'll cancel the appointment at the opticians then! Thanks

 

LOL, no worries

 

I think it might have something to do with the Advanced Heuristic engine update (look in the system information, it should be dated 02/06/05)

 

I wish I had such a clean log file. I see loads of failed servers at the Eset side...

 

There haven't been any problems with update servers on our side. The errors in your log must have occured due to no Internet connectivity or glitches at your ISP.

 

Only Twice? Nod has updated to 1.993 (20050207) 5 times on my machine Like Edwin024, I'm seeing a lot of failed connections in my logs Boclean isn't having any trouble updating

 

Something is wrong here. If I click on "update now" Nod will update again to the same version, Instead of saying.."nod is up to date" Anyone know whats going on here? It's already did 6 updates now All done by clicking "update now"

Automatic update just did another update while ago. To the same version. I'm having a lot of "server update failures" also. I've been trialing nod about 5 days.

Hope this matter can be straightened out. One more question. Is it harmful to put that many updates into the same update?

 

You're lucky!

I'm doing a trial of NOD32 and I'm not impressed so far. I noticed a lot of WAN activity today so I figured I'd do a manual update and scan. NOD errored on the connection and asked for an username and password! I had a look at the update log and found that there were several days of errors on the updates. There was no warning.

With 23 days of trial left, I can't get updates! I next un-installed NOD and re-installed it. Now I can get updates, which I do. I do a full scan next, and it finds a trojan.... there's the cause of my WAN activity. Things seem cool now, but every hour I get a popup that says I've been updated to the same version!

Here is my update log since my install:

Time Module Event User
2/8/2005 0:36:04 AM Kernel The virus signature database has been updated successfully to version 1.993 (20050207).
2/7/2005 23:36:04 PM Kernel The virus signature database has been updated successfully to version 1.993 (20050207).
2/7/2005 22:36:04 PM Kernel The virus signature database has been updated successfully to version 1.993 (20050207).
2/7/2005 21:36:05 PM Kernel The virus signature database has been updated successfully to version 1.993 (20050207).
2/7/2005 20:36:22 PM Kernel The virus signature database has been updated successfully to version 1.993 (20050207).
2/7/2005 19:53:56 PM NOD32 An infiltration has been detected. See the on-demand scanner Log for details. T\me
2/7/2005 19:37:16 PM Kernel The virus signature database has been updated successfully to version 1.993 (20050207).
2/7/2005 19:37:06 PM Kernel The virus signature database has been updated successfully to version 1.993 (20050207).
2/7/2005 19:36:50 PM Kernel The virus signature database has been updated successfully to version 1.993 (20050207).
2/7/2005 19:36:19 PM Update Update attempt failed (Server connection failure)
2/7/2005 19:29:00 PM Update Error connecting to server u4.eset.com.
2/7/2005 19:28:37 PM Update Error connecting to server u3.eset.com.
2/7/2005 19:28:14 PM Update Error connecting to server u5.eset.com.
2/7/2005 19:27:53 PM Update Error connecting to server u1a.eset.com.
2/7/2005 19:11:39 PM NOD32 An infiltration has been detected. See the on-demand scanner Log for details. NT AUTHORITY\SYSTEM
2/7/2005 18:57:17 PM Update Function: DownloadAuthorization, parameters: , return value: 401 T\me
2/7/2005 18:57:17 PM Update Update attempt failed (Incorrect username or password.) T\me
2/7/2005 18:44:02 PM Update Function: DownloadAuthorization, parameters: , return value: 401 T\me
2/7/2005 18:44:02 PM Update Update attempt failed (Incorrect username or password.) T\me
2/7/2005 18:39:05 PM Update Function: DownloadAuthorization, parameters: , return value: 401 T\me
2/7/2005 18:39:05 PM Update Update attempt failed (Incorrect username or password.) T\me
2/7/2005 18:38:10 PM Update Function: DownloadAuthorization, parameters: , return value: 401 T\me
2/7/2005 18:38:10 PM Update Update attempt failed (Incorrect username or password.) T\me
2/7/2005 18:38:07 PM Update Function: DownloadAuthorization, parameters: , return value: 401 T\me
2/7/2005 18:38:07 PM Update Update attempt failed (Incorrect username or password.) T\me
2/7/2005 18:35:21 PM Update Function: DownloadAuthorization, parameters: , return value: 401 T\me
2/7/2005 18:35:21 PM Update Update attempt failed (Incorrect username or password.) T\me
2/7/2005 18:28:49 PM Update Function: DownloadAuthorization, parameters: , return value: 401 T\me
2/7/2005 18:28:49 PM Update Update attempt failed (Incorrect username or password.) T\me
2/7/2005 18:27:50 PM Update Function: DownloadAuthorization, parameters: , return value: 401 T\me
2/7/2005 18:27:50 PM Update Update attempt failed (Incorrect username or password.) T\me
2/7/2005 18:27:23 PM Update Function: DownloadAuthorization, parameters: , return value: 401
2/7/2005 18:27:23 PM Update Update attempt failed (Incorrect username or password.)
2/7/2005 17:32:08 PM Update Function: DownloadAuthorization, parameters: , return value: 401
2/7/2005 17:32:08 PM Update Update attempt failed (Incorrect username or password.)
2/7/2005 16:32:09 PM Update Function: DownloadAuthorization, parameters: , return value: 401
2/7/2005 16:32:09 PM Update Update attempt failed (Incorrect username or password.)
2/7/2005 15:32:20 PM Update Function: DownloadAuthorization, parameters: , return value: 401
2/7/2005 15:32:20 PM Update Update attempt failed (Incorrect username or password.)
2/7/2005 15:27:16 PM Update Error connecting to server u1.eset.com.
2/7/2005 15:27:12 PM Update Error connecting to server u3.eset.com.
2/7/2005 15:27:08 PM Update Error connecting to server u1a.eset.com.
2/7/2005 15:27:08 PM Update Error connecting to server u4.eset.com.
2/7/2005 5:07:22 AM Update Error connecting to server u3.eset.com.
2/4/2005 12:01:56 PM Update Error connecting to server u1a.eset.com.
2/4/2005 10:57:06 AM Update Error connecting to server u1a.eset.com.
2/3/2005 14:19:01 PM NOD32 An infiltration has been detected. See the on-demand scanner Log for details. NT AUTHORITY\SYSTEM
2/2/2005 15:44:05 PM Kernel The virus signature database has been updated successfully to version 1.990 (20050202).
1/31/2005 18:13:00 PM Kernel The virus signature database has been updated successfully to version 1.989 (20050131).
1/31/2005 12:16:29 PM Kernel The virus signature database has been updated successfully to version 1.988 (20050131).

 

You found a trojan? I'm gonna disable nod for now, and do a scan with bitdefender free. See if it comes up with anything.

 

I did a scan with nod, and scanned with bitdefender free. My system comes up clean. no infections.

 

Eset seems to like to stick their heads in the ground when it come to server problems... More people have the same problems that I see with their servers and than the answer of Marcos is a laugh

 

Please note that I posted the submission yestreday before I went to bed :-] There's actually an issue with one of the servers which might be causing that. We're looking into it, don't worry.

 

Thanks for the info Marcos. I will rest a little easier now