bbahes

Hi, We have ESET Endpoint Security on 5 clients and Server Security on Windows file server. We don't use any management, on prem or cloud. We used Apache HTTP Proxy on one client for all other clients and file server to fetch updated. Now that Apache HTTP Proxy is not supported, what are our options since we don't use any management options. Thanks!

Hi Tomo, Yes I had contact with your sales already. The form just sends your team my order and I receive offer I can pay using bank account. I was asking for renewal payments via VISA cards, Paypal...etc... Boris. PS. One benefit of this would be to auto charge my card when license is about to expire.

@Marcos ?

Is renew possible strictly through regional reseller?

Is there option to pay renewal online?

Hi, Not sure if it's right forum, if not feel free to move it... I'm considering license renewal as home user, however I don't see that ESET ever made online store for users in Croatia. Instead we are redirected to Croatian reseller from who we receive offer which we pay via normal banking account. I won't go into prices of renewal, but does ESET consider making online purchase normal thing? Thanks.

I wonder, would you consider RHEL as security vendor? If not why not?

Will new application filtering feature announced for future 7.x version of endpoint clients be able to control these situations? We have situations where clients roam outside corporate network and we would want to be able to control things on application level. Thanks!

We did not try to reproduce problem. I will ask user to repeat same process and give you feedback.

What user did in the end is restarted machine. After that alerts went away. We talked to user and he told us that he did not shutdown notebook in Start > Shutdown way but he just closed lid. After he resumed notebook from sleep state this alert started.

Maybe related....but I have one client (Endpoint v7) that has this alert in ESMC:

HI! We got today a event in THREATS: However, I see action as Detected. If we wanted to change action for this types of threats, which specific policy/rule would we need to modify? Thanks!

Description : Add variable for COMPUTER DESCRIPTION Details: We use COMPUTER DESCRIPTION to denote workstation position and/or users and would like to include this field in notification messages.

This is what I see in /var/log/httpd/error_log file: [Mon May 06 09:16:32.930991 2019] [proxy_http:error] [pid 29607] (70007)The timeout specified has expired: [client 192.168.224.8:49679] AH01102: error reading status line from remote server update.eset.com:80 [Mon May 06 09:16:32.931042 2019] [proxy:error] [pid 29607] [client 192.168.224.8:49679] AH00898: Error reading from remote server returned by hxxp://update.eset.com/ep7-dll-rel-lb/mod_049_horusdb_4350/em049_64_l0.dll.nup [Mon May 06 09:29:08.351585 2019] [proxy_http:error] [pid 4953] (70007)The timeout specified has expired: [client 192.168.224.8:50128] AH01102: error reading status line from remote server update.eset.com:80 [Mon May 06 09:29:08.351623 2019] [proxy:error] [pid 4953] [client 192.168.224.8:50128] AH00898: Error reading from remote server returned by hxxp://update.eset.com/ep7-dll-rel-stop1/mod_049_horusdb_4350/em049_64_l0.dll.nup [Tue May 07 09:07:03.708265 2019] [proxy:error] [pid 4185] [client 192.168.224.8:49861] AH00898: DNS lookup failure for: i3.c.eset.com returned by hxxp://i3.c.eset.com:80/ 192.168.224.8 was client that had problem with update on monday. Also I see many (not too many) messages about DNS lookup failure. Is this something I should look on my side, ISP side? cat error_log | grep -o "DNS lookup failure" | wc -l 64

Still...I would be nice to know what really happened. Maybe you could anonymize trace file with https://www.tracewrangler.com/ and share it...