Client Tools Connection Issues

  • Good Day All

    I have recently started tests with SQL 2014 and Security to only allow the TLS1.2 Connections.

    As per above link it states that you need to download and install the SQL 2012 Client Tools on the server.

    I finished my tests and changed the registry settings back to their defaults allowing all Protocols since i need to test certain replication scenarios on SQL2008R2 Publications that have not been configured for TLS1.2.

    But as a result of installing the client tools and other patches , i cannot seem to connect to the server using SQL2008R2 SSMS. SQL2014 works fine but i feel that when you install the SQL Server Native Client for the SQL 2014 and 2012 that is needed for TLS1.2 configuration, it no longer allows connections from the 2008R2 SSMS.

    Has anyone tested this or is there something i might be missing.

    Regards

  • Snakeyes (5/10/2016)


    Good Day All

    I have recently started tests with SQL 2014 and Security to only allow the TLS1.2 Connections.

    As per above link it states that you need to download and install the SQL 2012 Client Tools on the server.

    I finished my tests and changed the registry settings back to their defaults allowing all Protocols since i need to test certain replication scenarios on SQL2008R2 Publications that have not been configured for TLS1.2.

    But as a result of installing the client tools and other patches , i cannot seem to connect to the server using SQL2008R2 SSMS. SQL2014 works fine but i feel that when you install the SQL Server Native Client for the SQL 2014 and 2012 that is needed for TLS1.2 configuration, it no longer allows connections from the 2008R2 SSMS.

    Has anyone tested this or is there something i might be missing.

    Regards

    Just making the link more usable for others:

    https://support.microsoft.com/en-us/kb/3135244

  • I Resolved the problem by removing any manual Cipher and Protocol registry settings, and installing the SQL2008R2 Client Tools and then removing the Service account Profile and restarting the server.

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply