My question can sound crazy but it does reflect a real Customer issue.
A Customer migrated their DBs to a new SQL 2016 server hosted by a Windows Server 2016 server but discovered that an old legacy application is still attempting to establish an ODBC connection from a Windows 2000 (!) Server.
The Customer realizes that they MUST migrate the application to a less ancient box but in the meantime they need to allow the legacy application work.
When they try to establish a connection they get an error that sounds like:
Connection Failed:
SQLState: '01000'
SQL Server Error: 772 Connection failed:
SQLState: '08001'
SQL Error: 18
The same ODBC connection can be successfully created from a Windows 10 client, so the connections settings and authentication are ok.
Based on what I read in forums and blogs it looks like an SSL or TLS issue.
What can they implement as a TEMPORARY workaround to let the legacy application work waiting to be migrated to a newer server?
Regards
Mario