3

I have a classic ASP site that accesses a SQL Server 2008 R2 database (which resides on a separate server) and when I disable TLSv1.0 and SSLv3.0, my site displays an error stating that: "Microsoft SQL Server Native Client 11.0 error '80004005'

Encryption not supported on the client."

I first read this: http://blogs.sqlsentry.com/aaronbertrand/tls-1-2-support-read-first/, then applied all applicable server and client patches as instructed here https://support.microsoft.com/en-us/kb/3135244, and attempted the fix as described here Classic ASP Outbound TLS 1.2 to no avail.

I also found that when I use FIPS compliant encryption algorithms, as seen here https://dba.stackexchange.com/a/99129, this site resolves, but the other non-classic ASP sites on this server do not.

Any ideas on how I can correct this?

Community
  • 1
  • 1
Rob Hefty
  • 58
  • 2
  • 8
  • I got around this issue by limiting protocols at the load balancer. This allows internal traffic to use the antiquated protocols and still remain PCI compliant. – Rob Hefty Sep 26 '16 at 16:35

1 Answers1

3

You can accomplish this by setup recent MS OLE DB or ODBC driver on server with your application and slightly change connection string to DB.

Option 1 - MS OLE DB Driver



Option 2 - MS ODBC Driver

Anton Palyok
  • 1,249
  • 1
  • 16
  • 27
  • When installing the OLE DB driver, install both the Client Components AND the OLE DB Driver for SQL Server SDK. The latter is not selected as default. – Michael Hansen Jun 10 '22 at 14:34