evaluating Nod32 - update question

I am evaluating Nod32 for use on my R51 Thinkpad, which is not always connected to the internet. I have experienced no updates between 9/29 and 10/9, even with some manual attempts. After reading a lot of mostly uncivil posts on this forum relating to this question, I decided to try repeatedly hitting the manual update button. Lo and Behold! I got an update on the 5th try. So, my concern is: will the regsistered version behave better on my laptop?

 

I certainly hope so! To be honest, I cannot tell how much of your problem is because you have the trial version (which has a lower priority for updates than for paid versions), and how much is because the laptop is not always connected to the internet.

What I *can* tell you is how my home computer is working with the paid version. My home computer is set up to a DSL connection via a home router. The router is set to drop the DSL connection if it has been idle for a 5 or 10 minutes (I forget which). The home computer is usually the only one on the network. When I turn my computer off, I usually set it to Standby mode as opposed to doing a full shutdown.

When I turn my computer back on, NOD32 always tries to check for updates (assuming it has been off for over an hour). I can look in my Event Log and see several failed attempts within a few seconds of each other, because the router was still in the process of reestablishing the DSL connection. Once the connection gets established, though, I almost always get updated immediately (assuming there is actually a new version available). For me, it is quite reliable.

By the way, what type of internet connection do you use for your laptop? Ethernet connection to network? Wireless? Dialup?

 

Thanks for your reply-
When I want to connect to the internet, I use an Ethernet cable to a router on my home network. There is a DSL modem connected to the router. Generally, I connect the laptop to the network and then boot up.

I have Nod32 set to auto update when I log on (thinking that it would try at that point). We have Nod32 installed on all our machines at work, but they are always on the network. In that setting, always on, registered software, there is no problem.

 

I always get my update

 

If you buy NOD32 , your registered version will be much much better with no problems . The issue here is most likely related to the fact you are trial user.
Trial users have low priority on ESET servers whereas paid user have higher priority on these servers , which means if a particular server is busy with paid clients , your trial will automatically be rejected with a message " Your NOD32 is up-to-date, no update necessary " although it is not true .

When you was connected to the internet , your NOD may have connected to a server but it was busy so NOD got an answer no update needed .

However , this is less likely to happen with paid NOD32 , I get the updates with no problem now and with pleasure I am looking forward to the new ESET NOD32 v.2.7 and the new servers

 

I done a fresh install of nod32 (paid with license) a couple of days ago, it's set up using Blackspears settings but I haven't received any auto-updates yet, I have to manually press 'update' to get the update and I usually get it straight away when I do this. So this is affecting paid users aswell, hopefully it will all be solved when the new servers are installed.
Regards,

 

The last update is v.1.1797 (20061010). In the same time Avira has released 3 updates this wednesday 11 october, kaspersky more. I think NOD32 relies to much on its heuristic.

 

You might find a report on www.av-comparatives.org called Release rates & signature updates interesting, and it will show you eset actually provides very good levels of signature updates considering the strength of it's heuristics. Also, esets last update yesterday, 1.1797, was large, with nearly 100 signatures.

 

Why do u have 3 update options checked?

 

I originally only had 2 checked, and added the third (after dial-up connection) to see if it would make a difference and fix the issue. It didn't.

 

Londonbeat, if you look in your Event Log, do you have a pattern of NOD32 failing to connect to many servers within a few seconds of each other, with this pattern repeating every hour?

 

Here's a copy of the log I think it is showing what you say, the very top line is when i updated manually:

