1-800-691-1991 | 9am - 8pm ET
EN

Secure channel communications stop working after disabling TLS 1.0/1.1

KB ID: 2853
Product: Veeam Backup & Replication
Published: 2018-12-26
Last Modified: 2021-10-07

Challenge

After disabling TLS 1.0/1.1, Veeam functionality which utilizes the SCHANNEL security provider, such as license auto-update, license usage reporting, and Veeam explorers with remote mounts, stop working.

The following error will be listed in the Svc.VeeamBackup.log log file and the pop-up error window.
The client and server cannot communicate, because they do not possess a common algorithm.

Cause

The currently targeted .NET Framework version, 4.5.2, defaults to TLS 1.0 and doesn’t switch automatically to 1.2 when TLS 1.0/1.1 is disabled.

Solution

The following registry keys need to be added on machines where TLS 1.0/1.1 has been disabled to force the usage of TLS 1.2.

Key Location: HKLM\SOFTWARE\Microsoft\.NETFramework\v4.0.30319
Value Name: SchUseStrongCrypto
Value Type: DWORD (32-bit) Value
Value Data: 1

Key Location: HKLM\SOFTWARE\Microsoft\.NETFramework\v4.0.30319
Value Name: SystemDefaultTlsVersions
Value Type: DWORD (32-bit) Value
Value Data: 1

Key Location: HKLM\SOFTWARE\Wow6432Node\Microsoft\.NETFramework\v4.0.30319
Value Name: SchUseStrongCrypto
Value Type: DWORD (32-bit) Value
Value Data: 1

Key Location: HKLM\SOFTWARE\Wow6432Node\Microsoft\.NETFramework\v4.0.30319
Value Name: SystemDefaultTlsVersions
Value Type: DWORD (32-bit) Value
Value Data: 1


A .reg file is provided by Microsoft that will set these keys to their safest values:
https://docs.microsoft.com/en-us/dotnet/framework/network-programming/tls#configuring-security-via-the-windows-registry

More information

Microsoft .NET Framework Best practices for TLS
https://docs.microsoft.com/en-us/dotnet/framework/network-programming/tls

 
KB ID: 2853
Product: Veeam Backup & Replication
Published: 2018-12-26
Last Modified: 2021-10-07

Couldn't find what you were looking for?

Below you can submit an idea for a new knowledge base article.
Report a typo on this page:

Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!

Spelling error in text

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Your report was sent to the responsible team. Our representative will contact you by email you provided.

Oops! Something went wrong.

Please try again later.

KB Feedback/Suggestion

By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Policy.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Thank you for your interest in Veeam products!
We've sent a verification code to:
  • Incorrect verification code. Please try again.
An email with a verification code was just sent to
Didn't receive the code? Click to resend in sec
Didn't receive the code? Click to resend

ty icon

Thank you!

We have received your request and our team will reach out to you shortly.

OK

error icon

Oops! Something went wrong.

Please try again later.