Chanklish
-
Posts
104 -
Joined
-
Last visited
Posts posted by Chanklish
-
-
i have the same issue for all users ..more than 250
-
On 9/13/2023 at 2:06 PM, Marcos said:
Please provide logs collected with ESET Log Collector from the machine.
here you go
-
-
is this correct ? i also create a bridge policy following this : https://help.eset.com/ebe/1/en-US/bridge_policy.html
everything was working perfectly before the last protect update .. now all is screwed
-
-
i wanted to install the latest version of the endpoints but it did not work
tried a fresh install , installed the management agent on around 140 devices .. but a lot are failing to update and are receiving : bad link to update server
i believe it is something with the ESET bridge .. same thing happened with a different company as well runing eset that i manage
-
hello
1- how to push the management agent ?
2- how to push the endpoint ?i used protect server tasks for both - the KB you are sharing have too many solutions that i am not able to understand
-
i used the server tasks for the management which is installed previously and the endpoints installation ..
i cannot see any errors but several pc has failed , no other details are showing
-
13 minutes ago, Marcos said:
I'd recommend deploying the managing agent via GPO, Remote Deployment tool, etc. and then installing Endpoint via a software install task.
Please read https://support.eset.com/en/kb7655 for more information.
the management tool is easier .. especially when you have x64 and x86 in the same network
-
hello
i am trying to install remotely some endpoints but i have dozens that are failing with : The network name cannot be found (WNetAddConnection2 failed with 0x43)
protect server and endpoints are part of the same domain , firewall off .. i can nslookup , ping and trace route the endpoints normally
no other antivirus is installed .. what to check ?
thank you
-
reinstalled everything
-
47 minutes ago, labynko said:
If it's not the DNS settings, then you can try to find out something in the log file:
C:\ProgramData\ESET\Bridge\Logs\Bridge.log
i see a lot of httpproxy not starting errors
i opened a case . waiting for the slowest support in existence -
11 minutes ago, labynko said:
Yes.
this is already present since day one
-
11 hours ago, labynko said:
ESET Bridge will not work if DNS server is not specified in the system.
where in the system ? network card ?
-
-
good day everyone
i updated eset protect to 10.1 with the all-in-one installer , and i see now the eset bridge proxy is non functional , it couldn't start - bridge service is running
i have created a bridge policy , rebooted the server , no solution
this is causing the endpoints not to receive their updates from the protect server - endpoints have no internet , only the protect server
what should i verify ?
-
yes and i received this error in my mail
-
i think even your support contact has issue
i received this after filling a support request online
<support@esetme.com>: host mail.midisglobaluae.com[94.200.27.254] said: 550
5.7.0 Local Policy Violation (in reply to end of DATA command)
-
4 minutes ago, Marcos said:
Ok but you can prepare the pcap logs cause technical support will request them.
they can do them themselves - i will not lose time over a broken software
-
i will wait for the eset support team
-
7 minutes ago, Marcos said:
There's obviously a problem establishing SSL communication with ESET's servers. Please check if you have applied this workaround in the past and undo the changes if an update addressing the security vulnerability is installed:
How to undo the workaround. Follow these steps to disable the SSL Cipher Suite Order policy setting:
- At a command prompt, type gpedit.msc and press Enter to start the Group Policy Object Editor.
- Expand Computer Configuration, Administrative Templates, Network, and then click SSL Configuration Settings.
- Under SSL Configuration Settings, double-click SSL Cipher Suite Order.
- In the SSL Cipher Suite Order window, click Disabled and then click OK.
- Close the Group Policy Object Editor and then restart your system.
If that's not the case, provide a Wireshark pcap log from an unsuccessful activation attempt.
nothing like this was done
-
with sysinspector
-
2 minutes ago, Marcos said:
Unfortunately a SysInspector log which is selected by default was not selected and therefore was missing in the generated zip file.
there is no sysinspector installed on the endpoints
i opened a ticket , this is taking too much time -
13 hours ago, Marcos said:
Yes, the logs were supposed to be taken from an Endpoint with ESET installed where activation was failing. Please provide such logs.
here you go
certificate revoked on endpoints
in ESET PROTECT On-prem (Remote Management)
Posted
also the users dont have internet , only specific sites