NOD updates

[Stem]

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.

[Marcos]

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

[Stem]

-{ Quote: "First of all, the update server must be set to Choose automatically unless you update from your LAN mirror." }-Alway been set to auto for update server. (and as mentioned, the connection to the server are establised)
-{ Quote: "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)." }-No,..as I mentioned, I re-installed on to a clean XP installation,...... no reg utilities used.


EDIT
I will E-mail support

[Stem]

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

[JRCATES]

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

[Stem]

Hi JRCATES,
-{ Quote: "Of course, I am running the "trial"...so that may explain why I may be a little behind on my PC...." }-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)

[JRCATES]

-{ Quote: "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:

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

Guess that answered that! :P ;D

[Joliet Jake]

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.

[izi]

-{ Quote: "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)" }-

Hello!

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

[Marcos]

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

[guilijan]

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?

[zapjb]

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

[rdsu]

Great work, ESET Team! :P

-{ Quote: "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?" }-
At least, the data time of the file is from today... ;)

[Blackspear]

-{ Quote: "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?" }-If Marcos says it is so, then it is so, as he would know ;) ;D

Cheers ;D

[Marcos]

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.

[Blackspear]

-{ Quote: "...and trial / cracked version users will be enabled to download updates shortly." }-:blink: :dry: :blink: :dry:

[Marcos]

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

[JRCATES]

-{ Quote: "-{ Quote: "...and trial / cracked version users will be enabled to download updates shortly." }-:blink: :dry: :blink: :dry:" }-

My thoughts EXACTLY!!! ??? :P

[Blackspear]

-{ Quote: "Unfortunately it's impossible to distinguish between trial and cracked version users." }-Oh well I guess we have to keep them happy, image the complaints if their cracked versions wouldn't update :blink: ;) ;D

;D ;D ;D

[Marcos]

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

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.

[JRCATES]

-{ Quote: "I think we've already seen some of them here recently ;D

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!!!!!!!:blink:

[Blackspear]

-{ Quote: "Well, one things for sure....it wasn't me!!!" }-I think he was reffering to me :blink: ;) ;D :lurking:


-{ Quote: "Heck, I just had a difficult enough time following Blackspear's suggested settings thread to set the darn thing up!!!!!!!:blink:" }-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 :blink: ;) ;D


;D ;D ;D

[izi]

