Update Errors

If that happens (server is down or can't be reached), NOD32 will automatically move on to the next server.
And since you are getting your updates, I really don't see what the problem is.

 

I am still tinkering around with the suggestion HiTech_boy gave me in another thread on how to set up Nod when using dialup, now that I understand the server status on Nod32sse.com, I see that U2, U7 and 82.165.237.14 show no errors and are 100%. I have selected one for dialup connection, so far, it seems to be working, everytime I connect now, I show no errors if there is not an update available. This just might work to my satisfaction. Again, my thanks to HiTech_boy for his help and Brian N for Nod32sse.com.

Marc

 

"NOD32 will automatically move on to the next server"

Ok, but in what moment?
Do I supouse that if when I have Update Error connecting to server and no updates recived, it is because there are not updates just in that moment?
In other words, when i recived Update Error connecting to server I must be sure that in that moment ther are not an update available? Or can be available an update but by the error conecting I can get it in that moment and need to wait to the next hour so the automatic updates will connect again?

 

Look at you own log right here, notice the time frame...

 

Ok ok ok.
I understand what you say.

I found a Eset web page where I can find the hour of the update. I've seen for example that the 1.1736 update was released at 14.38GMT I supused that the time in that web page are local time then modified it to GMT. I have six hours of difference.

But in my log I can see:
Time Module Event User
02/09/2006 11:43:35 Update Error connecting to server u3.eset.com.

11.43:35 is 15.43:35 GMT for my conuntry

So as you can see at 15.43:35 GMT I have an error connecting to server u3.eset.com but a new update was released at 14.38 GMT so I lost it and must wait to new connect.

That's what I'm trying to say.

 

I get frequent error 11001 also and want to know is it because NOD32 tries once each hour to connect and my PC was not connected to the Internet, or it tries to connect to the server when my PC is connected and then issues this alert?
I suppose it should try to update only when NOD32 detects Intertnet connection active, but am not so sure...

 

If the settings found under Control Center\Nod32 System Tools\Scheduler/Planner are selected to check every hour or at User Logon and you indeed are not connected to the Internet....that can be a cause of error 11001's.

Bubba

 

Hi Bubba,
Thanks. Now it is clear! I guess Eset guys should then make Event Log ignore these error messages if NOD32 detects no Internet connection to the PC!
Regards,
Radi

 

Can anyone explain my log? I only got the update from 1871-82 because I upgrade to the new Nod. But it is not getting the updates automatically. I am on cable and the pc is on every day a number of times for a good length of time each go. Here is the log

Time Module Event User
24/11/2006 21:23:16 Kernel The virus signature database has been successfully updated to version 1882 (20061124).
20/11/2006 17:32:49 Kernel The virus signature database has been successfully updated to version 1871 (20061119).
20/11/2006 17:32:33 Update Update attempt failed (Download interrupted.) DESKTOP\Iris
20/11/2006 16:36:53 Update Update attempt failed (Server connection failure)
20/11/2006 10:30:49 Update Update attempt failed (Server connection failure)
19/11/2006 21:14:31 Kernel The virus signature database has been successfully updated to version 1871 (20061119).
19/11/2006 17:31:17 Update Update attempt failed (Server connection failure)
19/11/2006 17:17:40 Update Update attempt failed (Server connection failure)
19/11/2006 16:31:12 Update Update attempt failed (Server connection failure)
19/11/2006 15:31:12 Update Update attempt failed (Server connection failure)
19/11/2006 13:30:08 Update Update attempt failed (Server connection failure)
18/11/2006 12:56:34 Kernel Statistical information has been sent to Eset.
18/11/2006 12:56:34 Kernel Statistical information has been sent to Eset.
18/11/2006 11:57:34 Kernel The virus signature database has been successfully updated to version 1870 (20061117).
17/11/2006 17:46:40 Update Update attempt failed (Server connection failure)
17/11/2006 16:46:52 Update Update attempt failed (Server connection failure)
17/11/2006 15:14:47 Update Update attempt failed (Server connection failure)
17/11/2006 14:14:59 Update Update attempt failed (Server connection failure)
16/11/2006 19:59:34 Kernel The virus signature database has been successfully updated to version 1869 (20061116).
16/11/2006 17:59:20 Kernel The virus signature database has been successfully updated to version 1868 (20061115).
16/11/2006 16:59:09 Update Update attempt failed (Server connection failure)
16/11/2006 13:12:43 Update Update attempt failed (Server connection failure)
15/11/2006 16:47:27 Update Update attempt failed (Server connection failure)
15/11/2006 07:40:57 Update Update attempt failed (Server connection failure)
14/11/2006 20:29:52 Kernel Statistical information has been sent to Eset.
14/11/2006 20:29:50 Kernel The virus signature database has been successfully updated to version 1866 (20061114).
14/11/2006 17:57:43 Kernel Statistical information has been sent to Eset.
14/11/2006 17:57:43 Kernel Statistical information has been sent to Eset.
14/11/2006 17:57:41 Kernel The virus signature database has been successfully updated to version 1865 (20061114).
14/11/2006 13:28:43 Update Update attempt failed (Server connection failure)

 

Please check the following:

NOD32 Control Centre> Update> Setup> Server is set as "Choose Automatically".

Click on Advanced and make sure LAN is set for Broadband ADSL/Cable or Dialup is set for Broadband Wireless/Dialup.

Check Proxy Server Setup> setup to make sure there isn't a tick in there (99.99% of people do not use a proxy).

Check that LAN servers connection> Setup is set to System Account (default).

Beyond this NOD32 will update unless a firewall is blocking the Internet connection for NOD32.

Cheers

 

Hi again Blackspear! All settings were OK. Zone alarm was OK. I have changed to automatic server and will see if that makes a difference. I have tried to set it to check every hour - but is it possible to tell if it does it? Also, where can I find out what the latest version number is eg at present it says 1882....? Thanks

 

U can find update info on http://www.eset.eu/support/update-xy1

 

Anyone that doesn't want to wait fror ronjor to post update details can subscribe to the email alert service direct from Eset;https://secure.eset.co.uk/forms/threatalerts.asp This gives update generation times in UCT and CET and, in my case, the emails appear to be forwarded via my UK reseller, so I get GMT as well.

 

Thanks - that is very useful.