Reza Yousefi

@Marcos hi sir thanks for your reply ok I know that IP is valid and the owner of that is ESET, but the policy was set to receive update from our mirror server in LAN (Like Update, product update,....) and I even turn off the anti phishing and ssl/tls, but the client systems want to connect to 91.228.167.21 directly. I don't want when I have lan and mirror servers and infrastructure clients systems try to connect directly outside of the LAN

hi the clients that have endpoint business account and connect to our updater server(Mirror) in LAN but we saw in monitoring client want to connect to 91.228.167.21 directly and we don't know for what ???!!!!!! all of policy of update set to receive update from our updater but the client systems try to connect to 91.228.167.21 anyone know that??????

Hi dude Sometimes one or two clients are updated and the rest of the clients fail in the same task

hi we have a HQ building and update server is here in the other building we have 100 clients that their proxy setting is set to HQ building server when in the other building we start agent update task for 1 computer the task will successful but if select 2 or more clients together for agent update client task we will get fail with this content GetFile: Failed to process HTTP request (error code: 20014, previous: 20014, url: 'hxxp://repository.eset.com/v1/com/eset/apps/business/era/agent/v9/9.0.1141.0/agent_x64.msi')