Fun times with TLS 1.2

Usage and Config
4

The below sequence worked fine for me, so there must be some inner aspects that make the difference. Official Support is required I think to help identify the root cause of the issue.

  1. Freshly installed BigFix 9.5.5 on WIN2K16 system, with remote SQL Server 2016 SP2 running on another WIN2K16 system (Note: BigFix 9.5.5 installs SQL Native Client 2011.110.5058.00)

  2. Successfully enabled “Enhanced Security/SHA256 downloads” on RootServer

  3. Disabled SSL 2.0/3.0 and TLS 1.0/1.1 on the remote SQL Server system

  4. At this point, RootServer started logging this message repeatedly:

Mon, 11 Mar 2019 11:42:58 +0100 - Main Thread (4996) - Startup failed: error testing database connection: Database Error: [Microsoft][SQL Server Native Client 11.0]TCP Provider: An existing connection was forcibly closed by the remote host.
_ (08001: 10,054)_
[Microsoft][SQL Server Native Client 11.0]Client unable to establish connection (08001: 10,054)

  1. On the RootServer system, manually updated SQL Native Client from 2011.110.5058.00 to 2011.110.7001.00 as per BigFix 9.5 Patch 6 is now available (post #8)

  2. After the update of SQL Native Client, all BigFix server processes could successfully connect to the remote database, and the BigFix deployment resumed full function mode

  3. Successfully upgraded all BigFix server components to 9.5.11

4 Likes