Jump to content

gregxn

Members
  • Posts

    5
  • Joined

  • Last visited

About gregxn

  • Rank
    Newbie
    Newbie

Profile Information

  • Location
    Bulgaria

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. 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.
  2. 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)
  3. the latest version of agent can talk with latest server i believe. check if you have any proxy set
  4. 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).
  5. 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.
×
×
  • Create New...