Jump to content

jcook

Members
  • Content Count

    4
  • Joined

  • Last visited

Profile Information

  • Location
    Cook Islands

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. There is another problem that makes the downloads so big: Every day large 'updates' are being downloaded. You can easily test that. Make sure your client is up to date. Then disconnect them from the proxy (eg pull out network cable). Wait 1 day. Open the Eset client and get ready to force refreshing the updates. Start making a screen video, put the network cable back in and hit the refresh update button. You will notice the first a small download is fetched, which is normal after 12 hours (a level 3 update). But immediately after that a very large download comes in (a Level 1 download). You might say this can happen, bit this happens every single day. ESET needs to fix this urgently, because their small updates was one of the last USP. I would hate to loose that.
  2. We have noticed exactly the same problem with one of our customers. And he could easily reproduce it in a lab with recommended ESET setup. One observation is that all update calls to hxxp://update.eset.com/ are redirected by that server to umXX.eset.com servers. So the files are downloaded from those umXX servers. But identical .nup files on those servers are not seen as identical by the proxy. Meaning the cache for a .nup file is only hit if-and-only-if it comes from the same umXX server. So, if you have for example 10 clients asking updates, via the proxy, to hxxp://update.eset.com/, then in practice only a fraction is hitting the cache due to the round-robin redirect policy from hxxp://update.eset.com/. I hope you are able to reproduce and fix this asap because, well, ... our customer uses satellite connections, so it hurts ... a lot.
×
×
  • Create New...