NOD updates

I have been using NOD32 for some time now (I have 2 current licences, but only use one at this time), with no problems as such.
I have noticed over this time period, that when I perform a manual update, half the time I am informed that "Your version of NOD32 is up to date. No update necessary". which in itself is not a problem, but on my next attempt to update, the update as jumped from, for example, database 1.140 to 1.145, and thought it strange that there would be so many updates in the time period from my last update attempt (I normally make a manual update once a day). Looking into this I have found that I am being given this message "No update necessary" even when an update is available (have been keeping an eye on the "update alerts" thread), and it can take 2 or 3 attempts (one after the other) to be allowed to update from the server to the latest database release.
I have checked to see if NOD is actually contacting the server when I am being given this incorrect info, and there are no connection problems, I have also re-installed NOD onto a fresh install of windows (in case of any possible corruption, or conflicts), but this "No updates necessary" continues, altough updates are available.
I can only assume from this, that the server may be busy when I attempt to update, and is simply knocking me back from the updates due to this,...... which I would certainly not be happy with,... as I should not be informed that NOD is up to date,...when it is not.

 

First of all, the update server must be set to Choose automatically unless you update from your LAN mirror. If you still get this message, then the NOD32 registry entries must have been tampered with (e.g. you ran a reg file to import old settings).

 

Alway been set to auto for update server. (and as mentioned, the connection to the server are establised)

No,..as I mentioned, I re-installed on to a clean XP installation,...... no reg utilities used.


EDIT
I will E-mail support

 

Hello again,
I am still having this problem with updating. My system has no connection problems, and the NOD servers are being connected to (all trafic is logged externally).
As I mentioned in my first post, I update manually, I had not updated for 2 days, so on seeing the update alert (in the forum updates) I decided to update,.. this took me 16 attempts. Now if the problem was my setup, be it within NOD or my OS, or even my firewall, I would expect the problem to be constant, not intermittent. I cannot see the reason for these problems apart from at the server end, (somtimes I get update first time, other times 3 or 4 attempts, this attempt 16)

Pic from one of my last attempted updates (I did manage to update, 2 attempts after the screen grab)
Regards

 

Hi Stem,

I sort of notice the same thing. Occasionally, when I check the "Event Log", I will see an "Error connecting to server u1.eset.com" message (for Event) with the Module marked as "Update".

When I just manually checked for an update, I got the same message as you: ""Your version of NOD32 is up to date. No update necessary", even though I am at version 1.1677 (20060724)....when, as your screenshot shows, the "latest" update in dated 20060725, with a release version of 1.1678.

Of course, I am running the "trial"...so that may explain why I may be a little behind on my PC....

 

Hi JRCATES,

I do not know of any "Priority" on updates from the "full" or "trial" (I currently have licence), I just think that if the server is busy (possibly backed up with the recent large update), then the user should be informed of this, not misinformed with the "popup" that "No update necessary" (NOD made server connection on each attempt)

 

Hi Stem,

Well, according to Marcos...there IS a "higher priority" according to registered versus trial users:

https://www.wilderssecurity.com/showpost.php?p=803944&postcount=51

Guess that answered that!

 

I think this just needs a change in the pop up message to avoid any confusion in future. Not a big deal here as mine updates soon enough.

 

Hello!

I have the same problem on 2 computers. Try to change update server. Works for me.

 

You can also download the latest commercial version, it already has the large update embedded.

 

Hi Marcos
Are you sure that this download
http://www.eset.com/download/registered_software.php
has the last update 1.1678 or 1.1679?

 

Yeah I'd like to know that too. I want to dl a spare copy. In case I have to reinstall. Thanks.

 

Great work, ESET Team!

At least, the data time of the file is from today...

 

If Marcos says it is so, then it is so, as he would know

Cheers

 

I've checked the engine version in the latest commercial installers and it was actually 1.1678. Though it's 2 versions behind, it was not possible for me to create an engine with all incremental updates and embed it to the installers. Anyway, paying users should no longer experience problems updating (I'll check the situation with my colleague) and trial / cracked version users will be enabled to download updates shortly. As you know, we plan to install new update servers soon. Given that such large base updates occur 3-4 times a year, I assume problems with updating should be definitely gone then.

 

Unfortunately it's impossible to distinguish between trial and cracked version users.

 

My thoughts EXACTLY!!!

 

Oh well I guess we have to keep them happy, image the complaints if their cracked versions wouldn't update

 

I think we've already seen some of them here recently

I'm not saying that all of those complaining were using a cracked version, but I'm pretty sure at least one of them was.

 

Well, one things for sure....it wasn't me!!!

I'll be the first to admit....I'm not smart enough to know how to "crack" any software!!! Heck, I just had a difficult enough time following Blackspear's suggested settings thread to set the darn thing up!!!!!!!

 

I think he was reffering to me

I did it that way just for you, don't want to make it simple you know, then anyone would be able to follow it

 

I don't use cracked versions!!!

 

No, I think he was reffering to me and my version of NOD32, one of these days I'll have to pay for it, though this version does update for 4 million years

 

Any Av system, for whatever reason, which erroneously reports sig. files as up to date is not competent and shouldn't be let near any computer system holding important data!

I would have liked to have tried it properly, but dispite assurances that the trial product would update today, it still gives false and misleading 'up to date' sig. reports. With regret, as I think it could otherwise be the product for me, this rules out NOD32.

The smugness and idiocy of those receiving updates as paid subscribers, but who don't appear to understand the inherent dangers, and unacceptability, of any system which allows false update reports in principle, is mind blowing.

Sadly, AVG is being installed now.