Update Errors

[DVD+R]

why does this NOD32 frequently have in the update logs "failure to connect to server, one time it did this more than 7 times in a row,and its bloody annoying!>:( oh! and I have an always on ADSL connection, just incase someone asks

[Brian N]

If you recieve the updates you shouldn't put too much attention into the connection errors.

[YeOldeStonecat]

It goes down a list of servers to try..until it finds one with a lighter load..then proceeds to update. Some servers may be busy at times..that's why it has a long list to choose from. The thing to focus on..is that it does update frequently, and ultimately does get the updates.

[marcromero]

DVD+R, I know what you mean, being on dialup myself, my event log is nothing but red with errors connecting with the ocassional non-red signature update and statistical update. Alot of times after my dialup connection has been established and it tries to update, it gets an error connecting and I don't get an update unless I do it manually, so I cannot depend on it to keep me automatically updated on dialup. I put up with the aggravation for the protection, but I sure wish it worked like it was suppose too. NOD's update feature is the weakest part of their software in my opinion, and the only problem I have so far using this antivirus. It is very annoying...

Marc

[webyourbusiness]

several servers on the blink at the moment - don't worry about them though, Eset working on update servers and future releases of the software will update the list of servers if/when required.

[jayt]

Here are my logs from the last 3 days. I am using DSL connection, always on, and update is set to automatic.

Time Module Event User
8/27/2006 11:09:12 AM Update Error connecting to server u8.eset.com.
8/27/2006 10:09:13 AM Update Error connecting to server u8.eset.com.
8/26/2006 23:08:12 PM Update Error connecting to server u8.eset.com.
8/26/2006 22:08:12 PM Update Error connecting to server u8.eset.com.
8/26/2006 21:08:12 PM Update Error connecting to server u2.eset.com.
8/26/2006 16:08:22 PM Kernel The virus signature database has been successfully updated to version 1.1727 (20060826).
8/26/2006 16:08:12 PM Update Error connecting to server u8.eset.com.
8/26/2006 15:08:12 PM Update Error connecting to server u8.eset.com.
8/26/2006 11:08:02 AM Update Function: gethostbyname, parameters: , return value: 11001
8/26/2006 11:08:02 AM Update Update attempt failed (Server connection failure.)
8/26/2006 11:08:00 AM Update Error connecting to server www.nod32.com.
8/26/2006 11:07:56 AM Update Error connecting to server u7.eset.com.
8/26/2006 11:07:53 AM Update Error connecting to server u8.eset.com.
8/26/2006 11:07:49 AM Update Error connecting to server u2.eset.com.
8/26/2006 11:07:45 AM Update Error connecting to server u4.eset.com.
8/26/2006 11:07:41 AM Update Error connecting to server u3.eset.com.
8/26/2006 11:07:39 AM Update Error connecting to server 82.165.250.33.
8/26/2006 10:08:02 AM Update Function: gethostbyname, parameters: , return value: 11001
8/26/2006 10:08:02 AM Update Update attempt failed (Server connection failure.)
8/26/2006 10:08:00 AM Update Error connecting to server www.nod32.com.
8/26/2006 10:07:56 AM Update Error connecting to server u7.eset.com.
8/26/2006 10:07:53 AM Update Error connecting to server u4.eset.com.
8/26/2006 10:07:49 AM Update Error connecting to server u2.eset.com.
8/26/2006 10:07:45 AM Update Error connecting to server u3.eset.com.
8/26/2006 10:07:41 AM Update Error connecting to server 82.165.250.33.
8/26/2006 10:07:41 AM Update Error connecting to server u8.eset.com.
8/26/2006 9:08:02 AM Update Function: gethostbyname, parameters: , return value: 11001
8/26/2006 9:08:02 AM Update Update attempt failed (Server connection failure.)
8/26/2006 9:08:00 AM Update Error connecting to server www.nod32.com.
8/26/2006 9:07:56 AM Update Error connecting to server u7.eset.com.
8/26/2006 9:07:53 AM Update Error connecting to server 82.165.250.33.
8/26/2006 9:07:51 AM Update Error connecting to server u4.eset.com.
8/26/2006 9:07:47 AM Update Error connecting to server u3.eset.com.
8/26/2006 9:07:43 AM Update Error connecting to server u2.eset.com.
8/26/2006 9:07:41 AM Update Error connecting to server u8.eset.com.
8/26/2006 3:08:00 AM Update Error connecting to server u8.eset.com.
8/26/2006 2:08:00 AM Update Error connecting to server u8.eset.com.
8/25/2006 20:08:00 PM Update Error connecting to server u8.eset.com.
8/25/2006 19:08:00 PM Update Error connecting to server u8.eset.com.
8/25/2006 14:08:00 PM Update Error connecting to server 82.165.250.33.
8/25/2006 8:08:00 AM Update Error connecting to server 82.165.250.33.

[ASpace]

It appears that currently ESET have issues with servers

