This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(166.4, 18%, 26%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
hello.
I was currently using the mssql 2008 r2 express version installed on windows 11, but after the windows 11 22h2 update, the connection from windows xp that was connected to the server is not available.
The error message that can be checked in windows xp is as follows.
[DBNETLIB][ConnectionOpen (SECDoClientHandshake()).]SSL security error.
The following has been tested.
https://danarman.blogspot.com/2023/02/windows-11-unable-to-connect-to-sql.html
I've tried the above, but I still can't connect to mssql 2008 r2 express version of windows 11 22h2 OS from windows xp.
Any help please?
thank you
Windows XP ist out-of-support, SQL Server 2008 R2 is out-of-support and it was never supported to install SQL Server 2008 R2 on Windows 11.
Why are you using such an old SQL Server version? Can you connect to SQL Server locally on Win 11 machine?
Win11 컴퓨터에서 로컬로 SQL Server 에 연결은 정상적으로 되고 있는 상태입니다.
Windows 11 에 SQL Server 2008 R2 를 설치한 것은 아니고, 이미 SQL Server 2008 R2 가 설치되어 있는 상태에서 OS를 Windows11 로 업그레이드 한 것으로 보입니다.
하나의 해결책으로 Windows XP 를 업그레이드 하는 것을 제시했으나, 오래된 하드웨어 장비 환경이라, 해당 하드웨어를 업그레이드할 의향이 없어보여 부득이 방안을 모색하게 되었습니다.
해결책은 아니지만, 관심을 가져주신 부분에 감사드립니다^^
It looks like you upgraded your OS to Windows11 with SQL Server 2008 R2 installed on your existing OS. In addition, the connection to the SQL Server locally from the Windows 11 PC is working normally, and the SQL Server is being accessed normally in other environments such as Windows 7 and 10.
As a solution, an opinion was given to upgrade the Windows XP OS, but it was not adopted due to reasons such as the upgrade cost of outdated hardware equipment.
It's not a solution, but thank you for your interest.^^
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(67.2, 68%, 16%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ELT%3C/text%3E%3C/svg%3E)
Hello,
This is 100% a TLS 1.0 issue. If after changing the internet security options in inetcpl.cpl didn't work, try the next:
In Windows Registry, add the below dword keys:
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.0\Server]
“Enabled”=dword:00000001
“DisabledByDefault”=dword:00000000
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.0\Client]
“Enabled”=dword:00000001
“DisabledByDefault”=dword:00000000
Also in the Local Security Policy on the Database Server, make sure that the setting “System Cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing” is Disabled.
--If the reply is helpful, please Upvote and Accept as answer--
It seems to be missing because the above question was not mentioned in detail, but the part of checking whether the corresponding setting is activated in the registry setting and local security policy you mentioned is a method that I have already tried and checked. This is not a solution to this problem either.
However, I wonder if there are any parts of the registry that will be affected by the settings for SSL 2.0, 3.0, TLS 1.1, and 1.2.