SSMS 20.2 on Windows11 not able to connect to SQL 2005 ??

Question

Post reply

SSMS 20.2 on Windows11 not able to connect to SQL 2005 ??

Johan Bijnens

SSC Guru

Points: 135389
More actions
November 19, 2024 at 9:25 am

#4485819
We still have a couple of dino's.
What should I check to re-enable access to ye good old SQL 2005 on Windows 2003 for my SSMS 20.2?
I have already accepted "use server certificate" and "optional encryption"
Still doesn't work;
"SSL Connection forcebly closed by server"
btw: When using SSMS 18.12.1 it works fine
- This topic was modified 2 months, 1 week ago by Johan Bijnens.
Johan

Learn to play, play to learn !
Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:
- How to post Performance Problems
- How to post data/code to get the best help[/url]
- How to prevent a sore throat after hours of presenting ppt
press F1 for solution, press shift+F1 for urgent solution 😀
Need a bit of Powershell? How about this
Who am I ? Sometimes this is me but most of the time this is me

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply

Ant-Green SSC Guru Points: 113509 More actions · Answer 1

Use an older version instead unfortunately.

As per the documentation, 20.2 is only tested on 2014 and above.

https://learn.microsoft.com/en-us/sql/ssms/download-sql-server-management-studio-ssms?view=sql-server-ver16#supported-sql-offerings

Johan Bijnens SSC Guru Points: 135389 More actions · Answer 2

The stange thing is, on Windows 10 with SSMS 20.2, this still works.

What is different with Windows 11 ?

Johan

Learn to play, play to learn !

Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:

- How to post Performance Problems
- How to post data/code to get the best help[/url]

- How to prevent a sore throat after hours of presenting ppt

press F1 for solution, press shift+F1 for urgent solution 😀

Need a bit of Powershell? How about this

Who am I ? Sometimes this is me but most of the time this is me

Ant-Green SSC Guru Points: 113509 More actions · Answer 3

Probably allows the use of old legacy ciphers / algorithms, but just clutching at straws there, unsure of the internals.

We can only go on what the public documentation says.

Might be worth a ticket to MSFT, but they will probably tell you the same, it's to old upgrade or to use an older version of SSMS.

micherve Grasshopper Points: 15 More actions · Answer 4

Since SSMS 18.12.1 works fine, it might be worth checking the TLS settings. SQL Server 2005 doesn’t support TLS 1.2 by default, so you might need to enable it or try forcing SSMS to use an older protocol.