Error: Replication connection problem: failed to connect to all addresses (code: 14)

[Juan123 0]

Buenos días.

Estoy recibiendo este error, alguien ha tenido este mismo problema? al tratar de realizar la comunicación con otro equipo
no me responde, este error genera que no se reporte el equipo a la consola, el error es directamente del agente.

Error: Replication connection problem: failed to connect to all addresses (code: 14) for request Era.Common.Services.Replication.CheckReplicationConsistencyRequest (id: e2983a0c-eb60-4fb2-9195-cf26115412c2) on connection to 'host: "ktm742pymbne5cwb4pb3qcffgi.a.ecaserver.eset.com" port: 443'

[Marcos 5,452]

Since this is an English forum we kindly ask you to post in English only.

Are you able to ping ktm742pymbne5cwb4pb3qcffgi.a.ecaserver.eset.com ?

Pinging ktm742pymbne5cwb4pb3qcffgi.a.ecaserver.eset.com [20.245.38.118] with 32 bytes of data:
Reply from 20.245.38.118: bytes=32 time=172ms TTL=105

[heewey 0]

I have the same issue only on one laptop. Ping and connection to port 2222 are OK from the laptop. Just have in the log the same issue

2023-07-12 13:28:55 Error: CReplicationModule [Thread 1d44]: CAgentReplicationManager: Replication finished unsuccessfully with message: Replication connection problem: failed to connect to all addresses (code: 14) for request Era.Common.Services.Replication.CheckReplicationConsistencyRequest (id: d971654e-421c-4f36-b550-c0c364abdc9d) on connection to 'host: "bla.bla.bla" port: 2222', Task: CReplicationConsistencyTask, Scenario: Automatic replication (REGULAR), Connection: bla.bla.bla:2222, Connection established: false, Replication inconsistency detected: false, Server busy state detected: false, Realm change detected: false, Realm uuid: e89bb7e4-39cb-4434-b85d-2953cd61359a, 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

Ano other computers are OK, seems to be something special on the laptop.

[Marcos 5,452]

Please raise a support ticket. We'll need to check your status.html and trace.log first.