Panagiotis Goudas 0 Posted April 16 Share Posted April 16 Hello everyone. I installed the latest version of ESET Endpoint Security (version 11.0.2044.0) on a PC but still I cannot see it on ESET Protect Console. Ι uninstalled the product and installed it again but still I get the same problem. The product is running without any problem locally. The only problem is that we cannot communicate with the PC through ESET Protect. Is there any idea why this may happen? Thanks in advance for your answer. Link to comment Share on other sites More sharing options...
Administrators Marcos 5,231 Posted April 16 Administrators Share Posted April 16 You should find more information about possible errors in C:\ProgramData\ESET\RemoteAdministrator\Agent\EraAgentApplicationData\Logs\status.html and trace.log. Link to comment Share on other sites More sharing options...
Panagiotis Goudas 0 Posted April 23 Author Share Posted April 23 Do you have any idea what should I search for particularly inside the logs? Link to comment Share on other sites More sharing options...
Panagiotis Goudas 0 Posted April 23 Author Share Posted April 23 I upload here the files I found so that you can give me a piece of advice about what is wrong. I uninstalled (safe mode) and installed again the ESET package (endpoint security and remote agent) but still I cannot get communication. status.pdf trace.log Link to comment Share on other sites More sharing options...
Administrators Marcos 5,231 Posted April 23 Administrators Share Posted April 23 Status.html should clearly state what the problem is. You can upload the logs here for perusal. Attachments are accessible only by ESET staff. Link to comment Share on other sites More sharing options...
Administrators Marcos 5,231 Posted April 23 Administrators Share Posted April 23 Please check if DNS resolves eset.ipXXXXXXio.local on the machine (some letters in the actual hostname were obfuscated with X). Link to comment Share on other sites More sharing options...
Panagiotis Goudas 0 Posted April 23 Author Share Posted April 23 (edited) Yes DNS resolves it properly to the right IP. Edited April 23 by Panagiotis Goudas Link to comment Share on other sites More sharing options...
Administrators Marcos 5,231 Posted April 23 Administrators Share Posted April 23 It will be necessary to check a pcap log with the network communication captured during an attempt to contact the ESET PROTECT server by the agent, hence I'd recommend raising a support ticket for help with further troubleshooting: ERROR: InitializeConnection: Initiating replication connection to 'host: "eset.ipXXXXXXio.local" port: 2222' failed with: Response for request of type DeviceSessionTokenRequest (request id: 40120) was not received in time Link to comment Share on other sites More sharing options...
Panagiotis Goudas 0 Posted April 23 Author Share Posted April 23 I can create a pcap file log via Wireshark. Any idea how can I trigger the client to contact ESET PROTECT server? Furthermore, I would like some help about how to raise a support ticket. Thanks in advance for your answer. Link to comment Share on other sites More sharing options...
Administrators Marcos 5,231 Posted April 23 Administrators Share Posted April 23 You can raise a support ticket by going through the troubleshooting wizard at https://go.eset.com/contact-support/. In order to create a pcap log, apply an agent policy that will set 1-minute interval for replication and let Wireshark log the communication for 2-3 minutes to ensure that a connection attempt will be logged. Link to comment Share on other sites More sharing options...
Panagiotis Goudas 0 Posted April 23 Author Share Posted April 23 What if I stop ESET service and then start it again while I'm logging the session with Wireshark? Link to comment Share on other sites More sharing options...
Administrators Marcos 5,231 Posted April 23 Administrators Share Posted April 23 That should work too. Link to comment Share on other sites More sharing options...
Recommended Posts