gregxn

just wanted to add, no trsafic inspection device, Firewall allows outbound, incoming trafic is behind NAT. If i enable VPN to our main office, where all the traffic on computer will go into tunnel replication works, and links in first post are accessible. dns resolution works with and without vpn (again links from first post, as well eset cloud address).

status and trace log from client that wont connect / cant access eset services located in ghana - accra, isp vodafone trace.zip

I have problem with 5-10 computers that wont/cant reach eset servers. Nor activation, updates, cloud console. eset.com opens normally. No firewall rules, DNS working correctly, tracert reaches end destination on checking, but not opening XML in browser: - repository.eset.com / hxxp://repository.eset.com/v1/info.meta - repositorynocdn.eset.com / hxxp://repositorynocdn.eset.com/v1/info.meta - edf.eset.com / https://edf.eset.com/edf Here is agent trace log. 2022-06-13 06:36:21 Error: CReplicationModule [Thread 1078]: InitializeFailOverScenario: Skipping fail-over scenario (stored replication link is the same as current) [RequestId: 10760fe7-a36a-44f4-8fec-8b7446637543] 2022-06-13 06:36:21 Error: CReplicationModule [Thread 1078]: CAgentReplicationManager: Replication finished unsuccessfully with message: InitializeConnection: Initiating replication connection to 'host: "xxxxxxxxxxxx.a.ecaserver.eset.com" port: 443' failed with: Request: Era.Common.Services.Replication.CheckReplicationConsistencyRequest on connection: host: "xxxxxxxxxxxxxx.a.ecaserver.eset.com" port: 443 with proxy set as: Proxy: Connection: :3128, Credentials: Name: , Password: ******, Enabled:0, EnabledFallback:1, failed with error code: 14, error message: Connect Failed, and error details: . Request Id: 10760fe7-a36a-44f4-8fec-8b7446637543 Replication details: [Task: CReplicationConsistencyTask, Scenario: Automatic replication (REGULAR), Connection: xxxxxxxxxxxxxx.a.ecaserver.eset.com:443, Connection established: false, Replication inconsistency detected: false, Server busy state detected: false, Realm change detected: false, Realm uuid: ae125732-1e81-40fd-b7e6-9c077d82a667, Sent logs: 0, Cached static objects: 69, Cached static object groups: 10, Static objects to save: 0, Static objects to delete: 0, Modified static objects: 0] i see here some proxy, But agents and endpoints were explicitly set not to use any proxy. The local network is behind NAT. offline licenses is not an option.

Hi MartinK, this is the error displayed: Failed to connect to URI: https://FQDN-vcednter.com/sdk/vimService. Code: 214Reason: NodSSL error occurred in completeHandshake. Searching up internet brings VMware KB that describes exactly this error. https://kb.vmware.com/s/article/1003218 Opening manually in browser the URI ESET tries to access: https://FQDN-vcednter.com/sdk/vimService - Results in 404 error Opening manualy in browser URI Vmware offers as solution: https://FQDN-vcednter.com/sdk/vimService.wsdl - Results in opening sample XML as expected.

sorry but these are some details that i forgot. ESET PROTECT (Server), Version 8.0 (8.0.1238.0)ESET PROTECT (Web Console), Version 8.0 (8.0.170.0)

the latest version of agent can talk with latest server i believe. check if you have any proxy set

I believe that ESET protect and agent might be in different VLANs. I have one agent with the same error. And i Know that protect and agent are in different VLANS and those 2 VLANS don't have connection (permission to communicate).

Hi admins, I am facing a interesting issue while tryin to sync Vcenter. all task settings are good. But there is task failure all the time. This is error: Failed to connect to URI: https://FQDN-vcednter.com/sdk/vimService. Code: 214Reason: NodSSL error occurred in completeHandshake.RecvEncryptedData (Certificate verification did not pass). Local: ESETProtectIP:62081 Peer: VCENTERip. Certificate is OK, But i found that Vmware posted this: https://kb.vmware.com/s/article/1003218 Is it possible that Eset is calling vcenter with wrong SDK address URI? URI: https://FQDN-vcednter.com/sdk/vimService <-- Not working in browser URI: https://FQDN-vcednter.com/sdk/vimService.wsdl <-- Working in browser Vcenter is 6.5. On one of the older vcenters (version 6) this sync task work.