August 11, 2017 at 8:26 am
Servers are running on SQL 2008 on Windows 2003. Client from where I am trying to connect to those servers is running SSMS 2017 on Windows server 2012 R2. I am getting following error while connecting from Management studio. I can ping the servers fine and also can connect to the port through telnet.
TITLE: Connect to Server
------------------------------
Cannot connect to ServerA.
------------------------------
ADDITIONAL INFORMATION:
A connection was successfully established with the server, but then an error occurred during the login process. (provider: SSL Provider, error: 0 - An existing connection was forcibly closed by the remote host.) (Microsoft SQL Server, Error: 10054)
Have anyone encountered this SSL provider error in past? Any idea what's causing it?
Thanks in advance!
August 11, 2017 at 8:45 am
Did you have problems with any older versions of SSMS? Personally, I have no problems connecting to a SQL Server 2008 via SSMS 2017, however, that server is running on Windows Server 2008.
I imagine the problem is actually with that you are running Windows Server 2003. Support for this ended over 2 years ago (14 July 2015), and so it probably doesn't confirm with the security protocols you are using on a more recent server.
Have you considered updating your OS (and SQL server, as 2008 does run end of life in 2019, so it's not far away).
Thom~
Excuse my typos and sometimes awful grammar. My fingers work faster than my brain does.
Larnu.uk
August 11, 2017 at 8:56 am
I have SSMS 2017 client on another Windows 2012 R2 server and from there I can connect to these servers fine. The issue is only with this one client server from where we are getting SSL error.
We have projects going on to retire/upgrade old windows 2003 servers but as you know that is ongoing process with business 🙂
August 11, 2017 at 8:59 am
RPSQL - Friday, August 11, 2017 8:56 AMI have SSMS 2017 client on another Windows 2012 R2 server and from there I can connect to these servers fine. The issue is only with this one client server from where we are getting SSL error.We have projects going on to retire/upgrade old windows 2003 servers but as you know that is ongoing process with business 🙂
Are these other server's you're able to connect to running Windows Server 2003 though?
Thom~
Excuse my typos and sometimes awful grammar. My fingers work faster than my brain does.
Larnu.uk
August 11, 2017 at 11:47 am
No They are running the same operating system (Windows 2012 R2)
August 14, 2017 at 2:11 am
RPSQL - Friday, August 11, 2017 11:47 AMNo They are running the same operating system (Windows 2012 R2)
Then this only, unfortunately, cements my feelings that the reason is because the server is running Windows 2003 (which as I said is unsupported).
Could you move the instance to another server? If not, have you also tried using an older version of SSMS to connect? You might find that using SSMS 2012/2008 might allow you to connect.
Thom~
Excuse my typos and sometimes awful grammar. My fingers work faster than my brain does.
Larnu.uk
August 15, 2017 at 5:51 am
The quickest way to solve this is to just install SQL 2008 Mgt Studio.
August 16, 2017 at 6:00 am
RPSQL - Friday, August 11, 2017 8:26 AMServers are running on SQL 2008 on Windows 2003. Client from where I am trying to connect to those servers is running SSMS 2017 on Windows server 2012 R2. I am getting following error while connecting from Management studio. I can ping the servers fine and also can connect to the port through telnet.TITLE: Connect to Server
------------------------------Cannot connect to ServerA.
------------------------------
ADDITIONAL INFORMATION:A connection was successfully established with the server, but then an error occurred during the login process. (provider: SSL Provider, error: 0 - An existing connection was forcibly closed by the remote host.) (Microsoft SQL Server, Error: 10054)
Have anyone encountered this SSL provider error in past? Any idea what's causing it?
Thanks in advance!
Does the source server is connecting from other SQL server Managment studio. Does the service account which is configured on the source server has the SET SPN set appropriately?.
Regards
Durai Nagarajan
August 28, 2017 at 6:43 am
I opened a case with MS support. We enabled all required ciphers with the use of IIS Crypto tool on client server. Issue resolved.
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply