Jump to content

NodSslWriteEncryptedData: Handshake failed to complete.


Recommended Posts

Hello,

 

Has anyone seen these alerts in the trace.log file?

2020-08-06 10:57:42 Error: NetworkModule [Thread 12fc]: Receive: NodSslWriteEncryptedData: Handshake failed to complete., ResolvedIpAddress: ResolvedHostname: , ResolvedPort:4053
2020-08-06 10:57:42 Error: NetworkModule [Thread 12fc]: Protocol failure for session id 2648660, error:Receive: NodSslWriteEncryptedData: Handshake failed to complete.

 

The issue I have found in the ESET Remote Administrator console, is that I'm not able to run client or server tasks to install the agents on domain joined computers.

Can anyone advise on what diagnostic steps I should take to get more information?

 

Cheers

Link to comment
Share on other sites

  • ESET Staff

Those errors indicates there is probably a certificate related issue. It is not clear from those lines, but in case AGENTs are not able to connect to ESMC, please check troubleshooting documentation. Most common errors are:

  • AGENT is missing CA certificate used to sign ESMC Server certificate currently used - mostly happens when non-default configuration is used. I would focus on this one in case you have generated your own certificate or performed any of migration scenarios described in documentation
  • ESMC certificate is not signed for hostnames or IP address, that are AGENTs used to connect to. This would result in state where AGENT are rejecting connection due to this missconfiguration.
Link to comment
Share on other sites

Thank you MartinK, sorry but I am not finding the troubleshooting documentation very easy to understand.

I agree that it appears to be certificate related, the log file covers activity for the entire day and lists machines that have the software installed. 

It is not clear to me from the errors what particular task is failing to run, if it's trying to communicate with the locally installed client for a status update, or trying to upgrade the version or modules etc.

My colleagues have previously had success in pushing out Client Tasks they have created, I have tried to repeat the same Client task. So far it has only installed successfully once but it did not activate the product.

 

When I create new Client or Server tasks I am unable to enter the passphrase for the certificate, as this has not been recorded.

So I have been working with Client and Server Tasks that were previously created and appear to have the passphrase saved already. It may be that at somepoint configuration was changed but I do not know how to troubleshoot for that.

Maybe a health check of the server is required or a walkthrough guide on what are the basic settings that need to be in place on a fresh installation. I have searched but have so far not found such information.

I have raised this as a support case because I cannot deploy the ESET Remote Agent or AV software directly to a domain joined computer.

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...