Latest trial version problems

I downloaded the latest trial version last night (10/3/06), and I am having issues with the updates. For some odd reason the software either tells me that it is up to date, which I know it is not, or it WILL update after several tries but then download the same signatures, version 1.1788, over and over again as the day passes. I'll see the little popup window telling me that an update has been applied, but it is always 1.1788. Today, I have since uninstalled and redownloaded the software again from eset.com and have noticed that now the signature file has changed to 1.1789. I hope the problem mentioned above has removed itself. Anyone know what the deal is?

 

Well, anyone from ESET or otherwise going to address this? I'd appreciate some help as this is VERY annoying. Kaspersky, here I come. I can tell you that it appears to be a server issue. One server will say the software is up to date, while another will download a small file that just tells us that the dat version is the same as it was before. Yet another server will actually grab an update that we know is available and finally install it. I'm now up to 1.1790, which it was like pulling teeth to get it downloaded. I don't think I want to purchase software again that I have to constantly visit eset.com to check to see what the latest version is and then plead to God to get it installed.


Anyone?

Thanks in advance....

 

Hi biggerbyte, I have sent you a PM.

Cheers

 

I'm seeing the same issue. Installed the trial, and it says its up to date, but the sigs are for 9/25 and today is 10/4...

The logs show errors connecting to each of four servers. My connection is fine.

 

Hi Secure1, I have sent you a Private Message.

Cheers

 

I am having the same problem??!?!?!

Can you help blackspear?!?!?

 

Hi denno69, welcome to Wilders.

Please slow down and stay within one thread.

I am waiting on your reply to Snowbounds question within that thread before proceeding further.

Cheers

 

Why? Is it some kind of secret that cannot be discussed in public?
Or, could it be that you are just trying to help Eset, who do not wish to correct and even admit their obvious mistake?

 

I am trying something, and if it works then I'll take up the matter further with Eset.

Do you have an issue with me helping people?

Blackspear.

 

Of course, not.

But, as you might remember, we were discussing this already few months ago, and it is not a problem of some people, but a mistake (or, logical bug) in NOD32 update. I have explained then, that this problem can be easily reproduced. But it was actually never really admitted by Eset that problem really exists - and written off to high server load - which has nothing to do with the cause of problem, it just helps it to become apparent.
According to my findings, people who report this(like O.P of this thread) are not the ones who experience it due to some specific conditions, but the ones who notice and choose not to ignore something everybody experiences to some degree.

In this context, your demonstrative(because you didn't just send a pm, you announced it, thus making appear that we are discussing something personal) helping only some people, not everybody, appears to me a bit like an attempt to make the problem look less common than it actually is.
That is why I asked the question about your motives, not a statement about issues.

Finally, yes, I have issues, but with Eset.
As I told already, I am installing trial version of NOD32 on every client's computer, and I have been even asked many times about the update issue. But when I am trying to discuss this with Eset, I am getting back just something for form only, at best, or completely stupid, at worst.

And what is really a problem in this case is not the update issue itself, because even simple changing the message text(or, even proper explanation of what is going on) would solve it, but attitude of Eset, who will do almost anything, just to not admit that they have some kind of problem.
And I really do not understand why it is me to try explain their bugs to potential clients, not NOD support who are paid to do exactly that.

 

I did this because the people involved are very new to Wilders and may not know how a Private Message works, at least this way they could ask what’s a PM.

I’m still testing my theory, but it certainly looks like what I believe the issue is, and that is load balancing of the servers for Trial versions, and Eset are addressing the issue, however as the saying goes, Rome wasn’t built in a day…

Cheers

 

And now, imagine for a moment that they changed the text to something like 'you are using the latest available version', and then explained (possibly, under 'full version' button), that for trial versions latest updates may be available with some delay.

Wouldn't it then magically solve all the issues, keeping in mind the purpose of trial versions?
Then, only question would be - why update is not available for so long, and answer that servers are too busy would really be an answer.

Maybe no need to build Rome or invent bicycle?

 

If this issue is related to Eset's server load balancing (it may not be, I cannot speak for eset), then this quote from Marcos suggests that it may soon be addressed:

Regards

 

Just so I'm clear on this, the reason why my log files keep showing "error connecting to server" and NOD32 keeps telling me that I have the most up to date definitions whenever I try to get today's update (the last one I have was on 10-06-06) is because the trial versions have a lower priority on ESET's servers?

I don't mind if that's the case, as long as I get it eventually, and I would hope that when I finally buy the program that doesn't happen. i just want to make sure it's not something on my end that's blocking it. I'm running COMODO as a FW - are there any special settings that need to be showing on it for NOD32 to access its servers?

 

Exactly the problem discussed here:

https://www.wilderssecurity.com/showthread.php?t=148621

I'm using latest trial version too.