update errors

Yesterday, July 11th, I had eight server connection update errors before I finally got the correct update. It looks as if it tried all of the servers and couldn't connect to anyone of them. Could this be connected to the component update issue?

 

No, there hasn't been any glitch with the update servers for a couple of months since we extended the number of update servers.

 

isp issues?

 

Here is the log:

Time Module Event User
8/11/2005 16:15:53 PM Kernel The virus signature database has been successfully updated to version 1.1192 (20050811).
8/11/2005 9:18:09 AM Update Function: gethostbyname, parameters: , return value: 11001
8/11/2005 9:18:09 AM Update Update attempt failed (Server connection failure.)
8/11/2005 9:18:08 AM Update Error connecting to server www.nod32.com.
8/11/2005 9:17:49 AM Update Error connecting to server u3.eset.com.
8/11/2005 9:17:30 AM Update Error connecting to server 82.165.237.14.
8/11/2005 9:17:07 AM Update Error connecting to server u4.eset.com.
8/11/2005 9:16:48 AM Update Error connecting to server u1a.eset.com.
8/11/2005 9:16:30 AM Update Error connecting to server u7.eset.com.
8/11/2005 9:16:09 AM Update Error connecting to server 82.165.250.33.

Update is set to automatic. Don't think it is a server issue. I am on DSL and constantly connected.

 

8/11/2005 9:18:09 AM Update Function: gethostbyname, parameters: , return value: 11001
ISP Issue or no connection to the net at the time

 

According to this thread from 2004, the problem was with the Eset servers, not the local isp:

https://www.wilderssecurity.com/showthread.php?t=42950

 

Well there you go

 

Since I use NOD32, about 2 years, I have problems with the update servers...

 

I told there haven't been any problems since we increased the number of update servers. It was definitely at a later time after the problem was reported on Wilders.

 

Time Module Event User
13/08/2005 1:00:49 AM Update Update attempt failed (Failure to open socket.)

Time Module Event User
13/08/2005 1:00:45 AM Update Error connecting to server www.nod32.com.
13/08/2005 1:00:43 AM Update Error connecting to server u4.eset.com.
13/08/2005 1:00:42 AM Update Error connecting to server u3.eset.com.
13/08/2005 1:00:40 AM Update Error connecting to server u5.eset.com.
13/08/2005 1:00:39 AM Update Error connecting to server u1a.eset.com.
13/08/2005 1:00:39 AM Update Error connecting to server u7.eset.com.

Im getting this message, what does it mean?

 

Try running WinsockFix which should fix your problem

 

Wow Thanks! I think it fixed it, well it said no updates available, Thanks!

 

You are welcome

 

Marcos, I was just using that thread as an example to answer Brian N when he said:

I thought he meant that the ISP problem was on my side. According to that thread "gethostbyname, parameters, return value: 1100", refered to error on Eset servers.
Anyway, I hope the problem has been cleared up by now. Time will tell.

 

I really should have checked it better
The error I get when disabling my connection looks like yours, but the numbers are different (11004)

 

I'm getting errors as well:

Time Module Event User
8/13/2005 0:27:41 AM Update Error connecting to server u1a.eset.com.
8/12/2005 23:46:14 PM Update Error connecting to server u4.eset.com.
8/12/2005 20:44:26 PM Update Error connecting to server 213.215.116.226.


This is my first try w/ Nod32, so I'm uncertain of the frequency of updates, but my last update is dated 8/12/05, version 1.1193. I am scheduled for repeated updates every hour; should I be concerned that I'm getting these log errors indicating I can't connect to Eset's server?

 

Updates are usually released daily from monday to friday, and in some special cases in the weekends too.
And yes, you have to most recent update.

The errors you are getting simply mean those 3 servers could not be contacted.
If that's the case, NOD will just try the other servers.