u8.eset.com
82.165.250.33

Unfortunately I also have errors with them (hope they fix it soon :) )


Errors from other servers (u3 , u7....) are because they were really busy and soon redirected you to another server.

[webyourbusiness]

8/26/2006 9:08:02 AM Update Function: gethostbyname, parameters: , return value: 11001

This means the server can not be resolved - it's a DNS lookup failure and happens if the ISP is down, or you're not connected to the internet.

If you get a PORT failure, this is an LSP fix required.

As HiTech_boy pointed out, u8 and 82.165.250.33 are currently down, and they error for everyone, so ignore those.

If you have PERSISTENT update failures, try two things:

1. repair connection from with NOD32 - reboot - try again
2. get lspfix - run that - reboot - try again.

If all those things work and you get errors still - post the logfile here for comment from one of us and/or Eset support.

[webyourbusiness]

one thing I forgot - I've used the symantec removal tool to remove various forms of Norton in the last week TWICE - and both times it messed up the LSP so that lspfix needed to be run - not a guarantee that you will need to do the same, but I've now changed our standard installation instructions (in-house version), to include running this tool immediately after the removal of any Symantec software... and we use the tool for removal as it's a lot easier than add/remove programs (or takes a less time and only one reboot)


Norton removal tool:

ftp://ftp.symantec.com/public/english_us_canada/linked_files/tsgen/SymNRT.exe


LSPFix: http://cexx.org/lspfix.htm

[jayt]

-{ Quote: "As HiTech_boy pointed out, u8 and 82.165.250.33 are currently down, and they error for everyone, so ignore those." }-

