Update Errors

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

 

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

 

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.

 

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

 

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.

 

Is Eset having server problems again?

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.

 

Re: Is Eset having server problems again?

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.

 

Re: Is Eset having server problems again?

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.

 

Re: Is Eset having server problems again?

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

 

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 !

 

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

 

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

 

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

 

But it's true

 

Numerous server update errors

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.

 

Re: Numerous server update errors

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

 

Re: Numerous server update errors

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

 

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.

 

Re: Numerous server update errors

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

 

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

 

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.

 

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

 

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