Time Module Event User
12/10/2006 00:32:34 Kernel The virus signature database has been successfully updated to version 1.1798 (20061011).
12/10/2006 00:22:21 Update Function: gethostbyname, parameters: , return value: 11001
12/10/2006 00:22:21 Update Update attempt failed (Server connection failure.)
12/10/2006 00:22:19 Update Error connecting to server www.nod32.com.
12/10/2006 00:22:18 Update Error connecting to server u7.eset.com.
12/10/2006 00:22:16 Update Error connecting to server u4.eset.com.
12/10/2006 00:22:14 Update Error connecting to server u2.eset.com.
12/10/2006 00:22:12 Update Error connecting to server u3.eset.com.
12/10/2006 00:22:10 Update Error connecting to server u8.eset.com.
12/10/2006 00:22:09 Update Error connecting to server 82.165.250.33.
11/10/2006 23:22:28 Update Function: gethostbyname, parameters: , return value: 11001
11/10/2006 23:22:27 Update Update attempt failed (Server connection failure.)
11/10/2006 23:22:26 Update Error connecting to server www.nod32.com.
11/10/2006 23:22:24 Update Error connecting to server u7.eset.com.
11/10/2006 23:22:22 Update Error connecting to server u4.eset.com.
11/10/2006 23:22:20 Update Error connecting to server 82.165.250.33.
11/10/2006 23:22:18 Update Error connecting to server u3.eset.com.
11/10/2006 23:22:16 Update Error connecting to server u8.eset.com.
11/10/2006 23:22:16 Update Error connecting to server u2.eset.com.
11/10/2006 23:20:53 Update Function: gethostbyname, parameters: , return value: 11001
11/10/2006 23:20:53 Update Update attempt failed (Server connection failure.)
11/10/2006 23:20:50 Update Error connecting to server www.nod32.com.
11/10/2006 23:20:48 Update Error connecting to server u7.eset.com.
11/10/2006 23:20:47 Update Error connecting to server 82.165.250.33.
11/10/2006 23:20:45 Update Error connecting to server u4.eset.com.
11/10/2006 23:20:43 Update Error connecting to server u2.eset.com.
11/10/2006 23:20:42 Update Error connecting to server u8.eset.com.
11/10/2006 23:20:42 Update Error connecting to server u3.eset.com.
11/10/2006 22:20:47 Update Function: gethostbyname, parameters: , return value: 11001
11/10/2006 22:20:47 Update Update attempt failed (Server connection failure.)
11/10/2006 22:20:45 Update Error connecting to server www.nod32.com.
11/10/2006 22:20:43 Update Error connecting to server u7.eset.com.
11/10/2006 22:20:41 Update Error connecting to server u4.eset.com.
11/10/2006 22:20:39 Update Error connecting to server 82.165.250.33.
11/10/2006 22:20:36 Update Error connecting to server u3.eset.com.
11/10/2006 22:20:34 Update Error connecting to server u8.eset.com.
11/10/2006 22:20:34 Update Error connecting to server u2.eset.com.

 

gethostbyname, parameters: , return value: 11001 = Internet connection failure, as in no connection to the Internet can be found.

Cheers

 

same here...
what is the correct and best setting with NOD32 (paid fullversion) for a WLAN Notebook, connected to a Router?
I´ve also trouble with quick automated update for my Notebook.
NOD32 runs update-check before the Notebook is connected to Router/Internet. Against, not before 1 hour later.
The Notebook is not allways online. So I´am with standard update settings late with updates. It´s not very comfortable, to do updates allways manual.
thks for help!
citycruiser (DE)

P.S. sorry for my bad english..

 

Londonbeat, citycruiser....

Try going to Update --> Setup --> Advanced. For the "Internet connection", try choosing "Dial-up" instead of "LAN/fixed line". See if that makes any difference.

 

thks, alglove,
yes, I´ve tried yesterday with update settings to "dial-up connection" - was not helpful.

Or, do I have to change the settings in "System > Scheduler/Planner" from "Regular" to "dial-up" also? I´ve found here at time also settings for update.
Sorry for this question..., I´am pretty new with NOD.

With my LAN PC (cable connection to Router) the update works verry well.
So, hope to find a way also for Notebook.

 

Thanks Blackspear, Ive updated straight to 1.1800 without any problems just now, but I was connected to the internet all night last night so im not sure how 'no internet connection' error comes up
It's working fine at the minute though.

Cheers

 

Yes, try that.

 

have tried the settings for dial up - then I didn´t have any update.
Notebook was longer than 1hour on this morning and I did not get any update.
I´am now with version 11800 and 11802 is out now.
So I go back now to the "regular" setting.

Any other idea, what I can do else, for quick automated updates?
many thks for your help!

 

its running now!
the trouble-maker here was Intel Pro/Wireless connection software!

the connection setup was handled by Intel Pro/Wireless software for Centrino.
after deinstall these software and going back to connection handling by Windows XP, update for NOD32 is running well by start, without failure logs!

 

Thanks for letting us know the outcome citycruiser, it will help someone in the future with the same issue.

Cheers