ODBC, SSL and TLC

[IlyaRabyy]

Colleagues,
We have just migrated from Sequel 2K to 2012, and now are trying to connect

- classic ASP .NET programs (made in VS 2012) on Win2016 server,
- via intranet (VPN),
- to the Sequel's DB on Win2016 server box
- via 32-bit ODBC ver. 10.00.14393.00

and getting error 18:

Firewall's not an issue (the needed port is open).
Apparently, it has something to do with SSL vs. TLC.

FYI: my partner and I already ran searches in the I-net for Sequel Error 18, found 5 altogether websites with explanations and resolutions... Explanations did help, resolutions - did not.

Thus, The Question is:

What steps and in what order shall we make to resolve this issue?

TIA!


Regards,

Ilya

 

[Olaf Doschke]

What I found points our you might need a Hotfix of SQL Server 2012:

https://dba.stackexchange.com/quest...onnect-to-sql-server-database-when-tls-1-2-or

If you go for a current Windows Server with latest TLS versions, it would also be better to use a newer SQL Server version. I guess you have decided for that version, as the compatibility is sufficient?

It's hard to mix old and new technology...

And as you said yourself, you find multiple reasons, could be anything, also group policies, I don't know what you tried already, but I'd go for SQL 2019, make the giant leap.

Bye, Olaf.

Olaf Doschke Software Engineering

https://www.doschke.name

 

[bobmpalmer]

Try Native client 11 with SQL 2012 and later.

Bob Palmer

http://www.resisystems.co.uk

The most common solution is H2O!

 

[IlyaRabyy]

Thank you Olaf.
Unfortunately, the company I work for is huge, naturally the IT security measures (read "restrictions") are sky-high, budgets are predetermined (means also "restricted").
Thus, we have to do with what we're given, not with what we choose. Plus, we are migrating from SQL 2K upward. Best case scenario, we'll get SQL 2016.
Moreover, we cannot run and install even standard updates and/or hot fixes ourselves even on our own workstations, let alone on a server! Only corporate Sys Admins can do it.
Thus, we need to file Service Ticket, wait for corp. VP approval, and then corp. IT security engineer takes control of your W/S and does it.
As result, we'll need to file this Service Ticket with justification... and you can figure all the rest.
But thank you nonetheless because your post should help us to formulate that Service Request's justification!


Regards,

Ilya

 

[Olaf Doschke]

Well, then I'd rather use SQL2016 than try whether the Hotfix SQL 2012 works. As it's not the only reason and option, first try easier options like using another driver.

The group policies change that could help I found here would even not require an installation, just a restart:

https://community.progress.com/s/ar...d-TLS1-0-protocols-on-the-WhatsUp-Gold-server

And it points in the same direction, TLS version, which means an ODBC driver change does not change how the socket is secured with which TLS version the underlying Windows system uses.
Besides that, it shows the same error can have multiple reasons, and if you're not able to try several things it likely will just cost more time for the next ticket, so a Sys Admin may be the best idea to look into this.

Bye, Olaf.

Olaf Doschke Software Engineering

https://www.doschke.name