-{ Quote: "I think we've already seen some of them here recently ;D

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

I don't use cracked versions!!!

[Blackspear]

-{ Quote: "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 :blink: ;) ;D :lurking:

;D ;D ;D

[henryg_1]

-{ Quote: " 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. " }-

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.

[Blackspear]

-{ Quote: "Sadly, AVG is being installed now." }-I think this is a good idea.

Blackspear.

[mantra]

hi
my friend tried to update a trial version , but the program don't want to update!

why?

[Edwin024]

The paid for version did not update too. 180 was out, I had 179 and the updater told me that it was correct. When I chose to go for the server with only the IP number things went smoothly and 180 ws installed... Not good at all, that update server thing.

[the_sly_dog]

trial version guys all stop moaning gees :o :o :o :o :o :o :o


eset are doing all they can to resolve the minor problem

if you dont like it then switch to another av software and moan on there forum please and tell them how u have issues with the way it works :thumb: :thumb: :thumb: :thumb:



i have heard that too that BLACKSPEAR IS USING DODGY NOD32 lol

atleast he owned up at last lmao

[mantra]

now i'm looking to my nod , paid version , and it's blocked it doesn't want to update too :-(



-{ Quote: "if you dont like it then switch to another av software and moan on there forum please and tell them how u have issues with the way it works
" }-

hi man i paid for this av , why should i drop it ???? >:(

[the_sly_dog]

mantra i never said you... i have paid version too,,


i just meant trial version or cracked versions people stop getting so stressed out about getting the update

[mantra]

ahh
sorry for misapprehension:-X ;D

[Marcos]

The update servers have been operating normally for a couple of hours, paying users should get updates immediately.

[Edwin024]

-{ Quote: "mantra i never said you... i have paid version too,,


i just meant trial version or cracked versions people stop getting so stressed out about getting the update" }-

It looks like a good point, but it isn't. If people try a software package and it doesn't do what it should do the company involved doesn't get a new client. I don't think that that is what eset wants, do you?

And as I already wrote: I had this problem too, with my paid for version, that is good until January 2008.

[Smokey]

-{ Quote: "The update servers have been operating normally for a couple of hours, paying users should get updates immediately." }-
Marcos,

why different update servers for paying and eval-users?
At this time, it just don't make sense to me???

Txs in advance for the explanation!;)

[pykko]

-{ Quote: " and trial / cracked version users will be enabled to download updates shortly. " }-

Wow...This is why I like ESET....they support even users having cracked versions. ;D ;D :o ::) 8)
Anyway, could I submitt some working cracks to ESET ? I"ve submitted once one and no reply. :(

[alglove]

-{ Quote: "It looks like a good point, but it isn't. If people try a software package and it doesn't do what it should do the company involved doesn't get a new client. I don't think that that is what eset wants, do you?

And as I already wrote: I had this problem too, with my paid for version, that is good until January 2008." }-
Or to put it another way, a user decides to install the trial version of NOD32 to see how he likes it. Problem is, he happens to install it at a time that the update servers are extremely busy, so he does not get an update until several days later. Is this going to make the trial user feel that he is getting "up-to-date" virus protection? Probably not.

As Marcos has said, large updates such as these only happen 3-4 times per year. The new update servers should be up and running by then, so hopefully this will not be a problem again. :wacko:

[Marcos]

And hopefully cracked versions will be eliminated at that time which will give more resources to trial users :P

[ASpace]

-{ Quote: "And hopefully cracked versions will be eliminated at that time which will give more resources to trial users :P" }-

Oh , I really hope so !:thumb: How do you plan to do it - something new into the servers or what ?
When this happen , please give more info , I'll then have some more clients,criminals who now use cracked NOD32 but don't to pay for it and claim NOD32 is free software .When their cracks become useless , I hope they will pay for it :)

NOD32

[Brian N]

I understand that trial users are supposed to try a fully functional product before purchasing it, because if something fails, they're most likely not going to to buy it (I wouldn't in most cases).

On the other hand, I do not want to get my updates later because some trial/crack users are sucking the life outta the servers - I do pay for the updates you know so I want first priority regardless of what people think.

So more servers or just dedicated trial servers is a good idea in my book.

[JRCATES]

-{ Quote: "mantra i never said you... i have paid version too,,


i just meant trial version or cracked versions people stop getting so stressed out about getting the update" }-

You'll be eating those words if some trial (or registered) user gets infected by something that the latest definition updates would have prevented!!!

Besides...let's be honest. TRIAL USERS are doing just that: Taking it on a TRIAL RUN!

If you were test driving a car.....and the car started having problems in the middle of your test drive, would you be really anxious to BUY that car???

Trial (and registered) users have a right to be upset. A little common courtesy (and sense)....PLEASE!!!

[Edwin024]

I fully agree with you. It's like having a test car and after 50 miles the left tires fall off. Hazardous and a reason not to buy that car ever. And I'm a licensed user until January 2008...

[Brian N]

--------------

[PigBrother]

After 2 days without updates (I think as a registered user, it's a two month licence from a local Eset retailer) I've just received a bonus :D

http://img65.imageshack.us/my.php?image=bonusfs5.jpg

The update has been downloaded few minutes ago from u3.eset.com

[guilijan]

-{ Quote: "After 2 days without updates (I think as a registered user, it's a two month licence from a local Eset retailer) I've just received a bonus

http://img65.imageshack.us/my.php?image=bonusfs5.jpg

The update has been downloaded few minutes ago from u3.eset.com" }-Wooow you have the antivirus of the future.

[Littlemutt]

At least AVK on their download page states: it contains no updates.

[pykko]

-{ Quote: "After 2 days without updates (I think as a registered user, it's a two month licence from a local Eset retailer) I've just received a bonus

http://img65.imageshack.us/my.php?image=bonusfs5.jpg

The update has been downloaded few minutes ago from u3.eset.com

Wooow you have the antivirus of the future." }-
:blink: :o :blink: That's even more interesting than I thought. ESET delievers dicriminating updates . ;D ;D I think those servers are really exhausted. You should give them a break. :P
mm...this is not so funny...I"m trying to get the 1.1682 update and nothing. :(

[RejZoR]

I also can't get 1.1682 for like an hour. NOD32 keeps on insisting that i'm up to date even though i'm certanly not. Commercial registered version here... ::)

Same happened when i installed NOD32 from scratch. Security Center was screaming that NOD32 is out of date but NOD32 was insisting that everything is up to date. Right... After insane 5 clicks it finally updated.
No such luck with this latest update...

[Stem]

Marcos,
-{ Quote: "Anyway, paying users should no longer experience problems updating (I'll check the situation with my colleague) " }-I am still being mis-informed that "No update necessary" which as been the same since my original post on this matter, at which time you stated:-{ Quote: "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)." }-As I had/have NOD server settings as "Choose automatically" you inferred that I must of "tampered with the registry entries", I have still not received any other direct reply from you on this.
Now on the same thread that I started, you are stating:
-{ Quote: "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." }-Are you now making an attempt to say that I am using a "cracked version" and that is why I am unable to update?

[fred22]

-{ Quote: "I also can't get 1.1682 for like an hour. NOD32 keeps on insisting that i'm up to date even though i'm certanly not. Commercial registered version here... ::)" }-

+1..its getting little annoying to... :thumbd:

[Smokey]

-{ Quote: "Are you now making an attempt to say that I am using a "cracked version" and that is why I am unable to update?" }-
Stem,

you belong to the lucky ones, i assume your database is maybe some days "old".

Honest trial-users have to deal with a database more then 1 month old.
IMHO it is highly irresponsible behavior direction trial-user.

[jg88swe]

Well,
Seriously there are issues regarding these big updates the first 24h with Commercial and trial versions of NOD32 antivirus.

But I'm glad you guys have decided to solve it with new servers.

I don't know marcos but latley it feels like you've become suspicous to everyone regarding of they are using a genuine version of NOD32.

Maybe you guys should have a discount for those pirates that wants to become clean ;) .. jk

[supergravy]

I was running two pc's with paid nod32 and one other with a trial. As of an hour ago none would update. This whole update issue along with some of the responses really left me feeling sour. So... I went ahead and took the offered advice and uninstalled the trial ~snip~ this is the NOD32 Support Forum ~ Blackspear

[Heco]

Hi all,
Now as for me, it is impossible to get the 1.1682 database:o . Already to get the 1.1680 database, i had to click 15 times on the "update now" button:blink: ; for database 1.1681, i had to click 50 times to get it:dry: . How many clicks are necessary to get the 1.1682? LOL. From now on to get updates, the number of clicks will increase exponentialy? LMAO
Yet i am a regular registered user and NOD32 is set to get updates automatically...:(
Thanks for your reply.
Cheers,
Hervé

[The Hammer]

Everything is running as smooth as silk here as far as updates are concerned.:)

[Blackspear]

-{ Quote: "Now as for me, it is impossible to get the 1.1682 database" }-Mine is sitting on 1.1681, however I do know it will update at some stage.

Cheers ;D

[Heco]

Thank you Blackspear for your reply:) .
Argh... patience is not my main quality... LOL
Let's wait then till the miracle operates;D. I will keep repeating to myself "It will update, it will update..." when going to bed;D
Cheers,
Hervé

[basti]

-{ Quote: "Mine is sitting on 1.1681, however

Cheers ;D" }-

Yep, mine is still sitting on 1.681 ???

@marcos :o

[Marcos]

Mine's too, but I don't assume this has something to do with the load of the update servers. We're on it.

[Marcos]

-{ Quote: "
Are you now making an attempt to say that I am using a "cracked version" and that is why I am unable to update?" }-

Hi Stem,

I meant a completely different person, not you. Sorry, I didn't realize you may take it personally since you started the thread.


Marcos

[Osaban]

Hi there,

I just wanted to say for the record that my updates have always been very regular and never needed a manual prompt.

However lately with the massive update of 1.1678 it stopped for a couple of days and I had to update manually. It is now regular again i'm upto 1.1682, but something was definetly strange.

[Lucy85]

Good day to you all, i'm a trial user but don't have problems updating to latest virus database with the server below, perhaps you guys can try that instead of let it choose automatically.

http://img135.imageshack.us/img135/8079/0000dw7.th.png (http://img135.imageshack.us/my.php?image=0000dw7.png)

[Blackspear]

Hi Lucy85, welcome to Wilders.
-{ Quote: "Good day to you all, i'm a trial user but don't have problems updating to latest virus database with the server below, perhaps you guys can try that instead of let it choose automatically." }-It is best to leave Servers on "Choose Automatically".

Cheers ;D

[supergravy]

I was frustrated, apparently did some spruiking and made some changes to my av choices. Regardless, I second Blackspears advice to leave servers on automatic.

I suspect the update issue may be resolved as my two pc's running NOD finally updated, as have a couple of clients machines that were running trials.

[Blackspear]

-{ Quote: "I was frustrated, apparently did some spruiking and made some changes to my av choices." }-That's ok, just have to remember this is the "NOD32 Support Forum".

Cheers ;D

[Nunes]

I've been reading with attention all the posts of this thread because I'm unsure about how the update process happens:

I'm now at my office, it is 9 AM and yesterday at home NOD was at update 1.1681 when I detected that update 1.1682 was ready I tried manually but got always the response that NOD was updated.

My question is:

When you get the answer that it is updated, that means that NOD was able to contact the server and received the answer that no new update was available ?

or

you can get this answer even if NOD is unable to contact the server?

and if you try manually and the contact is not possible do you get an event notifiction at the log?

This is because I attempted to update manually and I got the message that NOD was still updated but there was no new lines at the event log. It seems that the server contact was possible or not?

And if the contact is possible why do I receive the message that NOD is still updated but I know that it is not?
If the server is loaded with a new update and the contact is made (I don't have any lines is event log with missing contacts) why this kind of message?

[Brian N]

-{ Quote: "When you get the answer that it is updated, that means that NOD was able to contact the server and received the answer that no new update was available ?" }-
Yes.

-{ Quote: "you can get this answer even if NOD is unable to contact the server?" }-
No.

-{ Quote: "and if you try manually and the contact is not possible do you get an event notifiction at the log?" }-
Correct.

-{ Quote: "It seems that the server contact was possible or not?" }-
It was, otherwise you would have seen it in the log or a notification would popup if no connection could be made to any server.

-{ Quote: "And if the contact is possible why do I receive the message that NOD is still updated but I know that it is not?
If the server is loaded with a new update and the contact is made (I don't have any lines is event log with missing contacts) why this kind of message?" }-
Could be overloaded or server was not yet updated with the new defs.

[actarus9999]

Hello everybody,

Having been a registered user since I saw benefactions fact to my system with the trial version I am to ask the question but why thus rest it blocks on the definition of virus 1.1677 but by reading your topics I noticed that that did not come from me but from servers. Now I followed an advice that is to kidnap my version and to put a piece of news what I made. But here is impossible for me to pass to the version 1.1682 this morning. I arrived but at the end of 50 attempts there as said it precedly Hervé. I hope that it is not my license which seen bug which I changed operating system recently.

See ya

Actarus

[pykko]

I've updated to 1.1682 finally. IT's not your license actarus9999. It's a general problem.

[ASpace]

-{ Quote: "
Having been a registered user since I saw benefactions fact to my system with the trial version " }-
How much time have past since you paid for your NOD32 ?

When you paid for it , did you removed the trial version and installed the full version with your unique username and password ???

-{ Quote: " But here is impossible for me to pass to the version 1.1682 this morning." }-

This is very unlikely . As Marcos said there is no longer issues with the servers . I can also confirm , everybody at my office updated successfully to 1.1682 and everything is fine.

-{ Quote: " I hope that it is not my license which seen bug which I changed operating system recently. " }-

Details ... pls :)

[Blackspear]

One off topic post removed.

This is the "NOD32 Support Forum".

Blackspear.

[actarus9999]

-{ Quote: "How much time have past since you paid for your NOD32 ?
I have it to buy late in the year last one.

When you paid for it , did you removed the trial version and installed the full version with your unique username and password ???

No I did not make that because I have to enter my unique(only) username and my password directly the configuration of the update.



Details ... pls :)" }-

Having learnt that Windows 98SE would stop being updated from July 11th I thus convinced myself that I had to hand on to XP professional Sp2 even if it turns out that I already had to try to install it on my system but he had been able to work correctly.

[Gez]

My goodness! I just checked my NOD and it was last updated on the 23rd of June!
181785
Yet I had been getting the balloon notification every day or two that my antivirus was up to date! What's going on? I had trusted that NOD was doing its job and therefore I didn't check more closely till I stumbled across this thread. I've downloaded the recent installer and that seems to have corrected it, partly at least -- I'm now on 1.1678.
This is scandalous, and I really don't want to hear patronising and condescending comments by anyone that I haven't set my NOD up properly, or worse, that I have a cracked version installed. Yes, I relied on automatic updating, but with 5 or 6 servers I should think people shouldn't have to double-check by manually updating anyway.
Well well well! This really has changed my view of NOD, and I was so happy with it too. How can I depend on it from now on?

[Blackspear]

-{ Quote: "My goodness! I just checked my NOD and it was last updated on the 23rd of June!" }-Did you have your Servers as "Choose Automatically"? As no updates for a month talks of something very different to that of the large update issue.

Cheers ;D

[webyourbusiness]

-{ Quote: "
-{ Quote: "
When you paid for it , did you removed the trial version and installed the full version with your unique username and password" }-

No I did not make that because I have to enter my unique(only) username and my password directly the configuration of the update." }-

This is your problem - and I'm sure that your welcome email contained the instructions to do this. Unless you have a VERY RECENT trial version, it was always necessary to remove the trial PRIOR to inputting the username/password - just putting the new username and password into the trial was not sufficient, and updates still stopped being installed. Thankfully Eset has recently changed this, because it caused no-end of problems, like it seems to have done with you.

Just remove your NOD32 - re-download the COMMERCIAL version with your username/password from:

http://www.eset.com/download/registered_software.php

and setup and enter your registered username/password. Updates will be fine from then on. Sorry - but that just a fact until recently that this step is necessary - and I'm 99.9% sure it would have been in the email you received if you ordered from Eset or a reseller such as us.

hth

Greg

[webyourbusiness]

-{ Quote: "I've downloaded the recent installer and that seems to have corrected it, partly at least -- I'm now on 1.1678." }-


Are you sure you downloaded the full version, not the trial?

http://www.eset.com/download/registered_software.php

[Gez]

Update to last post -- I had to try manual update three times before I finally got my NOD up to 1.1682. This despite NOD telling me my antivirus had been automatically updated, to 1.1678.
Time to look for a more reliable antivirus I think. I can't rely on a product that tells me I am up to date when in fact I am over a month out of date. My system is critical to me as I use it to clean other people's disks. I am very disappointed with this indeed. Very disappointed. I bought NOD on the basis of the many recommendations in this forum, and on the helpfulness of people here. That trust has now been dashed by this update fiasco AND by the condescending replies of people here who treat ordinary users so flippantly by dismissing so blithely their legitimate concerns.

[webyourbusiness]

-{ Quote: "That trust has now been dashed by this update fiasco AND by the condescending replies of people here who treat ordinary users so flippantly by dismissing so blithely their legitimate concerns." }-

Sorry you feel that way...

[Heco]

WOW! Everything back to normal here as concern the updates:D .
Thank you Blackspear for your wise advice and Marcos for repairing the servers.;D
Cheers,8)
Hervé

PS: Database is 1.1683 now. Hurrah! LOL

[Gez]

Yes -- the servers were set to choose automatically. And I have since reinstalled with the new installer, and after 3 attempts have been able to bring it finally up to 1.1682. So no issues with firewalls or other software preventing updates.

[Gez]

Yes thank you. But ordinary users who don't have time to check all of these things out shouldn't have to do this kind of thing. If the antivirus is set to update automatically it should do so. It certainly should never go out of date by more than a month.

[Gez]

Well how would you feel? It's only half an hour or so since I found out my antivirus was over a month out of date! Yes, I was stupid not to check, but I have a lot to do, and the one piece of software I really trusted on this machine was NOD! I was told every day or two my antivirus had been updated to latest version so why should I think any differently. I can understand if there are update issues over a day or two, or even over a few days, but a month? And the fact that I have now resolved it by installing the latest version from the website suggests that it wasn't an issue with my system or my firewall.
Agreed?

[webyourbusiness]

-{ Quote: "Yes thank you. But ordinary users who don't have time to check all of these things out shouldn't have to do this kind of thing. If the antivirus is set to update automatically it should do so. It certainly should never go out of date by more than a month." }-


I agree, but AV / anti-spyware and windows networking are a complex set of interacting systems, the basic questions have to be asked and obvious answers eliminated before proceeding to the more complex issues that may be at hand. This occassionally comes across wrong in forums, as tonality can be be interpretted where there is none - and that can make you think a response is condescending when it was not inteded to be so. I'm glad you got that update, and to be honest, I had troubles getting 1.1682 myself, and I am still not sure why - I don't see that as a critical problem, as it's just one small update, and when I got up at 1AM to make some ticket reservations, the update had come down - problem solved.

However, a month of failed updates would have had me jumping round the room with frustration too - and getting to the bottom of it is not going to be easy once the update has been forced down. Watch the update versions and if you don't have the update within say, 4 hours of the update happening, please post back here.

[Gez]

Well thank you very much. You've calmed me down a bit!
;D
It's only come to my attention, so naturally I am livid, but as you say there could be other issues which need to be checked first before I jump down Eset's throat!

[webyourbusiness]

lol - computers have a way of doing that to people - I sometimes question my sanity and choosing them as a career option! ;)

[Suggers]

Updating fine now at my end. :)

[supergravy]

-{ Quote: "Well thank you very much. You've calmed me down a bit!
;D
It's only come to my attention, so naturally I am livid, but as you say there could be other issues which need to be checked first before I jump down Eset's throat!" }-

I enjoyed your posts as I went through the same reaction. Even managed to buy another AV program in the process and type out a post that was edited. It was pointed out (nicely) that this is the nod32 support forum. Problem is, I really did not feel very supported. Instead, I felt as though some were indirectly accusing me of using a cracked version or otherwise doing something wrong or incorrectly. So not only were none of my 3 pc's up to date but my internet feelers were now drooping. Fortunately with a little time all of the following happened:

- the person I thought the most guilty of accusations (and another I greatly respect) soon admitted their pc's hadn't updated either. Hmm... guess cracked machines weren't the only ones not updating. And if cracked versions are a big issue, I tend to think the nod folks should be finding a way to fix it. It is not the fault of paying customers or honest trial users.

- I became aware of a great alternative AV program that I am now really enjoying. There are consequences when issues like this update problem occur.

- ESET seems to have fixed the problem - woo hoo!

[Gez]

-{ Quote: "I enjoyed your posts as I went through the same reaction. Even managed to buy another AV program in the process and type out a post that was edited. It was pointed out (nicely) that this is the nod32 support forum. Problem is, I really did not feel very supported. Instead, I felt as though some were indirectly accusing me of using a cracked version or otherwise doing something wrong or incorrectly" }-
I have paid for three of the top-rated antivirus products, and until now have been using NOD for real-time scanning and the other two for on-demand scanning. I liked NOD for real-time because it was lightweight, and its heuristic capabilities are, we are told, second to none. But my big problem with what has happened today isn't the failure to update; it's the breach of trust which occurs when you are told your antivirus has been updated when in fact it hasn't. For over a month? And the second problem I have which makes me furious is the insinuation that most people who can't get the updates are using trial or cracked versions, or don't have their update policy set up correctly. This is unforgivable in my opinion.
-{ Quote: "- I became aware of a great alternative AV program that I am now really enjoying. There are consequences when issues like this update problem occur." }-
I'm going to have to reassess my security now. I had absolute faith in my antivirus -- stupidly, I hear some people say. This machine is used to clean other people's disks, and I can't risk getting infected because something as simple as updates isn't working properly. The machine is also used to test many security products, and to test lots of software, so it's critical that I can trust my antivirus. I really am disappointed now. Really disappointed.

[Stem]

-{ Quote: "Hi Stem,

I meant a completely different person, not you. Sorry, I didn't realize you may take it personally since you started the thread.


Marcos" }-Hi Marcos,.. Yes thanks,.. I did find after my posting, that posts had been removed, and that you could be referring to them,.. so sorry for "Jumping to conclusions" on my part.

[larryb52]

I updated earlier this moring after the machine came on, it said updated to 7/28?, I'll have to check to see what version when I get home...

[Blackspear]

Ladies and Gentlemen, what you have seen here over the last few days is so extremely rare, in fact you will see if you search the forums that this happened about 2 years ago, the consequence of which were further update servers added. The issue is caused by exponential growth, and that growth has to be managed, in this case it was let slip, more servers should have been brought online earlier and then the very unusual large update rolled out, as such this issue would not have been seen.

As a result of the above there are more servers being added, and I'm pretty sure Eset would have learnt a great deal from this experience, that in 2 years time we will not go through the same exercise.

Cheers

Blackspear.

[smith2006]

-{ Quote: "Ladies and Gentlemen, what you have seen here over the last few days is so extremely rare, in fact you will see if you search the forums that this happened about 2 years ago, the consequence of which were further update servers added. The issue is caused by existential growth, and that growth has to be managed, in this case it was let slip, more servers should have been brought online earlier and then the very unusual large update rolled out, as such this issue would not have been seen.

As a result of the above there are more servers being added, and I'm pretty sure Eset would have learnt a great deal from this experience, that in 2 years time we will not go through the same exercise.

Cheers

Blackspear." }-

I concur with Blackspear & let's move on! :)

[Beer Dog]

-{ Quote: "...The issue is caused by existential growth, and that growth has to be managed...
Blackspear." }-

Maybe you're a follower of Jean-Paul Sartre, but isn't the problem a result of exponential growth? :)

Nitpicking aside, your comments are appreciated.

[Heco]

-{ Quote: "Maybe you're a follower of Jean-Paul Sartre, but isn't the problem a result of exponential growth? :)

Nitpicking aside, your comments are appreciated." }-
LOLLL...
I'm imagining this philosopher and writer who said "Words are loaded pistols", computing side by side with S. de Beauvoir and trying to update NOD32 if they both were still living....;D
Really too funny LOL.
Cheers,
Hervé

[Blackspear]

-{ Quote: "...isn't the problem a result of exponential growth? :)" }-Indeed, and now corrected ;) ;D


-{ Quote: "Nitpicking aside, your comments are appreciated." }-My pleasure.

Cheers ;D

[DarkStar251]

I think the issue here is NOT that the update servers had problems etc, its that when the software cannot connect to the servers during an automatic or manual update it does not seem to alert the user to this, without looking through logs etc.

When you click 'update now', it should NOT state 'your version of nod32 is up to date', it should state 'could not connect to update server' or 'update server is busy try again later'.

The fact that the software lies to you and states that it is up to date, is the breach of trust people are talking about, and an update to the software must be released to change this behaviour.

That said, all people and companies are allowed a few mistakes, and NOD32's record up to now is totally impeccable imho.

Such a small and easily fixed problem is not a reason to switch AV software for me unless it is allowed to fester.

[Brian N]

-{ Quote: "When you click 'update now', it should NOT state 'your version of nod32 is up to date', it should state 'could not connect to update server' or 'update server is busy try again later'." }-
You'll only see that message when it has made contact to a server.
If it can't connect to any server at all, you'll see an alert notification.

It'll look like this:

[DarkStar251]

Well something doesnt tally up when the message on a manual update says 'Your Version of NOD32 is up to date' and the log says 'Update attempt failed (Server connection failure)'.

I can only assume this is because of a busy server when spamming the update button fixes it :)

Either way, in and of itself this isnt enough of a reason to stop me being a NOD32 customer, as I have said, I just think the messages should tally up, and that there should never be a situation where the software reports that it is up to date when it is not. Better to report that the update failed than that the software is already up to date.

[JRCATES]

-{ Quote: "You'll only see that message when it has made contact to a server.
If it can't connect to any server at all, you'll see an alert notification.

It'll look like this:" }-

Actually, Brian....I can concur with DarkStar here. In my case (and from the sound of it, several others as well)....no connection was made to a server (in the event log, I continually got the red exclamation icon with the words "Error connecting to server u1.eset.com" whenever I tried to manually update)....yet I was continually greeted with the pop-up window saying "Your version of nod32 is up to date. No update necessary"....

I agree this isn't a reason to drop NOD, just something that should be addressed for future changes....

[cerBer]

It is really funny, this attitude of Eset - both here and @email support too.

First, it is probably difficult to get, but nobody is going to attack you - there simple isn't point in that. So, there is no reason to take a deep defense.
Also, it is clear that by posting here most users are actually trying to help Eset.

O.P. clearly didn't complain about late updates, but pointed out the fact that NOD reports itself up-to-date, when it is actually not.
It is NOT something that happens once in two years. It happens all the time and one can reproduce this behaviour easily, if he really wants to understand what is going on. And it does not matter if NOD updates successfully 5 minutes later on not(as it happens once in 2 years) - it is BUG anyway.

So, why there is no straight answer from Eset? Is it really that after paying for software, spending time to find bug, user still needs to be insulted by some Eset moderator or support staff, who will better pretend dumb than admit the truth? (by insult I mean endless need to answer stupid questions when all it takes is to check own product).

The same stands for never ending moaning about 'cracked versions'.
One doesn't need to be an expert to see how bad NOD's protection is. It is actually completely laughable.
So, users are most likely paying because they are honest and do not deserve listening that BS, just because Eset didn't properly protect their product.

[PigBrother]

Erm, first of all I'm a Kaspersky user and now a two months demo version NOD32 user.

In my humble opinion something is pretty wrong with some users attitude. "Lost of faith", "lost of trust", "lost of whatever you like" are just granma complains.
As a decent user, some people should know that everything fails.
Kaspersky screwed up updates features few hours after version 6 launch, TrendMicro screwed up badly some things last year with an untested update that caused 100% CPU usage after start-up and another one who detects some IRC clients as threats, Symantec screwed up badly with some flaw in scanning engine that caused execution of malware instead of deletion and so on.

So, everything fails one day or another.
If you change an application on first error you'll finish soon out of applications. There is no such perfect thing.
As a personal conclusion: offer reasonable solutions, give feedback, wait for a fix and relax. Is not a hole in the ozone layer, is not a H bomb in Paris and is not a bloody alien invasion.
Thank you.

[The Hammer]

-{ Quote: "Erm, first of all I'm a Kaspersky user and now a two months demo version NOD32 user.

In my humble opinion something is pretty wrong with some users attitude. "Lost of faith", "lost of trust", "lost of whatever you like" are just granma complains.
As a decent user, some people should know that everything fails.
Kaspersky screwed up updates features few hours after version 6 launch, TrendMicro screwed up badly some things last year with an untested update that caused 100% CPU usage after start-up and another one who detects some IRC clients as threats, Symantec screwed up badly with some flaw in scanning engine that caused execution of malware instead of deletion and so on.

So, everything fails one day or another.
If you change an application on first error you'll finish soon out of applications. There is no such perfect thing.
As a personal conclusion: offer reasonable solutions, give feedback, wait for a fix and relax. Is not a hole in the ozone layer, is not a H bomb in Paris and is not a bloody alien invasion.
Thank you." }-Very well said.8)

[guilijan]

-{ Quote: "and now a two months demo version NOD32 user" }-Woow how can you do it? Two months? Are you using a cracked version?

[The Hammer]

-{ Quote: "and now a two months demo version NOD32 user

Woow how can you do it? Two months? Are you using a cracked version?" }-Trials beyond 30 days have been offered before in some countries. It's a little crass to jump to the conclusion the version is cracked.

[guilijan]

The tial version are only 30 days full operative.
But as you said, where can I download a 60 days full operative version?;D ;D ;D

[PigBrother]

It's a 60 days demo version from a local Eset reseller.
It comes on a CD-ROM with a serial number which must be activated on Eset site to get a user/password available for two months.

[guilijan]

Can you give me mails off some of that resellers?
So I can ask for one copy for me.

[The Hammer]

-{ Quote: "Can you give me mails off some of that resellers?
So I can ask for one copy for me." }-You are best served by checking with resellers in your own country. They are available on the Eset site.

[guilijan]

You are best served by checking with resellers in your own country. They are available on the Eset site.

Yes but no one in my country and no one in ESET (web page) gives 60 days demo, only 30 days.
So I ask you again, can you give me some mails from some resellers so I can ask for one copy?

[The Hammer]

-{ Quote: "You are best served by checking with resellers in your own country. They are available on the Eset site.

Yes but no one in my country and no one in ESET (web page) gives 60 days demo, only 30 days.
So I ask you again, can you give me some mails from some resellers so I can ask for one copy?" }-It looks as though you will have to move to Romania at the present time.

[Detox]

-{ Quote: "You are best served by checking with resellers in your own country. They are available on the Eset site.

Yes but no one in my country and no one in ESET (web page) gives 60 days demo, only 30 days.
So I ask you again, can you give me some mails from some resellers so I can ask for one copy?" }-

You've already said in more than one earlier post that you don't want to use NOD ever again anyway.

[guilijan]

Oh Dracula*puppy* *puppy* *puppy*

[guilijan]

You've already said in more than one earlier post that you don't want to use NOD ever again anyway.

And who said that it will be for me?

I have many enemies too.

[Detox]

Right... makes perfect sense, that. :lurking:

[smith2006]

-{ Quote: "The tial version are only 30 days full operative.
But as you said, where can I download a 60 days full operative version?;D ;D ;D" }-

For your information, I came across a site that is offering 90 days trial (commercial version). :o

[cerBer]

-{ Quote: "...everything fails.
Kaspersky screwed up...TrendMicro screwed up badly..." }-
That is correct.
But, have you tried to report bugs or suggest anything to Kaspersky or Trend?
I have numerous times, and always have received thanks and some info - do they recognize it as a bug, when it will be corrected etc. Same even in case I suggested something they didn't agree with.

Now, go get similar attitude from Eset, and good luck!

I already mentioned NOD's protection. They have screwed it up so badly that it is more like a joke. And, it requires really very litttle to fix.
I have tried to talk wit Eset about this, and guess what? They pretended dead, stupid, whatever, to just not admit there is a problem. Same for any other bug or suggestion - usually there is no straigt answer, just endless 'didyoudothisdidyoudothat' from their textbook, when everything would be clear had they switched on their computer and simply tried.

Sure enough, I didn't speak with developers(I think they cannot be dumb, if they created the best AV engine) but I do not feel urge to get through super defensive and not very intelligent support layer.
The result is something I would hardly associate with best interests of users and Eset itself.

[Suggers]

-{ Quote: "Right... makes perfect sense, that. " }-

Judging by some of the comments Guilijan has left about nod32 on another antivirus forum, not to mention this one, I'm not too sure that he actually wants a trial version of nod32. ;)

This link may be appropriate:
http://en.wikipedia.org/wiki/Internet_troll

:o 8)

[cerBer]

-{ Quote: "Judging by some of the comments Guilijan has left about nod32 on another antivirus forum, not to mention this one, I'm not too sure that he actually wants a trial version of nod32. ;)

This link may be appropriate:
http://en.wikipedia.org/wiki/Internet_troll

:o 8)" }-
Indeed a good link, and read it yourself!

However bad person Guilijan is, he asked a question which could possibly interest others too.
But instead of answering, you are starting to scrutinize his person, which does not add anything at all to NOD's support. 90 day trial possibly would, at least to some.

[LokiLoki]

-{ Quote: "Indeed a good link, and read it yourself!

However bad person Guilijan is, he asked a question which could possibly interest others too.
But instead of answering, you are starting to scrutinize his person, which does not add anything at all to NOD's support. 90 day trial possibly would, at least to some." }-

Ain't you doing the same now? Oh yeah me too.

[Suggers]

-{ Quote: "
However bad person Guilijan is" }-

Who said Guilijan was a bad person? Not me. :)

-{ Quote: "he asked a question which could possibly interest others too" }-

Indeed, he provided this response as well "And who said that it will be for me?
I have many enemies too." I think there is an insinuation here. ;)

[cerBer]

All I am saying is that if he would give NOD to his enemies, it wouldn't be so bad, after all. And that internet trolling does not apply to him in this case, even would he be the most natural one elsewhere.
And that I would also like to know where to obtain 90day trial. I have few clients that might be interested (not enemies).

[Suggers]

-{ Quote: "All I am saying is that if he would give NOD to his enemies, it wouldn't be so bad, after all." }-

Ok...

-{ Quote: "And that I would also like to know where to obtain 90day trial. I have few clients that might be interested" }-

Your best bet would be to email support @ eset .com
In my experience they are very quick, and helpful. :)

[pykko]

-{ Quote: "Erm, first of all I'm a Kaspersky user and now a two months demo version NOD32 user.

In my humble opinion something is pretty wrong with some users attitude. "Lost of faith", "lost of trust", "lost of whatever you like" are just granma complains.
As a decent user, some people should know that everything fails.
Kaspersky screwed up updates features few hours after version 6 launch, TrendMicro screwed up badly some things last year with an untested update that caused 100% CPU usage after start-up and another one who detects some IRC clients as threats, Symantec screwed up badly with some flaw in scanning engine that caused execution of malware instead of deletion and so on.

So, everything fails one day or another.
If you change an application on first error you'll finish soon out of applications. There is no such perfect thing.
As a personal conclusion: offer reasonable solutions, give feedback, wait for a fix and relax. Is not a hole in the ozone layer, is not a H bomb in Paris and is not a bloody alien invasion.
Thank you." }-

Agree with you! ;) Everything seems fine now anyway.

[Blackspear]

Ladies and Gentlemen, back to the topic at hand, leave the personal swipes aside and lets all get along.

Any further swipes or trolling will be removed without notice.

Blackspear.

[cerBer]

-{ Quote: "...Everything seems fine now anyway." }-
It may seem, but is not.
The bug is still there, and can be reproduced with trial version easily, a bit more difficult with commercial version(but still can be reproduced with that one too).

If you understand security in generally accepted way, it is not fine, even if it lasts for 2 or 5 minutes instead of few days or few weeks as it was before.
The fact remains - under specific conditions, NOD32 may not report its update status correctly, which is unacceptable for security software.

[pykko]

cerBer as Marcos stated numerous times paid users have higher priority then trial ones. I guess you have a trial version.
My commercial version works fine since Friday. ;)
Unacceptable is what you don't want to accept. Nobody is perfect, but ESET was fast in fixing the issue.

[cerBer]

I have many different versions at work, at home and on my client's computers, but this is certainly not a question of priorities, but of program logic.
If you have lower priority, it should be said so, not that your program is up-to-date.
It would probably not be a problem for anyone, if admitted by Eset and fixed in the way it is 'fixed' now - by perfectly working servers, which is actually not a fix, because servers can go wrong any moment again.

But if it is not recognized by Eset, it is a huge security problem. So sad that it is so difficult to realize that.
Possibility is one serious argument in security business, and more serious your attitude to that, more professional you are.

[DarkStar251]

The point some people seem to be missing is that its not about the fact that some people, wether trial or commercial, cant get the updates instantly.

Thats not a positive thing but a fully excusable symptom of NOD32s rapid growth, it doesnt cause me any issues whatsoever.

The problem is the software saying your copy is up to date when it is not, as a few people here keep saying and getting replies of 'oh well trail versions are lower priority'.

Its not about trial versions getting lower priority, its about ANY version saying it is up to date when it is not.

The reason I came across this is that I had installed NOD32 (yes, trial) on my parents computer as they had just gotten internet access. It was only by sheer coincidence that I noticed the deinitions were 6 days old yesterday despite it being connected non-stop those entire 6 days.

The program hadnt been able to update itself, but it hadnt alerted anyone to the fact that it was having server issues (due to the servers being overloaded etc) or anything, and when I clicked the update button the first 10 times or so it would say it was updated.

This is my issue, someone who didnt have NOD32 elsewhere and didnt KNOW that message was incorrect may have simply assumed it had been a quiet 6 days for virus writers and left it. I knew enough to spam the update button some more till it fixed :P

All that is required is some sort of alert that the program hasnt been able to update, rather than hiding it in the log, and a change in the 'your version is up to date' message.

For example, if I recieved such a message on a computer I was using I would know that there was a *small* risk of infection and would be less likely to run an untrusted program, depending on the AV system to notify me of a virus beforehand, and I would know I could trust on demand scanning of files I had just downloaded.

All users here are asking is to be kept informed, not for 'trial users to have the same priority as commercial' or some other unreasonable demand.

[Blackspear]

-{ Quote: "Its not about trial versions getting lower priority, its about ANY version saying it is up to date when it is not." }-Agreed, as far as I know the issue is being addressed. I will see if someone from Eset would care to comment further.

Blackspear.

[DarkStar251]

-{ Quote: "Agreed, as far as I know the issue is being addressed. I will see if someone from Eset would care to comment further.

Blackspear." }-

Well then from my point of view thats all I wanted to know and I'm more than happy with that response :)

[cerBer]

-{ Quote: "Agreed,..." }-
Great! Thanx!

Then, the only question is, why did it take 6 pages of everything, to accept this? I think, it was clearly enough explained in the first post.

Ok, I have tried it again(10 minutes ago). On the completely fresh Windows installation (XP SP2 with all updates). After installling NOD32(trial version, that is what I usually do on client's computers, as I am not a reseller) with all default settings, first manual update says your version is up to date (1.1680 20060727). After 5 or 6 retries, it updates itself successfully to version (1.1684 20060729). There is only one log - about successful update!!!
Is this not enough of evidence? Why would it not be reproducable in Eset office(unless they do such trials on update server itself ;D)?

But the most magnificent thing is how Eset decided to fight the problem!!!
Now NOD updates to 1.1684 (yesterday's version), but on Eset page 1.1683 is listed as latest. Great job:P !

[Blackspear]

-{ Quote: "Great! Thanx!" }-My pleasure :blink:


-{ Quote: "Then, the only question is, why did it take 6 pages of everything, to accept this? I think, it was clearly enough explained in the first post." }-It hasn’t, there are 2 issues here, one is the “your system is up to date, no update is necessary”, the other issue is the load on the servers caused by a unusual very large update. The first, as far as I am aware is being addressed, the 2nd has been addressed and is being addressed for future proofing against the problem.


-{ Quote: "Ok, I have tried it again(10 minutes ago). On the completely fresh Windows installation (XP SP2 with all updates). After installling NOD32(trial version, that is what I usually do on client's computers, as I am not a reseller) with all default settings, first manual update says your version is up to date (1.1680 20060727). After 5 or 6 retries, it updates itself successfully to version (1.1684 20060729). There is only one log - about successful update!!!
Is this not enough of evidence? Why would it not be reproducable in Eset office(unless they do such trials on update server itself ;D)?" }-I have asked for an Eset representative to respond here.


-{ Quote: "But the most magnificent thing is how Eset decided to fight the problem!!!
Now NOD updates to 1.1684 (yesterday's version), but on Eset page 1.1683 is listed as latest. Great job:P !" }-I never worry about the update version on their website, and so long as you are at the same version or ahead, there isn’t an issue, someone is simply having the weekend off, in a day or so they’ll update the website.

Cheers ;D

[nameless]

-{ Quote: "As a result of the above [problem with updates] there are more servers being added" }-When one has NOD32's update settings on <Choose automatically>, does this mean that new servers they add will be added to the local list within NOD32, or that NOD32 will simply choose from servers that were present in the (static) list that was there when it was installed?

In other words, will existing (registered) users have to do anything to benefit from the new servers that are added, such as reinstall, or manually update the server list?

Edit: Thanks for the answer, Blackspear. And for the totally needless reply notification, pykko.

[Blackspear]

-{ Quote: "When one has NOD32's update settings on <Choose automatically>, does this mean that new servers they add will be added to the local list within NOD32, or that NOD32 will simply choose from servers that were present in the (static) list that was there when it was installed?

In other words, will existing (registered) users have to do anything to benefit from the new servers that are added, such as reinstall, or manually update the server list?" }-They will magically appear in the servers list ;) ;D

Cheers ;D

[pykko]

-{ Quote: "They will magically appear in the servers list ;) ;D

Cheers ;D" }-

I knew there is something magic with NOD32. ;D ;D :o

[Brian N]

-{ Quote: "Actually, Brian....I can concur with DarkStar here. In my case (and from the sound of it, several others as well)....no connection was made to a server (in the event log, I continually got the red exclamation icon with the words "Error connecting to server u1.eset.com" whenever I tried to manually update)....yet I was continually greeted with the pop-up window saying "Your version of nod32 is up to date. No update necessary"...." }-
The error you see in your log is NOD32 failed to connect to a server...
When that happens, it automatically moves on to the next.
If it can't connect to any servers at all, you will not see the 'up-to-date' popup.

Try this
1: Disable your connection & hit the update button. No up-to-date popup here.
2: Change server to something else than automatic, try u4, hit update. No up-to-date popup here either.

There are several reasons why it said you're up to date (and I'm only guessing here)
- The particular server that NOD32 connected to has not yet been updated with the latest defs.
- All servers are too busy with the massive amounts of people trying to get the latest defs (so it puts you 'on hold' for an hour or two, not the end of the world btw) .

[cerBer]

-{ Quote: "
- The particular server that NOD32 connected to has not yet been updated with the latest defs." }-
I think it is enough proven, that up to date message can be displayed even if server IS updated.
-{ Quote: "
- All servers are too busy with the massive amounts of people trying to get the latest defs " }-
Still, reporting up to date status when it is not, is a bug. NO matter, server is busy or not.
-{ Quote: "
(so it puts you 'on hold' for an hour or two, not the end of the world btw) ." }-
Really, getting update an hour later wouldn't be a problem, if you knew that you need to update and were not mislead by up to date message.
Plus, if I preffer to update manually, would you suggest to click update button for one hour continuously, or just return to work after one or two hours to click it again?
End of the world or not depends on if you will get infected or not during those few days you were thinking your NOD is up to date due to false message.

Finally, trying to dissolve bug report thread with 'not the end of the world' posts is probably not a very good idea.

[Brian N]

I'm just gonna stop trying right here..
It's obvious that your sole purpose in this thread is to bash NOD32 and I'll have none of that.

[cerBer]

-{ Quote: "
It's obvious that your sole purpose in this thread is to bash NOD32 and I'll have none of that." }-
Could you please be more specific?
Are you saying that false up to date message is not a bug?
Or, are you saying discussing bugs here is bashig?
Or, you simply have something against me personally but you are afraid to say?

[Marcos]

Guys, please refrain from personal attacks. It's a matter of fact that for trial users to get updates on time we'll need to change the system for trial versions and minimize the number of those using cracked versions. Hopefully this won't take much time.

[Scott-Sutton]

Greetings All,

I was looking at the large update delivered to clients last week and noticed a number of exploit advisory protection signatures for Javascript and suchlike, along with Linux exploit protection signatures. Is this a trend that's growing in the shadows in realtion to Linux? I know it has a far lesser userbase than that of Windows but exactly when did Eset begin to notice the exploits? For what it's worth I certainly find it alarming that Linux is being targetted somewhat although many attackers choose Linux as their OS of choice to attack Windows Systems, I'd certainly be looking twice over my shoulder from now on, although in saying that, I do have an interest in Linux myself, although I spend the majority of my time using Windows. Even today there was a protection signature update for Linux in the 1.1685 signature. Are these exploits local and require root priviledges or are certain exploits remote?
I'll admit that I had issues updating my system's protection last week but I can't see anything that would warrant an argument, Eset can only do so much to protect their customers and many are expecting more than can be given and thus becoming frustrated when they don't live up to "expectations". Please remember that the analysts working at Eset are highly skilled in their field and it takes a high degree of knowledge to be able to undertake a position in malware research - They're only human. :)

Regards,

Scott Sutton

[agoretsky]

Hello,

There has been a great deal of discussion here about the base signature update released by ESET for NOD32, how the various versions of the client¹ software handle downloading of these updates, staging of the updates the the client, ESET's infrastructure for publishing and distributing updates to the client, anti-piracy issues and so forth and would like to try and address these issues as best as I can.

As everyone is aware, when a base update comes up, the NOD32 client downloads a new set of signatures which is much larger than the typical signature update. I understand these currently average around forty to fifty times the size of a typical set of signatures and that in the past base updates averaging 100 times the size of a typical update have been released. That's kind of like having to switch from a 100Mb/s Fast Ethernet connection to 10Gb/s Gigabit Ethernet connection on demand.

When an update like that occurs, the bandwidth required by ESET's update servers scales up proportionally and factors such as latency and jitter which lead to dropped packets and retransmittals which are a non-issue with small signature updates suddenly become critical and load-balancing the update servers to meet those demands goes from a routine process to a complex one.

Coupled with with these types of network delivery issues are client-side with the performance, reliability and quality of the network connection, time outs from hosts' network interfaces or the client application, and so forth.

In other words, providing enough bandwidth is merely part of the process. Ensuring the updates get delivered reliably over the connection is another.

Base updates are planned out in advance and scheduled to ensure they can be delivered in a proper fashion to the client. This time, though, we had some unexpected troubles:

The demand on the servers from clients requesting updates was greater than calculated and the number of unsuccessful downloads was also slightly higher², as well. And further confusing things was that people were seeing a message in the client UI saying they had the latest signature update when a newer one was available.

As a result, for several days some people had problems downloading updates. The number of problems, though, has decreased to about where things were before the base signature update was released.

Now that you have an idea of what the problems were and the effects they had, I'd like to talk a little about some of the steps ESET is taking to ameliorate the problem with distributing future base signature updates.

First off, we're adding more servers in new locations. This should help balance the traffic across the network of update servers and ensure that as the number of clients increases the number of servers increases to match the demand better. While this seems like a fairly self-evident process, it's not a decision that is made lightly. If you're going to anti-virus update servers, they have to be very reliable and very available. You have to take every practical step you can to minimize downtime, ensure the files they are host are updated correctly and pretty much ensure any part or cable can fail (or lose power) and the servers will continue operating. They also have to be protected against attackers.

The other side of this is to look at what sorts of changes, if any, need to be made on the client side to ensure delivery. Better handling of errors and unexpected conditions, ensuring that signature updates are received completely and correctly, even over low-bandwidth, high-latency error-prone connections and even changes to the UI like more informative status messages need to be investigated.

I know these seem like fairly mechanical processes of throwing time, money and bigger/faster equipment at a project like this and, in a sense, that's exactly what some of this is going to involve. However, there's a fair amount of work which which needs to involve investigating and testing of new hardware and software and networking equipment, testing load balancing and server clustering and so forth. Microsoft's BITS (http://en.wikipedia.org/wiki/Background_Intelligent_Transfer_Service) is an interesting protocol, for example, however it is not something which applies to Linux or Novell NetWare. And there are some quite legitimate concerns about the security of peer-to-peer update mechanisms for anti-virus software.

This message is a little longer than I had originally planned on writing, but these are neither simple or easy issues to address. I hope I have made it clear, though, that these are issues ESET is working to resolve.

ESET wants all of its customers to have not just satisfactory but great experiences with its products and services and this is one area where the company is going to try very hard make that happen. Please remember, though, that these kinds of improvements do not occur overnight but over time and occur gradually in small steps.

Thank you for your patience and your understanding.

Regards,

Aryeh Goretsky


¹I know most of you think of NOD32 and other anti-virus software as a utility program--you may even run the Enterprise Edition and have some sort of n-tier distribution model set up at work--but for purposes of this discussion, it's better to think of NOD32 as a client-server app, with your copies of NOD32 as the clients and ESET's update servers as the servers.

²This was somewhat puzzling until you consider that the greater the size of the file, the higher the likelihood of encountering errors in data transmission.

[PigBrother]

Maybe my idea sounds stupid, but...
I've never seen or heard about such feature in an antivirus product, but it's always a place for "the first time". Do you ever consider bittorrent as a way to distribute updates? Your server will act as a tracker (with authentification, of course) and another server will distribute the updates for a few hours then will shutdown itself to conserve bandwidth leaving the clients to take care of the distribution.

[Brian N]

-{ Quote: "Maybe my idea sounds stupid, but...
I've never seen or heard about such feature in an antivirus product, but it's always a place for "the first time". Do you ever consider bittorrent as a way to distribute updates? Your server will act as a tracker (with authentification, of course) and another server will distribute the updates for a few hours then will shutdown itself to conserve bandwidth leaving the clients to take care of the distribution." }-
I'm just gonna vote NO on that one :)

[alglove]

-{ Quote: "Maybe my idea sounds stupid, but...
I've never seen or heard about such feature in an antivirus product, but it's always a place for "the first time". Do you ever consider bittorrent as a way to distribute updates? Your server will act as a tracker (with authentification, of course) and another server will distribute the updates for a few hours then will shutdown itself to conserve bandwidth leaving the clients to take care of the distribution." }-
No, I do not think it sounds stupid. It is certainly one way to address the issue of update server capacity. However, there are other problems that could arise, such as making sure that the update files are actually trustworthy, and also making sure that they do not fall into the wrong hands. Aryeh Goretsky touched upon this when he said,
-{ Quote: "I know these seem like fairly mechanical processes of throwing time, money and bigger/faster equipment at a project like this and, in a sense, that's exactly what some of this is going to involve. However, there's a fair amount of work which which needs to involve investigating and testing of new hardware and software and networking equipment, testing load balancing and server clustering and so forth. Microsoft's BITS is an interesting protocol, for example, however it is not something which applies to Linux or Novell NetWare. And there are some quite legitimate concerns about the security of peer-to-peer update mechanisms for anti-virus software." }-
If nothing else, it does show that people have considered the idea of Bittorrent (or something like it), but have decided against it for various reasons.

[Blackspear]

Thank you Aryeh for taking the time to write such a detailed reply, it is appreciated.

Cheers ;D

[PigBrother]

alglove, thank, I'm a moronic blind guy, I didn't seen the BITS reference :)

[izi]

Hello!

What is wrong again with ESET update servers? I can't update NOD32.
I'm have valid license.

[Brian N]

-{ Quote: "Hello!

What is wrong again with ESET update servers? I can't update NOD32.
I'm have valid license." }-
Nothing, 1.1691 is the current version, nothing new has been released yet..
So you are up-to-date :)

[basti]

-{ Quote: "Nothing, 1.1691 is the current version, nothing new has been released yet..
So you are up-to-date :)" }-

Now it's 1.1692 ;)

[ASpace]

Yes , may be , but my NOD32 still say No update necessary , I am with 1.1691 :'(

[Brian N]

-{ Quote: "Now it's 1.1692 ;)" }-
My bad :)

[ASpace]

Update

I just manually turned to u4.eset.com and updated to 1.1692

There is adv heuristic update as well as other :)


NOD32 antivirus system information
Virus signature database version: 1.1692 (20060804)
Dated: 04 August 2006
Virus signature database build: 7791

Information on other scanner support parts
Advanced heuristics module version: 1.033 (20060804)
Advanced heuristics module build: 1117
Internet filter version: 1.002 (20040708 )
Internet filter build: 1013
Archive support module version: 1.048 (20060714)
Archive support module build version: 1173

[Brian N]

-{ Quote: "There is adv heuristic update as well as other :)" }-
Yes which you can always check at nod32sse.com (or compare at least) ;)

[ASpace]

-{ Quote: "Yes which you can always check at nod32sse.com ;)" }-

You seem to be really fast with the site

[Brian N]

-{ Quote: "You seem to be really fast with the site" }-
I'm pro .. ;D

[Suggers]

I am stuck on version 1.1691 with advanced heuristics version 1.032.

When I try to update manually it says "Your version of nod32 is up to date. No update necessary."

I am a paid user and use Blackspears settings.

Copy & paste below:

NOD32 antivirus system information
Virus signature database version: 1.1691 (20060803)
Dated: 03 August 2006
Virus signature database build: 7788

Information on other scanner support parts
Advanced heuristics module version: 1.032 (20060707)
Advanced heuristics module build: 1116
Internet filter version: 1.002 (20040708)
Internet filter build: 1013
Archive support module version: 1.048 (20060714)
Archive support module build version: 1173

Information about installed components
NOD32 for Windows NT/2000/XP/2003/x64 - Base
Version: 2.51.26
NOD32 for Windows NT/2000/XP/2003/x64 - Internet support
Version: 2.51.26
NOD32 for Windows NT/2000/XP/2003/x64 - Standard component
Version: 2.51.26


Thanks

[ASpace]

Suggers , it seems not all servers got the new update , which is strange.

I manually turned to u4 and I got it

[Marcos]

Tested with automatic selection and got the update fine twice from different servers.

[Suggers]

-{ Quote: "Suggers , it seems not all servers got the new update , which is strange.

I manually turned to u4 and I got it" }-

Thanks HiTech_Boy, I tried with "choose automatically" dozens of times and it didn't work, got it straight away with manual u4.

Cheers :)

[ASpace]

Removed by me

[Beer Dog]

u4 did the trick for me too. Now updated to 1.1692.

"Error connecting to server 82.165.250.33." I've been getting that message in the event log since early this morning.

[NOD32 user]

I heard on the grapevine that it's not too far away and there should be no further recurrence of these (intermittent) update issues.

Also, as noted in another thread there is a problem with one update server just at this time. I think that I may have killed it myself with the 57,000,000 times I clicked on 'update now' ;D

Besides that, after the 'special' trial versions are dealt with as Marcos has previously mentioned, and the new update servers are in place there should be plenty of update bandwidth for all to enjoy for some time to come (I would prefer if ESET enjoy even more substantial growth and need more servers again sooner than later ;D)

The trial version system is going to be completely changed and there will be many new update servers (not just a few) to satisfy the update demands for some time to come.

But in the mean time, don't let it be a bother to you really - IMHO just set updates to 'automatic' and check in every now and again to make sure things have been running smoothly. Of course it would be a bit different if things like Bagle, Bugbear, Mydoom, Netsky, Sobig and Zafi (to name just a few) were not detected via ThreatSense :)

Cheers :)

[racketeer66]

User, Hi! D'ya have a secret, trustworthy server which's kickin when nothin' else seems to b workin'? Kinda one takes it all type? 82.165.250.33 type?

[NOD32 user]

-{ Quote: "User, Hi! D'ya have a secret, trustworthy server which's kickin when nothin' else seems to b workin'? Kinda one takes it all type? 82.165.250.33 type?" }-lol - yes 82.165.250.33 has been 'reserved' for only those who can connect to it ;D (actually it's down completely ATM I think)

Didn't you hear yet? The best kept secret mod for NOD32 is the one for adding your own update sigs :blink::lurking:;D

Cheers :)

[racketeer66]

-{ Quote: "lol - yes 82.165.250.33 has been 'reserved' for only those who can connect to it ;D (actually it's down completely ATM I think)

Didn't you hear yet? The besk kept secret mod for NOD32 is the one for adding your own update sigs :blink::lurking:;D

Cheers :)" }-
Hi Mate! I c U from Down Under:) How's tricks?
Honestly speaking U ain't have clue ? Iwas told that there are some servers in time of trouble standin' proud:)

[Stan999]

-{ Quote: "Thanks HiTech_Boy, I tried with "choose automatically" dozens of times and it didn't work, got it straight away with manual u4.

Cheers :)" }-

I also tried with "choose automatically" but couldn't get it until I tried manual u4.

[NOD32 user]

-{ Quote: "Hi Mate! I c U from Down Under:) How's tricks?
Honestly speaking U ain't have clue ? Iwas told that there are some servers in time of trouble standin' proud:)" }-It's nice here in OZ right now - night, late, dark and cold of winter ;D
My update server works fine, but it's not a public one....it's for my LAN
I'd be glad to hear of any you might come across though (they're always useful ;)), only don't post them - just via PM to me.

Cheers :)

[Brian N]

---------------------

[Benvan45]

This is my update screen.......it's configured to choose the server automatically, so why just giving the one error? Beats me! And......it's not updating!

182011

[Benvan45]

182012

[NOD32 user]

-{ Quote: "This is my update screen.......it's configured to choose the server automatically, so why just giving the one error? Beats me! And......it's not updating!" }-Mine did for a while too Benvan45, but don't worry and no need to pound 'update now' - when it is ready it will update all by itself no problem.

Yes, there is a problem with that server just now.

Cheers :)

[Benvan45]

I know it will update and I won't be pounding 'update now', but why is it not choosing another server, as it is supposed to? That's what I don't understand. ;)

[Brian N]

-{ Quote: "I know it will update and I won't be pounding 'update now', but why is it not choosing another server, as it is supposed to? That's what I don't understand. ;)" }-
It is - When it can't connect to a server, it moves on to the next

[NOD32 user]

-{ Quote: "I know it will update and I won't be pounding 'update now', but why is it not choosing another server, as it is supposed to? That's what I don't understand. ;)" }-It only logs that error when it cannot connect to the server. When it can connect but the server is busy there is currently no log entry, but this is I believe already in the suggestions box. HTH

Cheers :)

[racketeer66]

U4 the one 2 that rox- that one helped me out. No automatic update seemed to work properly. Just in case:
Removed - Not an Eset sanctioned server. Please read the Terms Of Service (http://www.wilderssecurity.com/TOS-Privacy.html) for using these forums. - Ron Surprise:)

[NOD32 user]

Hey that's great - thanks for letting me know :)

Cheers :)

[cerBer]

-{ Quote: "Tested with automatic selection and got the update fine twice from different servers." }-
Could you please explain what you are saying with this strange statement?

That there is no such problem as false up to date message?


Or, are you saying that who is receiving this message is doing something wrong, or using cracked versions, or simply lying?


Or, this means that situation is good enough for you (Eset) and nothing to worry?


Thanks.

[racketeer66]

-{ Quote: "Hey that's great - thanks for letting me know :)

Cheers :)" }-
U welcome-just a handy cute Hungarian server in time of need for da chosen:)

[NOD32 user]

-{ Quote: "Could you please explain what you are saying with this strange statement?

That there is no such problem as false up to date message?
Or, are you saying that who is receiving this message is doing something wrong, or using cracked versions, or simply lying?
Or, this means that situation is good enough for you (Eset) and nothing to worry?
Thanks." }-I can abviously not answer on Marcos behalf, but all it means is that the update is available, and that it is definately possible to get it. Just a little patience and it should be a problem no more for any.

It has already been posted what ESET's position is, that there are currently some extra unforseen things also impacting and that progress is already well underway in the steps to resolve all these things. HTH

Cheers :)

[mvdu]

I got the update by choosing u4.eset.com. But why won't automatic updates go to u4 and do the same thing? It's supposed to go on to the next one. I strongly hope these issues are fixed soon.

[Benvan45]

Some people get it manually from U4.......so why can't the automatic server selection get it from U4? It's just crazy keeping on stating that's nothing to worry about, as it will update just fine! Well, I got news........it DOES NOT UPDATE and don't start telling me now, that we have to grab back to the good old fashioned hand job in order to get Nod32 updated properly.
Marcos gets everything automatic......well I guess he's connected to some private Eset servers? If Marcos gets it automatic, why don't others?
A crazy story as far as I'm concerned and I read too many different things here and would like to really know: What's what??????

[Benvan45]

-{ Quote: "I got the update by choosing u4.eset.com. But why won't automatic updates go to u4 and do the same thing? It's supposed to go on to the next one. I strongly hope these issues are fixed soon." }-

That's what I mean, yes! I second this!

[NOD32 user]

-{ Quote: "... If Marcos gets it automatic, why don't others?..." }-...I did :lurking:

[DavidCo]

Time Module Event User
04/08/2006 20:25:15 Update Error connecting to server u7.eset.com.
04/08/2006 20:25:13 Update Error connecting to server u4.eset.com.
04/08/2006 20:25:11 Update Error connecting to server u2.eset.com.
04/08/2006 20:25:09 Update Error connecting to server u8.eset.com.
04/08/2006 20:25:07 Update Error connecting to server 82.165.250.33.
04/08/2006 20:25:07 Update Error connecting to server u3.eset.com.

cant get 1692
I am paid up

[Suggers]

Just tried each server on my desktop now (leaving u4 till last as I know this works)

Apart from U4 which works fine, I got the same message on the following, no matter how many times I tried:

u2 - "Your current version of nod32 is up to date. No update necessary."
u3 - "Your current version of nod32 is up to date. No update necessary."
82.165.250.33 - "Server connection failure".
u7 - "Your current version of nod32 is up to date. No update necessary."
u8 - "Your current version of nod32 is up to date. No update necessary."
u4 - :thumb:

P.s. I'm a paid user with a license.

Suggers

[NOD32 user]

-{ Quote: "Time Module Event User
04/08/2006 20:25:15 Update Error connecting to server u7.eset.com.
04/08/2006 20:25:13 Update Error connecting to server u4.eset.com.
04/08/2006 20:25:11 Update Error connecting to server u2.eset.com.
04/08/2006 20:25:09 Update Error connecting to server u8.eset.com.
04/08/2006 20:25:07 Update Error connecting to server 82.165.250.33.
04/08/2006 20:25:07 Update Error connecting to server u3.eset.com.

cant get 1692
I am paid up" }-Mine only looks like that when the internet is down, or for dial-up users when offline, otherwise at the moment I would expect something more like attached.

Cheers :)

[DavidCo]

Well, as you can see internet is not down etc, getting emails as well.
8Mb adsl.
This occurs a lot here (UK)
I usually have to manually update!

Here goes a try at manual, any bets on the message.

Message reads - "Your version of Nod32 is up to date.............."
Ho-hum:P

[NOD32 user]

-{ Quote: "Well, as you can see internet is not down etc, getting emails as well.
This occurs a lot here (UK)
I usually have to manually update!

Here goes a try at manual, any bets on the message.

Message reads - "Your version of Nod32 is up to date.............."
Ho-hum:P" }-Indeed...
But those errors normally mean that the server was entirely non-contactable...
can you at least ping one of them?

[Detox]

-{ Quote: "...I did :lurking:" }-

Me too - all of them so far. I won't try to say there hasn't been some sort of problem but I would hazard a guess that it is definitely not universal.

[mvdu]

Detox:

Well, this is too widespread for comfort. I and the others reporting in are paid users, too. Frustrating.

[rothko]

-{ Quote: "Me too - all of them so far. I won't try to say there hasn't been some sort of problem but I would hazard a guess that it is definitely not universal." }-
probably not, but it is certainly a new problem that started around the time of the large update (1.1678 on July 25th). I am one of the users that have found updating a bit of a problem and it was since that update that things started going downhill...

something has changed, and i know ESET will sort it out, but for now i have to update manually from whichever server that lets me do so (if i want the update at the time it comes out)

Lee

[Suggers]

-{ Quote: "Detox:

Well, this is too widespread for comfort. I and the others reporting in are paid users, too. Frustrating." }-

I'm a real fan of nod32, the best antivirus software I've ever used, I've got it on my desktop and laptop (both paid versions), I fully accept technical problems as they are inevitable no matter which software you choose.

What I do find frustrating is when paid users, like myself, post on here and get responses such as 'not universal/widespread' and 'using cracks', etc, which implies that the problem is not important/big enough, or, that anyone suffering problems is using illegal cracked versions/free trials.

I live in U.K., I have noticed several other users with problems from the UK so perhaps it is a UK issue??

Cheers :)

[Benvan45]

It's an issue in The Netherlands as well. And the responses from the Eset guys are not what they should be.
If there's a problem, just state that, but don't give replies like there's nothing going on.

[Benvan45]

-{ Quote: "Tested with automatic selection and got the update fine twice from different servers." }-

So......and what are you trying to say? I don't like suggestions like that. Just admit there's a problem!

[mvdu]

I agree with Suggers - technical problems happen with all AVs, but a problem must be admitted here. I have licenses for NOD32 and KIS (my personal fav, but not sure KIS will work right on my computer,) and the response to problems affects my decision.

[De Hollander]

Mmmmmm ???

After reading this tread, (pc was online for more as an hour) I decided to hit the update button. It connected to U4 and the reply: Your version of Nod32 is up to date.
Attempt nr 2: It connected to U8 and the reply: Your version of Nod32 is up to date
Attempt nr:3 It connected to U4 and the reply: Your version of Nod32 is up to date
Attempt nr 4: It connected to U8 and the reply: Your version of Nod32 is up to date
Attempt nr 5: It connected to U3: 1.1692 (20060804)

[Blackspear]

-{ Quote: "So......and what are you trying to say? I don't like suggestions like that. Just admit there's a problem!" }-He is not implying anything other than when he tested it and retested it, it worked for him.

I'd simply like to say to everyone, give Eset some breathing space, they will get this resolved and back to normal as soon as they can.

Blackspear.

[Blackspear]

-{ Quote: "I agree with Suggers - technical problems happen with all AVs, but a problem must be admitted here. I have licenses for NOD32 and KIS (my personal fav, but not sure KIS will work right on my computer,) and the response to problems affects my decision." }-Please read THIS POST (http://www.wilderssecurity.com/showpost.php?p=809754) for a response by Eset.

Blackspear.

[Gez]

Still having problems with NOD updates, ever since I discovered last week that the program hadn't been updated in a month. Now I understand that NOD's strength is its heuristic ability to detect malware, which makes it less dependent on signature updates, and i can go without a day or two of updates for that reason. And if Eset have problems I can live with that too -- no problem. But what I can't abide is being told by the program that I am up-to-date when i am not, and also being indirectly accused by some in here of having cracked software. I bought my NOD in january after reading the many recommendations in here and to be frank I expected an awful lot better than the insulting and dismissive attitude of some of NOD's staunchest defenders here.
Anyway, back to my problem. I've uninstalled NOD 3 times cleanly, and reinstalled with the commercial version each time. On each occasion NOD will update to the latest version successfully the first time the computer restarts, but subsequently NOD will not update at all. No matter what server I choose, or whether update servers are set to automatic or not. When I try manually updating by spamming the update button I can see for a split second that NOD does reach the servers -- u2.eset.com, u8.eset.com, etc. Not always, but most of the time anyway. So no problem with firewalls or anything. And if there was some kind of a problem along those lines, I wouldn't get the full update after a reinstall anyway. Today I'm sitting on 1.1691, having reinstalled last night. 1.1692 is available but I keep being told my NOD is up-to-date. Yet if I reinstall I know that within five minutes my NOD will be up to version 1.1692, proving that my previous installation **WAS NOT UP TO DATE**
So what's the story? What's going on and is anybody prepared to tell the truth about this serious update issue, which is not a matter of servers but rather an issue of reliability and trustworthiness. When a program is able to check the servers for updates and then tells me I am up to date when i am not then to me that is a lie and a huge breach of trust ***which calls into question the reliability and integrity of other aspects of the program***
I have no personal grudge with Eset, and NOD is still just about hanging on as my preferred antivirus, but I would like an answer to this question, and not one that tries to pull the wool over our eyes or diverts our attention to some other irrelevant aspect of the program.
Thanks.
Gez

[Suggers]

-{ Quote: "
I'd simply like to say to everyone, give Eset some breathing space, they will get this resolved and back to normal as soon as they can.

Blackspear." }-

I agree, although in order for them to resolve a problem they need to know about it, how many are experiencing it, and that it is ongoing. I thought that was what this thread was for?
Are you saying that we shouldn't be reporting our updating problems in this thread anymore?

I am not intending to bash or offend anyone, simply pointing out a problem that I have and that other users are experiencing, and that it is frustrating to be told that only cracked/trial users may have a problem, when I am a paid user.

Aside from this temporary updating issue, eset gets a big :thumb:

Regards,
Suggers

[Stem]

Servers can take time to sort out when changes are being made, I have just updated from U8.eset, so possibly just some server downtime was needed.

[Blackspear]

-{ Quote: "Still having problems with NOD updates, ever since I discovered last week that the program hadn't been updated in a month." }-As I stated HERE (http://www.wilderssecurity.com/showpost.php?p=805995) no updates for a month talks of another issue.

If you are still seeing an update issue in a week, then please send me a Private Message with your Username and Password and I will have it checked.


-{ Quote: "But what I can't abide is being told by the program that I am up-to-date when i am not," }-See above reply.


-{ Quote: "…and also being indirectly accused by some in here of having cracked software." }-I’ve only ever seen people try to help you.


-{ Quote: "I bought my NOD in january after reading the many recommendations in here and to be frank I expected an awful lot better than the insulting and dismissive attitude of some of NOD's staunchest defenders here." }-Really, well I’ve only seen help, understanding and admittance that there is an issue and that issue is being addressed by Eset.


-{ Quote: "Anyway, back to my problem. I've uninstalled NOD 3 times cleanly, and reinstalled with the commercial version each time. On each occasion NOD will update to the latest version successfully the first time the computer restarts, but subsequently NOD will not update at all. No matter what server I choose, or whether update servers are set to automatic or not. When I try manually updating by spamming the update button I can see for a split second that NOD does reach the servers -- u2.eset.com, u8.eset.com, etc. Not always, but most of the time anyway. So no problem with firewalls or anything. And if there was some kind of a problem along those lines, I wouldn't get the full update after a reinstall anyway. Today I'm sitting on 1.1691, having reinstalled last night. 1.1692 is available but I keep being told my NOD is up-to-date. Yet if I reinstall I know that within five minutes my NOD will be up to version 1.1692, proving that my previous installation **WAS NOT UP TO DATE**" }-As explained in above posts and confirmed by Eset Moderator Aryeh Goretsky in THIS POST (http://www.wilderssecurity.com/showpost.php?p=809754) they are aware of the issue.


-{ Quote: "So what's the story? What's going on and is anybody prepared to tell the truth about this serious update issue, which is not a matter of servers but rather an issue of reliability and trustworthiness. When a program is able to check the servers for updates and then tells me I am up to date when i am not then to me that is a lie and a huge breach of trust ***which calls into question the reliability and integrity of other aspects of the program***" }-As I stated a few posts above yours, give Eset a breather while they sort this out.


-{ Quote: "I have no personal grudge with Eset, and NOD is still just about hanging on as my preferred antivirus, but I would like an answer to this question, and not one that tries to pull the wool over our eyes or diverts our attention to some other irrelevant aspect of the program." }-An answer by Eset was already given, this issue is being worked on.

Blackspear.

[Blackspear]

-{ Quote: "I agree, although in order for them to resolve a problem they need to know about it…" }-They are fully aware of it.


-{ Quote: "I thought that was what this thread was for?" }-It is, but some of the aggression seen is not required.


-{ Quote: "Are you saying that we shouldn't be reporting our updating problems in this thread anymore?" }-Not at all, just for everyone to keep things in perspective.


-{ Quote: "I am not intending to bash or offend anyone, simply pointing out a problem that I have and that other users are experiencing, and that it is frustrating to be told that only cracked/trial users may have a problem, when I am a paid user." }-No worries at all.

Cheers ;D

[mvdu]

-{ Quote: "Please read THIS POST (http://www.wilderssecurity.com/showpost.php?p=809754) for a response by Eset.

Blackspear." }-

Thanks. I'm glad they are on it. I also think they need to fix the "no update needed" when there's an update available.

[Blackspear]

-{ Quote: "Thanks." }-My pleasure.


-{ Quote: "I also think they need to fix the "no update needed" when there's an update available." }-They are aware of that as well.

Cheers ;D

[Gez]

-{ Quote: "As I stated HERE (http://www.wilderssecurity.com/showpost.php?p=805995) no updates for a month talks of another issue." }-
There may be other issues, and in that time I have tried several different firewalls and other security software, so I don't dispute the possibility that there are other issues. I only want to have this resolved and if somebody can shed light on it then I am happy.

-{ Quote: "If you are still seeing an update issue in a week, then please send me a Private Message with your Username and Password and I will have it checked." }-
I very much appreciate this. I hope it doesn't come to it though. I do a lot of work cleaning viruses and other crap from PCs and I've been trying to get customers away from the freebie antivirus programs towards NOD. That's why this issue has been a bit of a downer for me persoanlly.

[Blackspear]

-{ Quote: "There may be other issues, and in that time I have tried several different firewalls and other security software, so I don't dispute the possibility that there are other issues. I only want to have this resolved and if somebody can shed light on it then I am happy." }-I think things will get back to normal after this current update, and given more servers being brought online it should be a long time before we see another such hiccup.


-{ Quote: "I very much appreciate this. I hope it doesn't come to it though. I do a lot of work cleaning viruses and other crap from PCs and I've been trying to get customers away from the freebie antivirus programs towards NOD. That's why this issue has been a bit of a downer for me persoanlly." }-I’m sure your faith will be restored given time, time to take a breather, wait for this update to appear and see if further updates begin to return to normal.

Cheers ;D

[Detox]

-{ Quote: "
What I do find frustrating is when paid users, like myself, post on here and get responses such as 'not universal/widespread' and 'using cracks', etc, which implies that the problem is not important/big enough, or, that anyone suffering problems is using illegal cracked versions/free trials." }-

Hope you didn't take me wrong - I simply said it's not universal because that means it might be more difficult for Eset to track down or fix. Certainly please do not take my posts as any kind of representative answer from Eset or something as I am nothign more than a volunteer moderator here at Wilders. As the rest of you; I am just another paid subscriber. Should you not have been referring to my post; well hey I'll just shove off lol ;D Just wanted to be sure that was understood.

[Gez]

-{ Quote: "I think things will get back to normal after this current update, and given more servers being brought online it should be a long time before we see another such hiccup.


I’m sure your faith will be restored given time, time to take a breather, wait for this update to appear and see if further updates begin to return to normal.

Cheers ;D" }-
I'm not sure if this helps at all or sheds further light on the issue but if I set my server manually to one of the IP addresses and then start hitting the manual update button I can track visits to that server through my Squid proxy log and on each occasion a small update.ver file is recorded as having been accessed/downloaded.
As I say not sure if this throws light on the issue but it does seem to tell me that I have no problems accessing the servers.

[cerBer]

-{ Quote: "
I'd simply like to say to everyone, give Eset some breathing space, they will get this resolved and back to normal as soon as they can.

Blackspear." }-
This implies that we are talking about late updates due to overloaded servers, which is not really the case.

Let's go back to very first post in this thread. There is only ONE issue - NOD reports itself up to date when it is not, hich is a technical issue and has been present in NOD all the times - servers busy or not.
-{ Quote: "Please read THIS POST (http://www.wilderssecurity.com/showpost.php?p=809754) for a response by Eset.
Blackspear." }-
Again, in that post, agoretsky is discussing server issues(kinda off-topic for this thread) in such detail that I think,
nobody would complain, if his NOD32 would display 'server busy, please try later' message.
Is that the case? No, it still shows 'your version of NOD32 is up to date', which means there is a bug, not clearly acknowledged by Eset

-{ Quote: "He is not implying anything other than when he tested it and retested it, it worked for him." }-
And what is the point? Does it justify other cases when it didn't work?

Normally, it would just mean that he didn't understand anything and needs to be told again, again and again.

[actarus9999]

Hello everybody,

By waking me this morning I noticed that my Nod it was updated and I thus was to pass in 1.1693 however by referring to me in the site of Eset I have no same date of posted.

It marks me that:

Date et heure Module Evènement
05/08/2006 03:13:54 Kernel Mise à jour de la base des signatures virales par la version 1.1693 (20060805) réussie.


While on the site of Eset it marks (20060804) ?

It is still my version which messes around nevertheless I followed the advices of a person on this forum and since that work marvelously. I mean there that I have to download the last one commercial version on the official site.

Thank you in advance.

See ya

Actarus

[Benvan45]

Automatic update again this morning to 1.1693, so let's hope it stays this way. ;)

[Blackspear]

-{ Quote: "This implies that we are talking about late updates due to overloaded servers, which is not really the case.

Let's go back to very first post in this thread. There is only ONE issue - NOD reports itself up to date when it is not, hich is a technical issue and has been present in NOD all the times - servers busy or not.

Again, in that post, agoretsky is discussing server issues(kinda off-topic for this thread) in such detail that I think,
nobody would complain, if his NOD32 would display 'server busy, please try later' message.
Is that the case? No, it still shows 'your version of NOD32 is up to date', which means there is a bug, not clearly acknowledged by Eset


And what is the point? Does it justify other cases when it didn't work?

Normally, it would just mean that he didn't understand anything and needs to be told again, again and again." }-I'll spell it out for you: Eset are aware of the issue, ALL issues including the "your system is up to date, no update is necessary” issue.

Now let’s move on.

Blackspear.

[Blackspear]

-{ Quote: "Automatic update again this morning to 1.1693, so let's hope it stays this way. ;)" }-Same here.

Cheers ;D

[Suggers]

-{ Quote: "Hope you didn't take me wrong - I simply said it's not universal because that means it might be more difficult for Eset to track down or fix. Certainly please do not take my posts as any kind of representative answer from Eset or something as I am nothign more than a volunteer moderator here at Wilders. As the rest of you; I am just another paid subscriber. Should you not have been referring to my post; well hey I'll just shove off lol ;D Just wanted to be sure that was understood." }-


Sorry for the confusion Detox, I was referring more to this post:

-{ Quote: "Tested with automatic selection and got the update fine twice from different servers." }-

Just to clear this up/move on, I think myself and others may have misinterpreted Marcos' comment, which is why there were so many responses;
I interpreted Marcos' comment to mean:
1) He did not have any problems updating
2) He did not mention any global problems therefore it must be at our end as he does not know of any ongoing issues.

However, Blackspear has since informed that eset are aware that some paid users are still (as of this morning {UK time} Ive just had to manually update to 1.1693, managed to get it from u2) getting "Your version of nod32 is up to date. No update is necessary" false message, and not being able to update automatically when "choose automatically" server is checked.

I have full confidence in eset resolving this soon, in the meantime any users, like myself, who cannot update automatically could solve this by changing to server "u4" instead of "choose automatically". I know this is not recommend, and you should change back to "choose automatically" when problem is resolved, but at the minute this is the only way I can get auto-updates.

Cheers :)

Suggers

[Benvan45]

-{ Quote: "Sorry for the confusion Detox, I was referring more to this post:

Just to clear this up/move on, I think myself and others may have misinterpreted Marcos' comment, which is why there were so many responses;
I interpreted Marcos' comment to mean:
1) He did not have any problems updating
2) He did not mention any global problems therefore it must be at our end as he does not know of any ongoing issues.

Suggers" }-

You are right......this is no way of reacting to a problem, reported by so many users.

[Suggers]

-{ Quote: "You are right......this is no way of reacting to a problem, reported by so many users." }-

I never said that, I said I misinterpreted him. :lurking:

Marcos is usually very helpful. :thumb:

Suggers

[Benvan45]

-{ Quote: "I never said that, I said I misinterpreted him. :lurking:

Marcos is usually very helpful. :thumb:

Suggers" }-

Whatever......that's how it hit me anyway!