Update Errors

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.

 

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.

 

error connecting

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.

 

Re: error connecting

What kind of answer do you seek? ...

 

Re: error connecting

Easy.
When will this problem will solved?

 

Re: error connecting

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

 

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

 

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.

 

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 ~

 

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.

 

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 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

 

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.

 

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.

 

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.

 

Hi avenger107 & welcome to Wilders,

That's pretty much how it is, or at least how I see it.

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

 

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.

 

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

 

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?

 

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.

 

You should be able to see the current update version on this 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

 

But you have actually been getting the updates....

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.

 

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.