Odd behavior with update 1.917. Differents size between differents...

Hi,
I found a odd behavior in update version 1.917. My NOD was updated successfully from 1.916 to 1.917. The problem is that I checked again some hours late to check if is available 1.918 or a more recent update. NOD32 started downloading engine2.nup again and updated from 1.917 to 1.917, in others words, NOD32 downloaded the same update again. This problem occurs with the server. And something veru urgent. Recently I noted that the engine2.nup file that has the u3.eset.com server is about 57 KB and the engine2.nup that has the u2a.eset.com is about 67 KB!!!!! And is the same file and the same update version. What happend!!??

 

Maybe your first download was corrupted, Nod32 saw that the update was corrupted on the next attempt at an update and downloaded the file again to fix the issue...

Just a thought.

Cheers

 

Hi Blackspear,
Not, If I press the update button again and NOD choose u3, u4 servers, NOD download again the update (about 57 KB) and if NOD choose others servers like u2a, NOD download again the same file and it's about 67 KB. Please test yourself.

 

Just tried it, I can't replicate what you have found...

Cheers

 

Hello,
I contacted Eset. I think I'll not have reply because we're on weekend. What would you do?

 

Blackspear, you CAN replicate sir carew's experience? I CAN"T, works as it should, it checks when I press update now, but no files are d/l'd. I tried all 3 servers, u2a,u3,u4 same, no update d/l'd.

 

Sorry, I made a typo, fixed my post to read can't replicate the problem, same results as you...

Cheers

 

Quote:
Originally Posted by sir_carew
Hi Blackspear,
Not, If I press the update button again and NOD choose u3, u4 servers, NOD download again the update (about 57 KB) and if NOD choose others servers like u2a, NOD download again the same file and it's about 67 KB. Please test yourself.

I have tested the update on u2, u3 and u4 servers and no update again here all is well, all you get is the box poping up stating nod is up to date.
I have tried all servers many times over, but cannot replicate this issue that others are reporting all is well.

THE MUL

 

I found the problem

I found the problem. The problem is with Mirror enabled. Blackspear, if you've admin version, please enable Mirror feature and test again. Now with Mirror disabled all is OK...

 

Re: I found the problem

Ahhh there you have it, I don't use a mirror here at home (beautiful enough ) so can't test it here...

Cheers

 

I have the same problem here too and I have the admin version, it has to do something with the miror.

 

Good to see that it can be replicated, we'll wait for support to reply to the issue...

Cheers

 

I tried it this morning at work, and I too can replicate the problem, Nod32 updates, press "Update Now" and it updates the same signature again when a mirror is used...

Cheers

 

I too am having the same problem. I have the Admin version with mirror enabled. I noticed this yesterday when multiple update downloads for 1.917 were reported in the log.

sir_carew, please let us know the response from Eset support.

 

Hello Sir_carew and everyone else,

This issue has already been fixed. Eset's ISP was switching their connection and as a result, we were unable to send an update to one of the servers (but users
around the world were still able to access that site). The situation only affected users running a mirror and it should no longer be an issue.

Bandicoot.

 

Ahhh Mr Coot top of the morning to you, good to see you scurrying about the halls of Wilders

Thank you kind for the information, a pleasure as always

Cheers