Update issue?

[sir_carew]

Hello,
I've a scheduled update repeatedly every 1 hour, but I'm experimenting some problems with it.
When I start the computer, Nod load before that Zone Alarm Pro 4.0.146.029. When My computer finish to load all programs I receive an alert of my e-mail that said for example:
(I've configured NOD to email me all problems and alert)
08-10-2003 8:45:43 - During execution of Update on the computer xxxx, the following warning
occured: Update attempt terminated with error (Server connection failure), or Download files damaged, etc. However if I click on "Update now" botton under the Update tab, NOD update successfully without problems.
I think that the problem is the following:
Every time that start my computer, NOD load before that Zone Alarm Pro, for it reason Za Pro block any attemp comunication when the program is not fully loaded.
It's possible?
(If I update NOD manual, I not have problem) and some times (little) automatic work properly, but the most not :'(
Thanks,

[LowWaterMark]

-{ Quote: "If I update NOD manual, I not have problem) and some times (little) automatic work properly, but the most not..." }-

Is it only the first automatic update (when you first boot) that doesn't work, or is it all (or most) automatic updates, even after the system has been up for 1 hour, then 2 hours, etc. that don't work. It's not clear from what you've said whether later automatic updates also fail most of the time.

It is certainly possible that the firewall is blocking your first update, at bootup, because of a startup timing issue. It's also possible that the network is not fully connected when NOD first tries to update at boot time. The only way to test this would be to disable ZAP from starting at boot time and then seeing if NOD32 always updates properly while booting. (You need to be confident that your system is well patched, of course, to test with your firewall disabled.)

[sir_carew]

Thanks for your quickly reply ;D
It's extrange because I set update every 1 hour and when I start the PC i look at update tab and NOD is starting to update and not passed 1 hour.

[LowWaterMark]

-{ Quote: " quoting: sir_carew link=board=39;threadid=14704;start=0#msg92395 date=1065647286]It's extrange because I set update every 1 hour and when I start the PC i look at update tab and NOD is starting to update and not passed 1 hour." }-

I'm sorry, I don't quite understand what you are saying. After 1 more hour passes, (your PC's been up and running), does NOD try to update again? If so, is it successful or does it mostly fail? And then after the second hour, third hour and so on, does it update then, too?

[sir_carew]

Hello,
No, I've configured the update every 1 hour, however the update run when te computer start and also every 1 hour, and the failed is when the computer start recently, but the extrange is that I've configured update every 1 hour and not when the user log on, I check it.
And also if I update the NOD manually, NOD update perfect.
Best Regards.

[cheber]

Eset sure seems to have some problems with their servers. Automatic update every hour, and I always seem to get "Server connection failure". And only _once_ (2/10) has NOD32 tried using the other servers. Not that it helped trying all servers...

Time Module Event
2003-10-09 17:32 Kernel The virus signature database has been updated successfully to version 1.531 (20031009).
2003-10-09 16:32 Update Update attempt terminated with error (Server connection failure)
2003-10-08 17:34 Kernel The virus signature database has been updated successfully to version 1.530 (20031008).
2003-10-08 16:34 Update Update attempt terminated with error (Server connection failure)
2003-10-08 15:34 Update Update attempt terminated with error (Server connection failure)
2003-10-08 14:34 Update Update attempt terminated with error (Server connection failure)
2003-10-07 19:22 Update Error connecting to server sun.uid0.sk.
2003-10-06 22:09 Kernel The virus signature database has been updated successfully to version 1.528 (20031006).
2003-10-06 21:09 Update Update attempt terminated with error (Server connection failure)
2003-10-06 11:09 Kernel The virus signature database has been updated successfully to version 1.527 (20031006).
2003-10-06 10:09 Update Update attempt terminated with error (Server connection failure)
2003-10-04 09:28 Kernel The virus signature database has been updated successfully to version 1.526 (20031003).
2003-10-03 17:51 Kernel The virus signature database has been updated successfully to version 1.525 (20031003).
2003-10-02 18:21 Kernel The virus signature database has been updated successfully to version 1.524 (20031002).
2003-10-02 17:22 Update Update attempt terminated with error (Server connection failure)
2003-10-02 00:10 Update Function: gethostbyname, parameters: , return value: 11001
2003-10-02 00:10 Update Update attempt terminated with error (Server connection failure.)
2003-10-02 00:10 Update Error connecting to server www.nod32.com.
2003-10-02 00:10 Update Error connecting to server www.esetsoftware.com.
2003-10-02 00:10 Update Error connecting to server www.nod32.com.
2003-10-02 00:10 Update Error connecting to server www.eset.sk.
2003-10-01 18:53 Kernel The virus signature database has been updated successfully to version 1.523 (20030930).
2003-10-01 18:14 Update Update attempt terminated with error (Downloaded file is damaged.)
2003-10-01 17:14 Update Update attempt terminated with error (Server connection failure)

edit: One thing I'd like to add. When I posted this before for some reason I didn't think that all update-checks which didn't inlcude dl weren't visible in the log (obvously). That makes the log look worse than it really is.

[jan]

Hi All,

pls. try to use the function <Choose automatically> in the NOD32 CC->Update->Update->Setup->Servers - this can help to distribute the load between the update servers.

Thanks,

jan

[martindijk]

Thanks Jan,

Tried it and went fine, no probs.. ;)

cheers,
Martin

[cheber]

Uhm, well it doesn't help here. The above log is from NOD set to "choose auto".

[sir_carew]

Hello,
I've the solution:
Disable the update every 1 hour and schedule a new update task that Update your computer on user loggon.
I make it and now NOD update perfect and without me.
:D
Bye,

[sir_carew]

Sorry, isn't on user loggon, is when computer start.
;D

[jan]

Hi All,

it seems there is a increasing number of NOD32 users updating from our update servers - that's why we are preparing to add some more such server/s - it is scheduled for the next week.

Please use the <Choose automatically> setting - as I wrote above in the meantime - and we kindly ask you for a bit patience. The maximum load to the update servers is when a new update is released - so a while after the peak it should be better.

Sorry for the inconvenience and thanks a lot for your understanding. :)

All the best,

jan

[sir_carew]

Hello Jan, I understand perfectly, no problem ;)
When the new servers are ready, can you post the addresses for add it to NOD?
Thanks a lot.

[jan]

Hi,

>When the new servers are ready, can you post the addresses for add it to NOD?

Yeah, I'll post the news :)

Cheers,

jan

[Tomas]

Hi

There is no need to add the new servers. Once you set your update server to option <Choose automatically>, it will also automaticaly update the server list.

Tomas, Eset