Connect to sqlserver2000,throw errror: does not support encryption #2496
-
Question: when i use sqlconnection to connect sqlserver2000,throw error : The instance of SQL Server you attempted to connect to does not support encryption. connectionString: Data Source=;User ID= ;Password=** ;Initial Catalog=ScaleDb;TrustServerCertificate=true;even i change TrustServerCertificate to false or add encrypt=false (throw error: Internal connection fatal error ),both not work |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
Just a heads-up, anything before SQL Server 2016 is no longer supported, so it's a good idea to consider upgrading to a newer version for the best security and support. Now, onto your question! Are you using TLS 1.3 or TLS 1.2 on your client machine? It's worth noting that SQL Server 2000 doesn't support TLS 1.2, while TLS 1.2 is available for SQL Server 2008 and later versions. Also, TLS 1.3 kicks in from SQL Server 2022 onwards, each with their own cipher suites. If you're looking for a workaround, you could enable TLS 1.1 on your client machine, though it's not the safest option since it's deprecated. However, if you need to, you can still enforce its usage in your application. |
Beta Was this translation helpful? Give feedback.
Just a heads-up, anything before SQL Server 2016 is no longer supported, so it's a good idea to consider upgrading to a newer version for the best security and support.
Now, onto your question! Are you using TLS 1.3 or TLS 1.2 on your client machine? It's worth noting that SQL Server 2000 doesn't support TLS 1.2, while TLS 1.2 is available for SQL Server 2008 and later versions. Also, TLS 1.3 kicks in from SQL Server 2022 onwards, each with their own cipher suites.
If you're looking for a workaround, you could enable TLS 1.1 on your client machine, though it's not the safest option since it's deprecated. However, if you need to, you can still enforce its usage in your application.