NOD updates

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 for using these forums. - Ron Surprise

 

Hey that's great - thanks for letting me know

Cheers

 

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.

 

U welcome-just a handy cute Hungarian server in time of need for da chosen

 

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

 

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.

 

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

 

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

 

...I did

 

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

 

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 -

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

Suggers

 

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

 

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

 

Indeed...
But those errors normally mean that the server was entirely non-contactable...
can you at least ping one of them?

 

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.

 

Detox:

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

 

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

 

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

 

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.

 

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

 

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.

 

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)

 

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.

 

Please read THIS POST for a response by Eset.

Blackspear.

 

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