Jump to content

Domo

Members
  • Content Count

    5
  • Joined

  • Last visited

  • Days Won

    3

Domo last won the day on May 18 2017

Domo had the most liked content!

Profile Information

  • Gender
    Male
  • Location
    Russia
  1. Great, thanks. One small note, tho. The file path in txt files should be pointed to current directory. Ie file=/download/win/v5/eea_nt32_enu.nup should be file=eea_nt32_enu.nup etc.
  2. Thanks, Peter. While you at it, here's another related problem:
  3. Hi. Does anyone know when 5.0.2271 PCUs gonna be available? The ones listed at hxxp://support.eset.com/kb3308/ are still for 5.0.2265... Thanks.
  4. Here's a list generated with v5 mirror (hxxp://update.eset.com/eset_upd/v5/) by ESET Server security for Linux/BSD/Solaris 4.5.3 : https://drive.google.com/open?id=0B7C2H94GCV43M3lGekw2LXlkVnM Update options screen: hxxp://i.imgur.com/bkRocEF.png Still no PROTOSCAN module update listed. Client shows 1140 (20140806) and ofc ssl problem remains... *EDIT* Also, why v5 mirror provides 8.0.312.0 client PCUs instead of 5.0.95.0 in my update.ver list, is it normal? *Edit* 2016-04-04. After some weekend testing I can safely confirm that the whole SSL error is indeed due to outdated Protosca
  5. Same problem Endpoint 5.0.2237.1. I think that the problem with outdated PROTOSCAN 1140 (20140806) module, unfortunately our mirror that is based on ESET Server security for Linux/BSD/Solaris 4.5.3 doesn't provide required module update and half of others new modules for some unknown reasons. Even with "Mirror PCU" option enabled. AFAIK the problem doesn't exist with PROTOSCAN 1173.15 (20160125). Local ESET tech support failed to help. Updating all machines to latest 5.0.2260.1 is not an option for me, so I'm waiting for an actual fix. ESET Log Collector logs: https://drive.google.co
×
×
  • Create New...