TLS 1.2 and Development Environment Client using NAV2013 R2

sergisoft · 2018-08-16

Hi,

We recently banned TLS 1.0 connections to database server on a NAV2013 R2 environment and everything seems to be working fine except the Classic - Development Environment Client. Does anyone know if there's any solution to make it work? Are newer NAV Development Environment versions compatible with TLS 1.2?

Regards,
Sergi.

nverma · 2022-11-02

Were you able to resolve this? If yes, how did you make it work?

cgimec · 2022-11-03

Are both servers talking TLS1.2?

You must have TLS1.2 enabled on the server by following these articles AS IS. It won't work otherwise.
Article 1: https://docs.microsoft.com/en-us/mem/configmgr/core/plan-design/security/enable-tls-1-2-server

Article 2: https://knowledge.digicert.com/quovadis/ssl-certificates/ssl-general-topics/how-to-enable-tls-1_2-on-windows-server-2008-r2.html

The above are mandatory for any server, including 2016 I think

Also, check the below WinHTTP reg key

WinHTTP

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings\WinHttp\

DefaultSecureProtocols = (DWORD): 0xAA0

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Internet Settings\WinHttp\

DefaultSecureProtocols = (DWORD): 0xAA0

And I think on some servers you need to install a hotfix: https://support.microsoft.com/en-us/topic/update-to-enable-tls-1-1-and-tls-1-2-as-default-secure-protocols-in-winhttp-in-windows-c4bd73d2-31d7-761e-0178-11268bb10392

I hope this helps.

TLS 1.2 and Development Environment Client using NAV2013 R2

Answers

Categories