PuterCare 3 Posted May 31 Share Posted May 31 I have ran the live agent script on a clean install on macOS 13.0 using sudo bash, it installs ok but fails to connect to ESET PROTECT 10.0.2133.0. I have created a new agent installer but still I have issues. Here is the error from the status log: Last authentication 2023-May-31 08:49:06 Enrollment failed with error: failed to connect to all addresses (code: 14) for request Era.Common.Services.Authentication.RPCEnrollmentRequest (id: f0a86e5b-8ec6-4fe8-91eb-7dbc9c455dbd) on connection to 'host: "esmc.mydomain.com" port: 2222' [RequestId: f0a86e5b-8ec6-4fe8-91eb-7dbc9c455dbd] Last replication 2023-May-31 08:48:41 Error: Replication connection problem: Response for request of type DeviceSessionTokenRequest (request id: 21) was not received in time Task: CReplicationConsistencyTask Scenario: Automatic replication (REGULAR) Connection: esmc.mydomain.com:2222 Connection established: false Replication inconsistency detected: false Server busy state detected: false Realm change detected: false Realm uuid: 00000000-0000-0000-0000-000000000000 Sent logs: 0 Cached static objects: 0 Cached static object groups: 0 Static objects to save: 0 Static objects to delete: 0 Modified static objects: 0 All replication attempts: 1 Does anyone have any ideas where I am going wrong? I also found my agent install script failed to run from Intune automatically, never had an issue with this before but may be Ventura related. Thanks Link to comment Share on other sites More sharing options...
Administrators Marcos 4,844 Posted May 31 Administrators Share Posted May 31 If you can ping the hostname to rule out name resolution issues and there's no firewall between the server and the machine that could possibly block the communication, please raise a support ticket. Link to comment Share on other sites More sharing options...
PuterCare 3 Posted May 31 Author Share Posted May 31 12 minutes ago, Marcos said: If you can ping the hostname to rule out name resolution issues and there's no firewall between the server and the machine that could possibly block the communication, please raise a support ticket. I can ping the hostname ok, there is a firewall in front of the server but it allows port 2222 from any source, other agents are all connecting fine. I will raise a support ticket. Thanks Link to comment Share on other sites More sharing options...
Recommended Posts