7/13/2023 0 Comments Sql server express 2014I also tried using Management Studio from the client machine and the connection only works if TLS1.2 is enabled on both the client and server. The test 3) produce a successful output as expected. The test 1) fails as expected (handshake failure) while the test 2) takes several time (about 30 seconds or more) to produce the response which is successful. In order to test the connection i tried the following commands:Ģ) openssl s_client -connect :1433 -tls1_1ģ) openssl s_client -connect :1433 -tls_1_2 However the application can't connect to the database and it seems like TLS1.1 is not used by the SQL Server. In the meanwhile I want to let the application work with TLS1.1 so I re-enabled it. In order to use TLS1.2 a specific JDBC driver is needed and a property must be provided to the JDBC url (see the discussion here). I initially enabled only TLS1.2 but I need also TLS1.1 for backward compatibility with a Java application which run on another machine of the same domain. HKLM SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols. I disabled all protocols except TLS1.1 and TLS1.2 by setting the registry keys in the path: I have a Windows Server 2012 R2 which is a DC with SQL Server 2014 (Express) updated to the latest SP2 with CU10.
0 Comments
Leave a Reply. |