March 29, 2021 at 1:19 pm
Good day all,
I am assisting our DBA team by conducting some investigations into making use of SQL Server encrypted connections for one of our older (VB6-based, yes I know!) applications. I have successfully applied a certificate to the SQL server, restarted the SQL Server service and all looks well. Running the following shows me that connections are encrypted:
USE master
GO
SELECT encrypt_option FROM sys.dm_exec_connections
GO
So, here is the crux of the matter. Using a Windows 10 client with our ancient software installed on it, I can successfully launch, login and navigate around the application. I can see from running netstat on the W10 client, there are connections to the SQL server on the default SQL Server port bound to the IP address of the SQL server.
However, running netstat on the SQL server, I can see, well, nothing. There are no inbound connections to the SQL box from my W10 client and via SSMS and running the above script, while there are other connections hitting the SQL box, there are none for the application via my W10 client. I have checked DNS, IP addresses, etc., and all looks to be fine. I have temporarily removed AV software just to make sure it is not that.
I just wondered if anyone had come across this happening before? The SQL Server is running SQL Server 2016 Developer Edition with SP2 and CU 16.
Am happy to provide more information if needed. Just didn't want to inundate this post with information if there is something obvious that I am doing wrong.
Many thanks in advance,
Dave.
March 30, 2021 at 2:10 pm
Thanks for posting your issue and hopefully someone will answer soon.
This is an automated bump to increase visibility of your question.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply