Can´t update NOD32

[POS]

the NOd32.ch site shows 1.1266, but my nod is at 1.1265 and says it´s up to date...

[Triple Helix]

{QUOTE-> the NOd32.ch site shows 1.1266, but my nod is at 1.1265 and says it´s up to date... <-QUOTE}

Try till it updates!!

;D

[Blackspear]

{QUOTE-> the NOd32.ch site shows 1.1266, but my nod is at 1.1265 and says it´s up to date... <-QUOTE}Mine is still at 1.265, wouldn't worry about it to much just yet ;) ;D

Cheers ;D

[webyourbusiness]

I'm sure it will come in time - the update itself is pretty large - so you have to be a little patient - only so many bits can flow at any given moment... ;)

[The Hammer]

{QUOTE-> I'm sure it will come in time - the update itself is pretty large - so you have to be a little patient - only so many bits can flow at any given moment... ;) <-QUOTE}Got it via manual update a couple of minutes ago.;D

[Mover]

{QUOTE-> Got it via manual update a couple of minutes ago.;D <-QUOTE}

Which server ? I'm still getting the 'NOD32 is uptodate' message.

[thepacingman]

All I get is this message by both automatic and manual updates

27/10/2005 11:36:14 AM Update Update attempt failed (Server connection failure)

[The Hammer]

{QUOTE-> Which server ? I'm still getting the 'NOD32 is uptodate' message. <-QUOTE}Don't know? I just clicked update now several times a few minutes apart and the last time it worked.???

[Blackspear]

Mine just updated a few minutes ago, so all Eset are doing is balancing the load on their servers, have a little patience, you will see it ;) ;D

Cheers ;D

[Mover]

{QUOTE-> Don't know? I just clicked update now several times a few minutes apart and the last time it worked.??? <-QUOTE}

I think it specifies which one in your Event Log

[The Hammer]

{QUOTE-> I think it specifies which one in your Event Log <-QUOTE}Just checked and all it says is the virus signature database has been sucessfully updated.

[Triple Helix]

{QUOTE-> Just checked and all it says is the virus signature database has been sucessfully updated. <-QUOTE}


What is your Update Version Number? 1.1265 or 1.1266



:)

[The Hammer]

{QUOTE-> What is your Update Version Number? 1.1265 or 1.1266



:) <-QUOTE}1.1266

[Jaska]

Mine didn't update either until I manually chose server u4.eset.com. Then there came an engine0 update about 1 meg in size.

[worldcitizen]

This has always been a real problem with Eset. For God's sake when will they ever get their act together? I had NOD for 2 years and constantly had updating problems which I got fed up with after a few infections and got rid of the program.

If Eset are really serious about protecting PC's then they must address this issue once and for all. I've had many AV's but none of them ever gave me constant updating problems like NOD 32. It should happen automatically without hassel and function as smooth as silk but judging from posts and my own personal experience of having NOD for 2 years, Eset just seem to plod along with overloaded servers and never seem to fix this issue.

They worry more about getting awards than making life easier for their customers and that really stinks. Eset should show much more consideration towards their customers and fix their servers to function properly as do most other AV Companies. I have had Kaspersky Pro for a year and never once had update problems so far or had to fiddle with trying out different servers and the same with Bit Defender and Norton.

This is a problem that has gone on for years with NOD 32 and I haven't had a similar problem with any other AV so why don't they start to act a bit responsibly and do something to kill this problem once and for all? Ocassional problems are acceptable but this has always been a constant problem I have had with NOD over a 2 year period and NOD, if it is to be considered seriously must update smoothly without user intervention or hassel. I can't see why Eset can't do this properly if most other companies can.

Dave

[Marcos]

There have never been problems with the update servers for the last 1 year. If you have the update server set to automatic selection, NOD32 will cycle through all of them until it finds one from which an update can be downloaded (there's more than 90% chance it will be the very first server NOD32 tries). If a server is under maintanance, NOD32 will still be able to update from the others.

[Antarctica]

As for myself I cannot complain. Except for this week where the big update was delayed, it works perfect. It is set to "Automatic".:)

[worldcitizen]

That's always been my sticking point with NOD 32 for me.

I can accept that rarely viruses do get through even the best AV's because no AV is perfect but with the updating I had issues connecting to their servers and getting updates and I had my settings on automatic. Now and again it just wouldn't update and also occassionally asked for my password again although I had already entered that.

I rate it among the best and still would like to use it again one day but I'm a 'set it and forget it' person and just don't have the time or patience to fiddle with settings and having to do manual updates too often.

The other problem was once when some viruses got through I was advised to change the default settings and I've just got no time to go through the recommended settings by Blackspear is it to secure my PC. I just want to install the program and be left alone and it did become quite confusing going through many dialogues changing settings when all I really wanted was for it to install and do it's job to protect me without any hassel.

Maybe it's improved I don't know but configuring it is somewhat confusing and once when I did configure it according to some instructions I found here it scanned so slow and my PC slowed down a lot so I lost the benefit of it's low resources. It was a catch 22. If I had it on default some nasties got through. If I turned it up my performance got zapped.

Dave

[Blackspear]

I don't know why you continue to rehash this (http://www.wilderssecurity.com/showthread.php?t=43614) Dave. The plain and simple fact was you had a Trojan fly past the world’s best Trojan software, as well as Nod32, so this in turn points to your security lacking, as in the number 1 fact that you did not have a software firewall installed. But let's not go down this road yet again, and again, and again, and again... ::)

Blackspear.

[webyourbusiness]

agreed - anyone wanting "perfect" security should expect to have a "perectly deep pocket" - if not, there will be some kind of limitation somewhere... and just about EVERYONE needs to start getting used to the fact...

aint NOTHING perfect in this world...

[Brian N]

{QUOTE-> agreed - anyone wanting "perfect" security should expect to have a "perectly deep pocket" - if not, there will be some kind of limitation somewhere... and just about EVERYONE needs to start getting used to the fact...

aint NOTHING perfect in this world... <-QUOTE}
Amen to that.

[xp_1839]

The fact that they do not allow manual download of virus definition file and update problem can turn many away from using NOD32 anitvirus!!!

Time to dump NOD32 too?

Long user of Symantec antivirus, dumped it as virus definition file grow too big and resource-hog,

Then Avast antivirus, dumped it due to false positive and problem with transparent proxy,

Now using NOD32 and having this update issue!

Folks at NOD32 need to get their act together before users flee!

>:( >:( >:( >:( >:(

[The Hammer]

{QUOTE-> The fact that they do not allow manual download of virus definition file and update problem can turn many away from using NOD32 anitvirus!!!

Time to dump NOD32 too?

Long user of Symantec antivirus, dumped it as virus definition file grow too big and resource-hog,

Then Avast antivirus, dumped it due to false positive and problem with transparent proxy,

Now using NOD32 and having this update issue!

Folks at NOD32 need to get their act together before users flee!

>:( >:( >:( >:( >:( <-QUOTE}Most Nod users will not be going anywhere. In fact I know one chap who uses a particular Av (cough ) Antivir, and posts in the Other Av forum who would kiss the ground for one with as few update problems as Nod (if it were free).;D

[waters]

Wow,how bad has it got to use a free antivirus,and use it as a yardstick to nod

[worldcitizen]

{QUOTE-> I don't know why you continue to rehash this (http://www.wilderssecurity.com/showthread.php?t=43614) Dave. The plain and simple fact was you had a Trojan fly past the world’s best Trojan software, as well as Nod32, so this in turn points to your security lacking, as in the number 1 fact that you did not have a software firewall installed. But let's not go down this road yet again, and again, and again, and again... ::)

Blackspear. <-QUOTE}

Blackspear

The issue being discussed on this thread is NOD 32's updating problems and that is what I wish to speak about and try and resolve or make Eset more aware of the need to improve their service.

Infiltration is always on the cards if updating is not taking place smoothly/regularly and that is the secondary related issue I raised.

I constantly had problems with NOD 32's updating mechanism over a 2 year period and wanted to mention this on this forum in the hope that Eset notice this and try and improve their updating service.

I have never had issues with many other AV's updating service as I had with NOD's so if most other companies can provide a reliable service then I would expect Eset to do the same as infections can occur if a machine cannot update at a critical time.

Dave

[Blackspear]

{QUOTE-> I constantly had problems with NOD 32's updating mechanism over a 2 year period... <-QUOTE}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 ;D

[Marcos]

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

[The Hammer]

{QUOTE-> Wow,how bad has it got to use a free antivirus,and use it as a yardstick to nod <-QUOTE}Not bad at all really.;D 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.;)

[stevenestrada]

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

[stevenestrada]

{QUOTE-> There have never been problems with the update servers for the last 1 year. If you have the update server set to automatic selection <-QUOTE}

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

[Marcos]

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

[stevenestrada]

{QUOTE-> I'm not 100% sure, but I think http://u4.eset.com/nod_upd should work as well. <-QUOTE}

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.

[JimmyD]

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

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?

[billaku]

{QUOTE-> 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? <-QUOTE}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.

[The Hammer]

{QUOTE-> 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. <-QUOTE}u7 is down for maintaince for a few days, apparently was stated somewhere on the forum.

[JimmyD]

{QUOTE-> u7 is down for maintaince for a few days, apparently was stated somewhere on the forum. <-QUOTE}

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

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

[The Hammer]

{QUOTE-> Then what about the others servers that fail to connect, have they been down too?? :o

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 (20051028)
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. <-QUOTE}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. http://www.wilderssecurity.com/showthread.php?p=595634#post595634

[Stan999]

{QUOTE-> 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. <-QUOTE}

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

You posted for the 27th.
{QUOTE->
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.
<-QUOTE}


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

[JimmyD]

{QUOTE-> Could this possibly be another type of connection problem with your ISP? <-QUOTE}

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. ;D

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.

[The Hammer]

Everything works fine now on my end.;D

[billaku]

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.

[Marcos]

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.

[billaku]

{QUOTE-> 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. <-QUOTE}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.

[Marcos]

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.

[JimmyD]

{QUOTE-> 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. <-QUOTE}

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

[Marcos]

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.

[kirbysuperstar]

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?

[Brian N]

For future reference - You can always check the status of the update servers right here (http://ip2.users.whitehat.dk/server_status.php). ;)