-{ Quote: "8/26/2006 9:08:02 AM Update Function: gethostbyname, parameters: , return value: 11001

This means the server can not be resolved - it's a DNS lookup failure and happens if the ISP is down, or you're not connected to the internet.
" }-

Ok, I can buy these things, but if you look at my logs there was a failure to connect of servers 2,3,4, and 7 as well.

[ASpace]

-{ Quote: "Ok, I can buy these things, but if you look at my logs there was a failure to connect of servers 2,3,4, and 7 as well." }-


Don't worry , see my log
Time Module Event User
27.8.2006 22:56:20 Update Error connecting to server u4.eset.com.
27.8.2006 22:56:19 Update Error connecting to server u3.eset.com.
27.8.2006 22:56:14 Update Error connecting to server u7.eset.com.
Made especially for you , nothing to worry about . The onliest <problematic> are u8 and the other(82.165.250.33 ) but others works very well ! :thumb:

[GWA]

-{ Quote: "DVD+R, I know what you mean, being on dialup myself, my event log is nothing but red with errors connecting with the ocassional non-red signature update and statistical update. Alot of times after my dialup connection has been established and it tries to update, it gets an error connecting and I don't get an update unless I do it manually, so I cannot depend on it to keep me automatically updated on dialup. I put up with the aggravation for the protection, but I sure wish it worked like it was suppose too. NOD's update feature is the weakest part of their software in my opinion, and the only problem I have so far using this antivirus. It is very annoying...

Marc" }-

Marc: I have the same issue. Sometimes a manual update is the only way when NOD "gives up." It seems to go through periods where there is no trouble, then suddenly a day or two when it is quite exasperating. Oh well, NOD32 is the best, so I guess that is just the way it will be...(!) I'm not sure that I agree about the update feature being the weakest part though, since I love the fact that updates can be set for "upon connection to the internet." I wish more software had this option instead of only allowing a check at a certain time of the day - which means nothing to a dial-up user. CHUCK

[Brian N]

PLEASE read other responses, all this crap about updates failing will never happen, UNLESS your off the internet.

[DVD+R]

Ok relax Brian, we are just a few users who are concerned about the update status, take a seat and have a coke and a smile dude;D

[Brian N]

-{ Quote: "Ok relax Brian, we are just a few users who are concerned about the update status, take a seat and have a coke and a smile dude;D" }-
But it's true ;)

[vidmar]

I have NOD32 running on a few servers and multiple times a day I will get “Server connection failure” update error messages from each server resulting a quite a few emails. This even happens occasionally when I try an “Update now” update from the control center. I’ve set the “Server” to <Choose automatically> and I know my username and password are correct.

Is it possible that the pre-defined servers in the server list are down that often??? If so can I purge the “bad” servers from that list? Are there new ones I can add that are more reliable?

Here are the ones in the drop down list ATM:
u2.eset.com
u3.eset.com
u4.eset.com
82.165.250.33
u7.eset.com
u8.eset.com

TIA.

[NOD32 user]

-{ Quote: "...Is it possible that the pre-defined servers in the server list are down that often??? If so can I purge the “bad” servers from that list? Are there new ones I can add that are more reliable? ..." }-The list of update servers is kept current automatically with each succesfull update from ESET.

It is normal to have some entries anyway as the update servers deflect or for load balancing etc. or as different parts of the internet do their thing, which is something outside any of our control.

But the important things are that you do get the updates when they're available and that you are able to diagnose a problem if there is one.

Cheers :)

[wilco]

-{ Quote: "
But the important things are that you do get the updates when they're available and that you are able to diagnose a problem if there is one." }-

I am not sure that you actually do. The 1.1731 update has been available for over 12 hours and in that time two NOD workstations here have reported a total of six "error connecting to server ..." messages, and still not received the update. The offending server is usually u8.eset.com, but u8a.eset.com is also mentioned.

I am none the wiser with regard to further diagnosing this problem. Is it fair to say that eset are having server problems?

thanks :(

PS in fact update 1.1732 is now published (but not received).

[marcromero]

Eset is having server problems, I have been having update problems since I purchased this software in June, I got so aggravated the other day, I uninstalled it, tonight I re-installed it and have just decided to disable automatic updates and update manually. This seems to work for the time being. I'm still not happy about this setup.

[NOD32 user]

-{ Quote: "...Is it fair to say that ESET are having server problems?..." }-I am aware that there was some issues with maybe a couple of the update servers but this should not prevent updates altogether.
I have attached a sample from my logs from June as possible one of the worst example I have to give. Notice that the update was still received automatically even in the midst of all the connection errors.

Also remember that there are many many things that can have influence on the internet which include just for two examples - your service provider or even their service providers, or either transparent proxy servers or proxy servers in general if they have a cache function.
It is best to configure NOD32 to connect directly when at all possible but this still wouldn't resolve an issue if it were related to transparent proxies. Does anybody know how to tell if there's one of these between them and the host? And in any case this is just one possibility.

I have previously heard on the grapevine that ESET have been preparing many new update servers for use but even then I would still personally consider it very normal to have connection errors in the logs.

Cheers :)

[wilco]

Further to my earlier posting, I find that about 3 hours ago one machine updated from 1.1730 to 1.1731, despite the fact that 1.1732 had been available most of the day (and possibly also 1.1733).

Another machine here updated half an hour ago directly from 1.1730 to 1.1733.

Go figure ??? I understood that update would always grab the latest version available - in the case of the first machine above, this clearly did not happen.

(BTW, I am not so much concerned by the server errors per se, but the timeliness of the updates.)

[webyourbusiness]

wilco - are you running a trial or the full version?

[wilco]

-{ Quote: "wilco - are you running a trial or the full version?" }-

Trial, pending purchase. Does this make a difference to the update process? It seems that I'm not alone with regard to the server errors, registered or otherwise.

thanks :)

NOD32 2.51.30 actually.

[ASpace]

-{ Quote: "Trial, pending purchase. Does this make a difference to the update process? " }-

Trial versions have much lower priority than paid users .
That's why you not always have the really latest definitions .

[webyourbusiness]

as HiTech_boy said, the trial version updates are a little different - trials update from a different set of servers, which are known to lag behind the "live" servers - or those used by paid users. Whether you agree with this procedure or not, that's the way it works, and it means that a trial user it's perfectly "normal" to be a version or 2 behind the most up-to-date version of the update signatures.

Sorry - that's just how it it (for the moment).

[marcromero]

Sorry HiTech_Boy and webyourbusiness, but I do not agree, I have had server update problems before and after I purchased Nod. I was told the same thing back then, during the trial period, the update priority is different, well, I'm two months into Nod and I see no difference, Nod still has server issues.

[Carver]

If you notice evertime there is a upate error it is the update server and everytime there is a successful virus signature update it is the kernal, the update servers just get overwhelmed. The problem is going to be taken care of in a couple of months llRC.

[marcromero]

-{ Quote: "If you notice evertime there is a upate error it is the update server and everytime there is a successful virus signature update it is the kernal, the update servers just get overwhelmed. The problem is going to be taken care of in a couple of months llRC." }-

I'm trying a work around HiTech_boy suggested, I think that just might work for the time being. Thanks.

[guilijan]

When will Eset give a solution to server errors?
There are two servers that always give error.

Update Error connecting to server 82.165.250.33.
Update Error connecting to server u8.eset.com.

Please don't answer
"If you recieve the updates you shouldn't put too much attention into the connection errors"

Eset must give a definitive solution to this servers.

[Brian N]

What kind of answer do you seek? ...

[guilijan]

Easy.
When will this problem will solved?

[Brian N]

Probably when they add new servers.
But if you recieve the updates you shouldn't ... oh nevermind.

[guilijan]

Don't you think that Eset are a big company and take a solution for this two servers aren't so difficult?

I don't understand why Eset don't give to it's users/costumers a definitive solution to this problems.

[NOD32 user]

-{ Quote: "Don't you think that Eset are a big company and take a solution for this two servers aren't so difficult?

I don't understand why Eset don't give to it's users/costumers a definitive solution to this problems." }-I don't see how this is an issue - regardless of any particular servers status, or for that matter the total number of servers when more are added, it is IMHO quite normal to see errors like those mentioned and would expect that regardless of what steps ESET takes (short of simply no longer mentioning them in logs when they occur) it will continue to be normal to see them - The name of the thecnology used regardless of the protocol or method is the imperfect Internet.

All that is necessary is that you actually get the updates. If you don't get the updates then have a look at the logs as they may be useful for discovering the reason. Otherwise ignore them since as long as you get updates they become irrelevant and in any case on a correctly set up enterprise installation 99% of machines don't even connect to ESET for updates so they won't show these messages anyway.

Surely that's enough said.

Cheers :)

[guilijan]

I think it's an answer conformist.
All must work in better form.Sorry I can't explain in english so if somebody can translate why I said.

Creo que Eset es una empresa de primer nivel en el area de Antivirus.
Creo que conformarse con que igual se obtienen los updates es una respuesta conformista. Si uno verifica el estado de los servers, casi siempre estan al 100% es decir segun entiendo, en el limite de su funcionalidad.
Es cierto que Nod32 es tambien un antivirus muy usado en forma irregular, sin licencia y quizas sean estos usuarios lo que ocupen ancho en los servers, quizas deba Eset crear la forma de que no pueda crackearse tan facilmente su antivirus, asi quienes pagamos la licencia no tendremos inconvenientes.
Tambien es cierto que no hay forma simple de verificar cuanto tiempo pasa desde que sale la actualizacion hasta que un usario puede actualizar su antivirus ya que las actualizaciones diarias no tienen horario. esto es una gran diferencia con Kav, donde figura la hora en que sale la actualizacion y nunca da problemas de server.
Como puedo yo saber si en el momento en que me dio un error de server, no hay una actualizacion disponible?
Espero se entienda y alguien pueda traducirlo al ingles.
A pesar de todo compre mi licencia el 23 de agosto y confio en Nod.

[DVD+R]

In short, If I pay $92.75 for a AntiVirus program, I expect it to Work FLAWLWSSLY! indeed this AntiVirus doesnt otherwise there wouldnt be such a forum,and so many errors mentioned in it from users never mind updates alone, Come On ! Eset! ~ off topic comment removed - Ron ~

[webyourbusiness]

you are incredible dvd+r - did you contact support directly - or the reseller you purchased from? The complexity of your PC setup or some other software interaction which hasn't been got to the bottom of, or even your ISP could be the cause. There are literally hundreds of thousands, possible many more - users who have NO PROBLEMS. I have installed literally thousands of systems where updates have NOT BEEN A PROBLEM.

Now I don't wish to diminish your problem here - it's obviously a problem that you and others are having, but your statements have descended into name-calling and insults, and you really need to calm down and take a chill pill.

I for one don't help people (my customers or otherwise), who have lowered the conversation into insults.

[DVD+R]

;D ;D but quite obviously there are problems with other people and updates, and frankly who's calling who? nobody was singlrd out here, and by the way any other AV I've used in the past has not had as many update erros as NOD32 has, and as I'm to believe this promise by Eset to fix the problem isnt a new one, its been ongoing for years

Incidently,webyourbusiness, to your opening statement to I'm incredible, yes I know, I'm told often this;D and like I said before, I pay for consistancy, NOT Errors when the price is what it is regardless of how many dont have problems, Lucky them. and owning a $6200 dollar computer, I want things to work! or I get rid, and replace

[avenger107]

-{ Quote: "In short, If I pay $92.75 for a AntiVirus program, I expect it to Work FLAWLWSSLY! indeed this AntiVirus doesnt otherwise there wouldnt be such a forum,and so many errors mentioned in it from users never mind updates alone, Come On ! Eset! ~ off topic comment removed - Ron ~" }-

In my opinion, the software IS working flawlessly when it tries another server after the first, or second, or third is not able to be the source for the update. The variability of the Internet is too great to expect any one server to be available all of the time, to all potential traffic. I am glad that NOD logs the fact and moves on.

I also view the existence of this forum as evidence of an active and supportive user community – something I look for in any software. The existence of this forum is in large part why I use NOD32 and recommend it to others.

[marcromero]

-{ Quote: "The variability of the Internet is too great to expect any one server to be available all of the time, to all potential traffic." }-

Variability of the internet, that's funny, it doesn't seem to affect other av update servers, like Antivir and DrWeb, only the Nod update servers.

[webyourbusiness]

cobblers - Eset just reports things how they are - unlike many other software vendors, who don't report things that MIGHT be considered a "failure" - such as a lack of connection or dns failure.

[NOD32 user]

-{ Quote: "In my opinion, the software IS working flawlessly when it tries another server after the first, or second, or third is not able to be the source for the update. The variability of the Internet is too great to expect any one server to be available all of the time, to all potential traffic. I am glad that NOD logs the fact and moves on.

I also view the existence of this forum as evidence of an active and supportive user community – something I look for in any software. The existence of this forum is in large part why I use NOD32 and recommend it to others." }-Hi avenger107 & welcome to Wilders,

That's pretty much how it is, or at least how I see it.-{ Quote: "Variability of the internet, that's funny, it doesn't seem to affect other av update servers, like Antivir and DrWeb, only the Nod update servers." }-If the servers were side by side and all vendors made the same mention of the same things then maybe they could be compared in this way, but even if this were the case there would still be other differences.

Cheers :)

[guilijan]

Hi guys sorry nobody can translate my previous post.
But guys, this is not normal for a great company.
I get the updates, but have more errors than updates.


Time Module Event User
02/09/2006 21:43:41 Update Error connecting to server 82.165.250.33.
02/09/2006 20:43:40 Update Error connecting to server 82.165.250.33.
02/09/2006 14:43:40 Update Error connecting to server 82.165.250.33.
02/09/2006 13:43:41 Update Error connecting to server 82.165.250.33.
02/09/2006 12:41:46 Kernel The virus signature database has been successfully updated to version 1.1736 (20060902).
02/09/2006 11:43:35 Update Error connecting to server u3.eset.com.
02/09/2006 09:43:42 Kernel Statistical information has been sent to Eset.
02/09/2006 00:38:11 Update Error connecting to server 82.165.250.33.
01/09/2006 18:38:12 Update Error connecting to server 82.165.250.33.
01/09/2006 17:38:11 Update Error connecting to server 82.165.250.33.
01/09/2006 16:40:11 Update Error connecting to server 82.165.250.33.
01/09/2006 16:38:11 Update Error connecting to server u8.eset.com.
01/09/2006 15:38:11 Update Error connecting to server u8.eset.com.
01/09/2006 15:30:18 Kernel The virus signature database has been successfully updated to version 1.1735 (20060901).
01/09/2006 15:30:11 Update Error connecting to server u8.eset.com.
01/09/2006 15:30:05 Update Error connecting to server 82.165.250.33.
01/09/2006 09:40:11 Update Error connecting to server 82.165.250.33.
01/09/2006 09:38:11 Update Error connecting to server u8.eset.com.
01/09/2006 08:38:11 Update Error connecting to server u8.eset.com.
31/08/2006 23:18:47 Update Error connecting to server u4.eset.com.
31/08/2006 13:17:01 Kernel The virus signature database has been successfully updated to version 1.1734 (20060831).
31/08/2006 06:16:56 Kernel The virus signature database has been successfully updated to version 1.1733 (20060831).
31/08/2006 05:18:46 Update Error connecting to server 82.165.250.33.
30/08/2006 14:19:00 Kernel The virus signature database has been successfully updated to version 1.1732 (20060830).
30/08/2006 14:18:46 Update Error connecting to server u8.eset.com.
30/08/2006 07:42:36 Update Error connecting to server u8.eset.com.
30/08/2006 07:40:36 Update Error connecting to server 82.165.250.33.
30/08/2006 06:42:41 Kernel The virus signature database has been successfully updated to version 1.1731 (20060830).
30/08/2006 06:42:31 Update Error connecting to server 82.165.250.33.
30/08/2006 06:40:31 Update Error connecting to server u8.eset.com.
29/08/2006 16:17:18 Kernel The virus signature database has been successfully updated to version 1.1730 (20060829).
29/08/2006 16:15:33 Update Error connecting to server u1a.eset.com.
29/08/2006 16:14:10 Update Function: gethostbyname, parameters: , return value: 11004
29/08/2006 16:14:10 Update Update attempt failed (Server connection failure.)
29/08/2006 16:14:08 Update Error connecting to server www.nod32.com.
29/08/2006 16:14:06 Update Error connecting to server u5.eset.com.
29/08/2006 16:14:04 Update Error connecting to server u4.eset.com.
29/08/2006 16:14:03 Update Error connecting to server u1a.eset.com.
29/08/2006 16:14:01 Update Error connecting to server u3.eset.com.
29/08/2006 16:14:01 Update Error connecting to server u7.eset.com.

[NOD32 user]

-{ Quote: "Hi guys sorry nobody can translate my previous post.
But guys, this is not normal for a great company.
I get the updates, but have more errors than updates.


Time Module Event User
02/09/2006 12:41:46 Kernel The virus signature database has been successfully updated to version 1.1736 (20060902).
02/09/2006 09:43:42 Kernel Statistical information has been sent to Eset.
01/09/2006 15:30:18 Kernel The virus signature database has been successfully updated to version 1.1735 (20060901).
31/08/2006 13:17:01 Kernel The virus signature database has been successfully updated to version 1.1734 (20060831).
31/08/2006 06:16:56 Kernel The virus signature database has been successfully updated to version 1.1733 (20060831).
30/08/2006 14:19:00 Kernel The virus signature database has been successfully updated to version 1.1732 (20060830).
30/08/2006 06:42:41 Kernel The virus signature database has been successfully updated to version 1.1731 (20060830).
29/08/2006 16:17:18 Kernel The virus signature database has been successfully updated to version 1.1730 (20060829).
" }-Your log looks perfectly normal to me since you actually get the updates.
When you are getting the updates then the rest means nothing.

Cheers :)

[guilijan]

Ok but since updates have "no time it was made by Eset" like Kav updates (The standard antivirus databases currently contain xxxxxxxrecords. The last update to the antivirus databases was released at 03 September 2006 at 01:50 (GMT +0400)., how can I know if when i have an error there is really an update available and I can't get it in that moment?

[mata7]

same here, i dont trust the auto update any more like every 3 hours i check for update manually

Time Module Event User
9/2/2006 20:44:57 PM Update Error connecting to server 82.165.250.33.
9/2/2006 19:44:58 PM Update Error connecting to server 82.165.250.33.
9/2/2006 15:44:55 PM Update Error connecting to server u3.eset.com.
9/2/2006 13:44:55 PM Update Error connecting to server 82.165.250.33.
9/2/2006 10:44:40 AM Kernel The virus signature database has been successfully updated to version 1.1736 (20060902).
9/2/2006 6:44:55 AM Update Error connecting to server 82.165.250.33.
9/2/2006 0:44:55 AM Update Error connecting to server 82.165.250.33.
9/1/2006 23:44:55 PM Update Error connecting to server 82.165.250.33.
9/1/2006 17:44:55 PM Update Error connecting to server 82.165.250.33.
9/1/2006 16:45:16 PM Update Error connecting to server u8.eset.com.
9/1/2006 16:44:55 PM Update Error connecting to server 82.165.250.33.
9/1/2006 15:44:55 PM Update Error connecting to server u8.eset.com.
9/1/2006 13:44:40 PM Kernel The virus signature database has been successfully updated to version 1.1735 (20060901).
9/1/2006 9:44:00 AM Update Error connecting to server 82.165.250.33.
9/1/2006 8:44:21 AM Update Error connecting to server 82.165.250.33.
9/1/2006 8:44:00 AM Update Error connecting to server u8.eset.com.
9/1/2006 7:44:02 AM Update Error connecting to server u8.eset.com.
9/1/2006 6:43:56 AM Update Error connecting to server 82.165.250.33.
8/31/2006 14:44:00 PM Kernel The virus signature database has been successfully updated to version 1.1734 (20060831).
8/31/2006 10:45:49 AM Update Function: gethostbyname, parameters: , return value: 11001
8/31/2006 10:45:49 AM Update Update attempt failed (Server connection failure.)
8/31/2006 10:45:47 AM Update Error connecting to server www.nod32.com.
8/31/2006 10:45:29 AM Update Error connecting to server u7.eset.com.
8/31/2006 10:45:10 AM Update Error connecting to server u8.eset.com.
8/31/2006 10:44:51 AM Update Error connecting to server u4.eset.com.
8/31/2006 10:44:32 AM Update Error connecting to server u3.eset.com.
8/31/2006 10:44:13 AM Update Error connecting to server u2.eset.com.
8/31/2006 10:43:56 AM Update Error connecting to server 82.165.250.33.
8/31/2006 9:45:49 AM Update Function: gethostbyname, parameters: , return value: 11001
8/31/2006 9:45:49 AM Update Update attempt failed (Server connection failure.)
8/31/2006 9:45:47 AM Update Error connecting to server www.nod32.com.
8/31/2006 9:45:28 AM Update Error connecting to server u7.eset.com.
8/31/2006 9:45:10 AM Update Error connecting to server u4.eset.com.
8/31/2006 9:44:51 AM Update Error connecting to server 82.165.250.33.
8/31/2006 9:44:28 AM Update Error connecting to server u2.eset.com.
8/31/2006 9:44:09 AM Update Error connecting to server u3.eset.com.
8/31/2006 9:43:52 AM Update Error connecting to server u8.eset.com.
8/31/2006 8:45:51 AM Update Function: gethostbyname, parameters: , return value: 11001
8/31/2006 8:45:51 AM Update Update attempt failed (Server connection failure.)
8/31/2006 8:45:49 AM Update Error connecting to server www.nod32.com.
8/31/2006 8:45:31 AM Update Error connecting to server u7.eset.com.
8/31/2006 8:45:12 AM Update Error connecting to server u4.eset.com.
8/31/2006 8:44:53 AM Update Error connecting to server u2.eset.com.
8/31/2006 8:44:34 AM Update Error connecting to server u3.eset.com.
8/31/2006 8:44:15 AM Update Error connecting to server 82.165.250.33.
8/31/2006 8:43:54 AM Update Error connecting to server u8.eset.com.

[NOD32 user]

-{ Quote: "Ok but since updates have "no time it was made by Eset" like Kav updates (The standard antivirus databases currently contain xxxxxxxrecords. The last update to the antivirus databases was released at 03 September 2006 at 01:50 (GMT +0400)., how can I know if when i have an error there is really an update available and I can't get it in that moment?" }-You should be able to see the current update version on this (http://www.eset.com/support/updates.php) page. NOD32 should download the update automatically with no problems but if some time has passed after you see an update listed on the linked page and you do not have it yet then you may wish to try 'Update Now' just once or twice or ask about it here.

Cheers :)

[NOD32 user]

-{ Quote: "same here, i dont trust the auto update any more like every 3 hours i check for update manually

Time Module Event User
9/2/2006 10:44:40 AM Kernel The virus signature database has been successfully updated to version 1.1736 (20060902).
9/1/2006 13:44:40 PM Kernel The virus signature database has been successfully updated to version 1.1735 (20060901).
8/31/2006 14:44:00 PM Kernel The virus signature database has been successfully updated to version 1.1734 (20060831)." }-But you have actually been getting the updates....

Cheers :)

[guilijan]

-{ Quote: "You should be able to see the current update version on this (http://www.eset.com/support/updates.php) page. NOD32 should download the update automatically with no problems but if some time has passed after you see an update listed on the linked page and you do not have it yet then you may wish to try 'Update Now' just once or twice or ask about it here.

Cheers :)" }-

You don't understand me.
In the link you post, there is no time date of the release.
Supouse a new update was release at 02/09/2006 21:43 but at this time i get an update error.
02/09/2006 21:43:41 Update Error connecting to server 82.165.250.33.
I can´t get then the update at that time.

So again, how can I know if when I get an update error really there is an update but I can´t catch or get it?

Why Eset don't know us the time of the update? It can do perfect in the link you give.
Kaspersky do it so Kav/Kis user know perfectly when the update are released and then the delay to get it.
So if Eset do the same, there will not be a problem if update errors continuous because in that way the user know at what time (gmt or a time Eset like to use) the update was released.
You can see what I say here:
http://www.kaspersky.com/avupdates

Y really hope you can understand me.
I was a Kis user an love Nod, but I think Nod can be better even.

[ctrlaltdelete]

-{ Quote: "Supouse a new update was release at 02/09/2006 21:43 but at this time i get an update error.
02/09/2006 21:43:41 Update Error connecting to server 82.165.250.33.
I can´t get then the update at that time.
" }-

From your logfile;

01/09/2006 15:30:18 Kernel The virus signature database has been successfully updated to version 1.1735 (20060901).
01/09/2006 15:30:11 Update Error connecting to server u8.eset.com.
01/09/2006 15:30:05 Update Error connecting to server 82.165.250.33.

If u read the logfile u will see that u only lost 13 seconds from the first error until a succesfull update.

[Brian N]

-{ Quote: "Supouse a new update was release at 02/09/2006 21:43 but at this time i get an update error.
02/09/2006 21:43:41 Update Error connecting to server 82.165.250.33.
I can´t get then the update at that time." }-
If that happens (server is down or can't be reached), NOD32 will automatically move on to the next server.
And since you are getting your updates, I really don't see what the problem is.

[marcromero]

I am still tinkering around with the suggestion HiTech_boy gave me in another thread on how to set up Nod when using dialup, now that I understand the server status on Nod32sse.com, I see that U2, U7 and 82.165.237.14 show no errors and are 100%. I have selected one for dialup connection, so far, it seems to be working, everytime I connect now, I show no errors if there is not an update available. This just might work to my satisfaction. Again, my thanks to HiTech_boy for his help and Brian N for Nod32sse.com.

Marc

[guilijan]

-{ Quote: "If that happens (server is down or can't be reached), NOD32 will automatically move on to the next server.
And since you are getting your updates, I really don't see what the problem is." }-
"NOD32 will automatically move on to the next server"

Ok, but in what moment?
Do I supouse that if when I have Update Error connecting to server and no updates recived, it is because there are not updates just in that moment?
In other words, when i recived Update Error connecting to server I must be sure that in that moment ther are not an update available? Or can be available an update but by the error conecting I can get it in that moment and need to wait to the next hour so the automatic updates will connect again?

[Brian N]

Look at you own log right here (http://www.wilderssecurity.com/showpost.php?p=830517&postcount=50), notice the time frame...

[guilijan]

Ok ok ok.
I understand what you say.

I found a Eset web page where I can find the hour of the update. I've seen for example that the 1.1736 update was released at 14.38GMT I supused that the time in that web page are local time then modified it to GMT. I have six hours of difference.

But in my log I can see:
Time Module Event User
02/09/2006 11:43:35 Update Error connecting to server u3.eset.com.

11.43:35 is 15.43:35 GMT for my conuntry

So as you can see at 15.43:35 GMT I have an error connecting to server u3.eset.com but a new update was released at 14.38 GMT so I lost it and must wait to new connect.

That's what I'm trying to say.

[kar]

I get frequent error 11001 also and want to know is it because NOD32 tries once each hour to connect and my PC was not connected to the Internet, or it tries to connect to the server when my PC is connected and then issues this alert? ???
I suppose it should try to update only when NOD32 detects Intertnet connection active, but am not so sure...

[Bubba]

-{ Quote: "I get frequent error 11001 also and want to know is it because NOD32 tries once each hour to connect and my PC was not connected to the Internet, or it tries to connect to the server when my PC is connected and then issues this alert? ???" }-If the settings found under Control Center\Nod32 System Tools\Scheduler/Planner are selected to check every hour or at User Logon and you indeed are not connected to the Internet....that can be a cause of error 11001's.

Bubba

[kar]

Hi Bubba,
Thanks. Now it is clear! I guess Eset guys should then make Event Log ignore these error messages if NOD32 detects no Internet connection to the PC!
Regards,
Radi

[iarhill]

Can anyone explain my log? I only got the update from 1871-82 because I upgrade to the new Nod. But it is not getting the updates automatically. I am on cable and the pc is on every day a number of times for a good length of time each go. Here is the log

Time Module Event User
24/11/2006 21:23:16 Kernel The virus signature database has been successfully updated to version 1882 (20061124).
20/11/2006 17:32:49 Kernel The virus signature database has been successfully updated to version 1871 (20061119).
20/11/2006 17:32:33 Update Update attempt failed (Download interrupted.) DESKTOP\Iris
20/11/2006 16:36:53 Update Update attempt failed (Server connection failure)
20/11/2006 10:30:49 Update Update attempt failed (Server connection failure)
19/11/2006 21:14:31 Kernel The virus signature database has been successfully updated to version 1871 (20061119).
19/11/2006 17:31:17 Update Update attempt failed (Server connection failure)
19/11/2006 17:17:40 Update Update attempt failed (Server connection failure)
19/11/2006 16:31:12 Update Update attempt failed (Server connection failure)
19/11/2006 15:31:12 Update Update attempt failed (Server connection failure)
19/11/2006 13:30:08 Update Update attempt failed (Server connection failure)
18/11/2006 12:56:34 Kernel Statistical information has been sent to Eset.
18/11/2006 12:56:34 Kernel Statistical information has been sent to Eset.
18/11/2006 11:57:34 Kernel The virus signature database has been successfully updated to version 1870 (20061117).
17/11/2006 17:46:40 Update Update attempt failed (Server connection failure)
17/11/2006 16:46:52 Update Update attempt failed (Server connection failure)
17/11/2006 15:14:47 Update Update attempt failed (Server connection failure)
17/11/2006 14:14:59 Update Update attempt failed (Server connection failure)
16/11/2006 19:59:34 Kernel The virus signature database has been successfully updated to version 1869 (20061116).
16/11/2006 17:59:20 Kernel The virus signature database has been successfully updated to version 1868 (20061115).
16/11/2006 16:59:09 Update Update attempt failed (Server connection failure)
16/11/2006 13:12:43 Update Update attempt failed (Server connection failure)
15/11/2006 16:47:27 Update Update attempt failed (Server connection failure)
15/11/2006 07:40:57 Update Update attempt failed (Server connection failure)
14/11/2006 20:29:52 Kernel Statistical information has been sent to Eset.
14/11/2006 20:29:50 Kernel The virus signature database has been successfully updated to version 1866 (20061114).
14/11/2006 17:57:43 Kernel Statistical information has been sent to Eset.
14/11/2006 17:57:43 Kernel Statistical information has been sent to Eset.
14/11/2006 17:57:41 Kernel The virus signature database has been successfully updated to version 1865 (20061114).
14/11/2006 13:28:43 Update Update attempt failed (Server connection failure)

[Blackspear]

Please check the following:

NOD32 Control Centre> Update> Setup> Server is set as "Choose Automatically".

Click on Advanced and make sure LAN is set for Broadband ADSL/Cable or Dialup is set for Broadband Wireless/Dialup.

Check Proxy Server Setup> setup to make sure there isn't a tick in there (99.99% of people do not use a proxy).

Check that LAN servers connection> Setup is set to System Account (default).

Beyond this NOD32 will update unless a firewall is blocking the Internet connection for NOD32.

Cheers ;D

[iarhill]

Hi again Blackspear! All settings were OK. Zone alarm was OK. I have changed to automatic server and will see if that makes a difference. I have tried to set it to check every hour - but is it possible to tell if it does it? Also, where can I find out what the latest version number is eg at present it says 1882....? Thanks

[ctrlaltdelete]

U can find update info on http://www.eset.eu/support/update-xy1

[Togg]

Anyone that doesn't want to wait fror ronjor to post update details can subscribe to the email alert service direct from Eset;https://secure.eset.co.uk/forms/threatalerts.asp This gives update generation times in UCT and CET and, in my case, the emails appear to be forwarded via my UK reseller, so I get GMT as well.

[iarhill]

Thanks - that is very useful.