Can´t update NOD32

Over the last 3+ years I have never had an issue and nor have any of my hundreds of customers. I do know another reseller had an issue with a few of her dialup customers, but that is it.

Cheers

 

As it's been already said, there have never been problems with updating for the last year since Eset improved the update system.

 

Not bad at all really. The two AV's themselves are not directly being compared as to their features, detection or removal abilities. I'm just pointing out to xp 1839 that he does not know what frustration truly is when it comes to updating.

 

>> Time to dump NOD32 too? <<

Maybe. The two times I emailed support in the past - NEVER got the courtesty of an email or phone reply.

LINUX mailservers report failed updates past two days.
www.nod32.com is down.

NOD32 Update Mirror Creator, Version 2.09,
(C) 2004 Eset, s.r.o.
Update started on 10-30-2005, 04:00:01.
Checking remote update packages at 'www.nod32.com'... failed.
error: Remote update packages not checked. exitting...

 

There is no automatic selection on unix.
It's either www.nod32.com or nothing.

 

I'm not 100% sure, but I think http://u4.eset.com/nod_upd should work as well.

 

I usually try all the windows update servers by looking up their IPs and putting them in /etc/hosts on the unix computers as www.nod32.com fooling the updater to look at those other spots. Although alive, they give errors about missing files which goes away (this isn't the first time update broke for over a day) when the regular site starts working.

 

I don't know exactly how you define "never been problems with updating" but I constantly get a "error connecting to server message" before it eventually updates.

For example, today is Oct 30th, the last successful update I got was on the 28th. I've had 10 "error connecting" messages since then. Before I got the update on the 28th, I had 51 (yes, 51!) failed update attempts. I don't check my logs that often, but whenever I do, there are MANY, MANY error messages before I finally get a good update. I, too have used other A/V's and none of them have the constant update problems that NOD32 has.

I stick with NOD32 because I believe it's one of the best A/V's out there but the update problem does need to be addressed.

I use all the default settings so I haven't tried manually changing the update servers. I know they scroll through until they find one that works but it seems that alot of them do not work. Should I try changing order of them?

 

My setup as: Update | Setup | Location | Server: | <Choose automatically> works with ~ 1/2 second lag.

If I select 82.165.237.14 or 82.165.250.33, or at least all *but* u7.eset.com, update check more immediate.

u7.eset.com, for me at this time, 'pauses' ~ 20 sec. before apparently successfully completing - no error message in update screen. But when go to 'Event Log' (see edit below), see that the update has failed when u7 selected as the server.


Per http://eset.sk/en CURRENT VERSION Virus database: 1.1267 ( 20051028 )
10/28/05 17:49:19 PM (US CDT - at the time) which is what shows in my installation.


edit re 'error connecting': I thought what was meant was an error message appearing in update session.

Did just check 'Event Log' and do see 'error connecting' to u7.eset.com repeatedly recent hour and and going back to 10/16/2005 all the others one time or another.
On 10/16/2005 appears none worked for ~ 2 h. Definite issues with u7 since 26th, maybe continuously back to 16th of 10/2005.

 

u7 is down for maintaince for a few days, apparently was stated somewhere on the forum.

 

Then what about the others servers that fail to connect, have they been down too??

Time Module Event User
10/30/2005 11:45:20 AM Kernel Statistical information has been sent to Eset.
10/30/2005 10:43:30 AM Update Error connecting to server u7.eset.com.
10/30/2005 7:43:31 AM Update Error connecting to server u3.eset.com.
10/30/2005 4:43:18 AM Update Error connecting to server u7.eset.com.
10/30/2005 3:43:18 AM Update Error connecting to server u7.eset.com.
10/29/2005 21:43:19 PM Update Error connecting to server u7.eset.com.
10/29/2005 20:43:18 PM Update Error connecting to server u7.eset.com.
10/29/2005 14:43:19 PM Update Error connecting to server u7.eset.com.
10/29/2005 7:43:19 AM Update Error connecting to server u7.eset.com.
10/29/2005 0:43:18 AM Update Error connecting to server u7.eset.com.
10/28/2005 17:43:18 PM Update Error connecting to server u7.eset.com.
10/28/2005 15:43:02 PM Kernel The virus signature database has been successfully updated to version 1.1267 (2005102
10/28/2005 10:43:18 AM Update Error connecting to server u7.eset.com.
10/28/2005 3:43:18 AM Update Error connecting to server u7.eset.com.
10/27/2005 20:43:18 PM Update Error connecting to server u7.eset.com.
10/27/2005 13:43:19 PM Kernel Statistical information has been sent to Eset.
10/27/2005 13:43:18 PM Update Error connecting to server u7.eset.com.
10/27/2005 8:42:58 AM Kernel Statistical information has been sent to Eset.
10/27/2005 7:43:18 AM Update Function: gethostbyname, parameters: , return value: 11001
10/27/2005 7:43:18 AM Update Update attempt failed (Server connection failure.)
10/27/2005 7:43:16 AM Update Error connecting to server www.nod32.com.
10/27/2005 7:43:12 AM Update Error connecting to server u4.eset.com.
10/27/2005 7:43:09 AM Update Error connecting to server u3.eset.com.
10/27/2005 7:43:05 AM Update Error connecting to server u1a.eset.com.
10/27/2005 7:43:01 AM Update Error connecting to server 82.165.237.14.
10/27/2005 7:42:59 AM Update Error connecting to server 82.165.250.33.
10/27/2005 7:42:59 AM Update Error connecting to server u7.eset.com.
10/27/2005 6:43:18 AM Update Function: gethostbyname, parameters: , return value: 11001
10/27/2005 6:43:18 AM Update Update attempt failed (Server connection failure.)
10/27/2005 6:43:16 AM Update Error connecting to server www.nod32.com.
10/27/2005 6:43:12 AM Update Error connecting to server 82.165.237.14.
10/27/2005 6:43:11 AM Update Error connecting to server 82.165.250.33.
10/27/2005 6:43:09 AM Update Error connecting to server u4.eset.com.
10/27/2005 6:43:05 AM Update Error connecting to server u3.eset.com.
10/27/2005 6:43:02 AM Update Error connecting to server u1a.eset.com.
10/27/2005 6:42:59 AM Update Error connecting to server u7.eset.com.
10/27/2005 5:43:19 AM Update Function: gethostbyname, parameters: , return value: 11001
10/27/2005 5:43:19 AM Update Update attempt failed (Server connection failure.)
10/27/2005 5:43:18 AM Update Error connecting to server www.nod32.com.
10/27/2005 5:43:14 AM Update Error connecting to server u1a.eset.com.
10/27/2005 5:43:10 AM Update Error connecting to server 82.165.250.33.
10/27/2005 5:43:08 AM Update Error connecting to server u7.eset.com.
10/27/2005 5:43:04 AM Update Error connecting to server u3.eset.com.
10/27/2005 5:43:01 AM Update Error connecting to server u4.eset.com.
10/27/2005 5:42:58 AM Update Error connecting to server 82.165.237.14.
10/27/2005 3:44:49 AM Update Function: gethostbyname, parameters: , return value: 11001
10/27/2005 3:44:49 AM Update Update attempt failed (Server connection failure.)
10/27/2005 3:44:47 AM Update Error connecting to server www.nod32.com.
10/27/2005 3:44:29 AM Update Error connecting to server u4.eset.com.
10/27/2005 3:44:06 AM Update Error connecting to server u1a.eset.com.
10/27/2005 3:43:43 AM Update Error connecting to server u3.eset.com.
10/27/2005 3:43:21 AM Update Error connecting to server 82.165.250.33.
10/27/2005 3:42:58 AM Update Error connecting to server 82.165.237.14.
10/27/2005 3:42:37 AM Update Error connecting to server u7.eset.com.
10/27/2005 2:44:49 AM Update Function: gethostbyname, parameters: , return value: 11001
10/27/2005 2:44:49 AM Update Update attempt failed (Server connection failure.)
10/27/2005 2:44:47 AM Update Error connecting to server www.nod32.com.
10/27/2005 2:44:28 AM Update Error connecting to server u1a.eset.com.
10/27/2005 2:44:06 AM Update Error connecting to server u7.eset.com.
10/27/2005 2:43:43 AM Update Error connecting to server 82.165.250.33.
10/27/2005 2:43:21 AM Update Error connecting to server u4.eset.com.
10/27/2005 2:42:58 AM Update Error connecting to server u3.eset.com.
10/27/2005 2:42:37 AM Update Error connecting to server 82.165.237.14.
10/26/2005 21:42:37 PM Update Error connecting to server u7.eset.com.
10/26/2005 20:42:38 PM Update Error connecting to server u7.eset.com.

 

I commented about u7 only, because specific reference was made to it by a previous poster. I don't know about the others, but some info is better than none don't you think? You probably know this but in case you don't there is another current thread about the problem on the forum. https://www.wilderssecurity.com/showthread.php?p=595634#post595634

 

Could this possibly be another type of connection problem with your ISP?

You posted for the 27th.

Here is my log for the 27th.

Time Module Event User
10/28/2005 5:19:49 AM Kernel Statistical information has been sent to Eset.
10/27/2005 12:20:34 PM Kernel Statistical information has been sent to Eset.
10/27/2005 6:19:56 AM Update Error connecting to server 82.165.250.33.
10/27/2005 5:20:20 AM Kernel Statistical information has been sent to Eset.
10/27/2005 5:19:56 AM Update Error connecting to server 82.165.250.33.
10/26/2005 15:37:03 PM Kernel The virus signature database has been
successfully updated to version 1.1266 (20051026).

 

I don't think so. Before work each day, I'm on the internet reading news, checking email etc. from around 06:00am to 07:00am, which I did on the 27th. I will say that the past few days seem to have been worse than usual (regarding the NOD32 updates) but I usually check the logs a few times a week and I constantly get the error messages. As long as I get a successful one in between, I don't worry too much.

The main reason I posted was in response to Marcos' comment where he said "There have never been problems with the update servers for the last 1 year"

That's just plain ludicrous.

I have several programs that do auto-updates and none of them have the problems that NOD32 has. Now, I'm in the USA so maybe something is getting lost between here and the NOD32 servers, I don't know but I do know the problem isn't on my end.

 

Everything works fine now on my end.

 

I use my computer very regularly, every morning and throughout each evening, sometimes into early am, and have not noticed any network connection problems: http, https, smtp, imap for dates covered below:

Time Module Event User
10/27/2005 1:24:55 AM Update Error connecting to server 82.165.250.33.
10/27/2005 1:24:33 AM Update Error connecting to server u1a.eset.com.
10/27/2005 1:24:10 AM Update Error connecting to server u7.eset.com.
10/27/2005 1:23:49 AM Update Error connecting to server u4.eset.com.
10/26/2005 23:23:53 PM Update Error connecting to server u7.eset.com.
10/26/2005 22:23:54 PM Update Error connecting to server u7.eset.com.
10/17/2005 16:30:53 PM Kernel The virus signature database has been successfully updated to version 1.1258 (20051017).
10/16/2005 16:00:15 PM Update Update attempt failed (Failure to open socket.)
10/16/2005 16:00:14 PM Update Error connecting to server www.nod32.com.
10/16/2005 16:00:12 PM Update Error connecting to server u4.eset.com.
10/16/2005 16:00:10 PM Update Error connecting to server u1a.eset.com.
10/16/2005 16:00:09 PM Update Error connecting to server 82.165.250.33.
10/16/2005 16:00:07 PM Update Error connecting to server u7.eset.com.
10/16/2005 16:00:06 PM Update Error connecting to server u3.eset.com.
10/16/2005 16:00:06 PM Update Error connecting to server 82.165.237.14.
10/16/2005 15:58:17 PM Update Update attempt failed (Failure to open socket.)
10/16/2005 15:58:15 PM Update Error connecting to server www.nod32.com.
10/16/2005 15:58:14 PM Update Error connecting to server u4.eset.com.
10/16/2005 15:58:12 PM Update Error connecting to server u1a.eset.com.
10/16/2005 15:58:11 PM Update Error connecting to server u3.eset.com.
10/16/2005 15:58:09 PM Update Error connecting to server u7.eset.com.
10/16/2005 15:58:07 PM Update Error connecting to server 82.165.237.14.
10/16/2005 15:58:07 PM Update Error connecting to server 82.165.250.33.

Do wonder if: Update attempt failed (Failure to open socket.)
implies, means, anything specific?
Though, reason for update failure only two of the occurrences.
Do notice that those both follow: Error connecting to server www.nod32.com.

Will now check Event Log daily.

 

If an attempt to open a socket fails, then there is either another program interfering with NOD32 installed, or there is a serious problem with the oper. system itself.

 

Does seem odd that another program interfering only when attempting to connect to server www.nod32.com.

No serious problem with OS here.

Thanks for the info - though still do not understand why a program interferes only when attempting to connect to nod32.com and not the other servers - at least over a ~ a 12 day history.

 

The problem occurs regardless of the update server used, the thing is the NOD32 kernel service is unable to open a socket for http connection for some reason. Usually this is caused by another program that might be interfering somehow.

 

What about all my error messages? None of them say "failure to open socket.

 

All the update servers (except u7 that's down for maintanence) have been running flawlessly for at leat one year. Make sure the errors are not from computer startup when an internet connection might not have been established yet. Also, see http://www.eset.com/support/ans/11b.htm for possible causes of that error.

 

I just installed NOD32 today, and I try to update, only to get these messages-

Time Module Event User
11/1/2005 0:20:47 AM Update Update attempt failed (Server connection failure)

Are there any ports I need to foward so I can get the updates?

 

For future reference - You can always check the status of the update servers right here.