FlexNet agent communication with beacon fails: "The client and server cannot communicate, because they do not possess a common algorithm"

[bmaudlin]

Hey Guys,

I hope you can help, I have a number of Win 2012 servers that have the agent installed, however cannot connect, and they are displaying the error of > 

The client and server cannot communicate, because they do not possess a common algorithm

We enable TLS 1.2 as a default, and I have been able to find this document > https://community.flexera.com/t5/FlexNet-Manager-Knowledge-Base/The-client-and-server-cannot-communicate-because-they-do-not/ta-p/2239 however the link at the bottom of the page that states If you run into any issues after disabling the older SSL protocols (like SSL 3.0 and TLS 1.0), then try the workaround listed under the Failed to Download Beacon Policy when only using TLS 1.2  < this url fails to load so I'm not 100% sure what the workaround is.

Am I missing something simple here? 

Ben

[ChrisG]

Thanks for the note on the old/broken link. I think the correct current link is: Failed to Download Beacon Policy when only using TLS 1.2 

I think Windows Server 2008 computers are likely to require the update discussed on the following page installed to be able to communicate using TLS 1.1 or 1.2: https://support.microsoft.com/en-au/help/3140245/update-to-enable-tls-1-1-and-tls-1-2-as-default-secure-protocols-in-wi

Information on the following page can also be useful for guidance on how to enable TLS 1.2 on client computers: https://docs.microsoft.com/en-us/mem/configmgr/core/plan-design/security/enable-tls-1-2-client. (While this page is nominally about configuring client computers in a Microsoft Configuration Manager environment, it generally applies to any client computers that need to communicate with servers using TLS 1.2.)

[durgeshsingh]

Team,

I am also facing this issue on my Windows HyperV Server 2016.

Can you confirm if any known issue on agent version 17.0.1

[ChrisG]

@durgeshsingh - I can't think of any specific known issues in the agent itself related to this. The error discussed in this thread is typically related to a mismatch in the the TLS protocols supported by the OSes running on the client and beacon computers, not an issue in the agent software itself.