NOD updates

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

Regards,
Suggers

 

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.

 

As I stated HERE 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.

See above reply.

I’ve only ever seen people try to help you.

Really, well I’ve only seen help, understanding and admittance that there is an issue and that issue is being addressed by Eset.

As explained in above posts and confirmed by Eset Moderator Aryeh Goretsky in THIS POST they are aware of the issue.

As I stated a few posts above yours, give Eset a breather while they sort this out.

An answer by Eset was already given, this issue is being worked on.

Blackspear.

 

They are fully aware of it.

It is, but some of the aggression seen is not required.

Not at all, just for everyone to keep things in perspective.

No worries at all.

Cheers

 

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.

 

My pleasure.

They are aware of that as well.

Cheers

 

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

 

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 Just wanted to be sure that was understood.

 

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.

 

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.

 

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

 

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

 

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.

 

Same here.

Cheers

 

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.

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

 

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.

Marcos is usually very helpful.

Suggers

 

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