I never used encrypted connection, but you can consider these things:
- dblib.dll is precompiled using TDS ver. 7.3 + in MSSQLConnection there is hardcoded version 7.3 (MS SQL Server 2008+). I do not know if encrypted connection does not require higher 7.4 TDS version?
In that case you can play with environment variable TDSVER:
https://www.freetds.org/userguide/freetdsconf.htmlYou can also enable loging for FreeTDS so you can look into log file what precedees error.
- FreeTDS dblib.dll is compiled with some defines enabled and some disabled; may be that encryption support is just not enabled by default - that seems to me the most likely.
- there was already released FreeTDS ver 1.2 and is ready ver 1.3 so may be that encryption support was completed in these later versions. (but according to NEWS file encryption support was added in 0.64 version; (using either GnuTLS or OpenSSL))