已成功与服务器建立连接，但是在登录过程中发生错误。(provider:SSL Provider, error:0-远程王机强迫关闭了一个现有的连接。)

原创于 2025-11-04 11:57:47 发布 · 638 阅读

9 ·

CC 4.0 BY-SA版权

文章标签：

#服务器 #ssl #运维

简介：windows系统更新时会更新成新的TLS协议与密码套件，此时链接sqlsever数据库时就可能出现“已成功与服务器建立连接，但在登录过程中发生错误，错误代码0 - 远程主机强迫关闭了一个现有的连接”错误弹窗。

原因：通常由TLS协议不兼容、网络配置错误或服务器端异常导致。以下是常见解决方法：

调整TLS协议与密码套件

右键点击windows图标-》打开终端（管理员）把命令贴上就好了。

foreach ($CipherSuite in $(Get-TlsCipherSuite).Name) {
    "Disabling cipher suite: " + $CipherSuite
    Disable-TlsCipherSuite -Name $CipherSuite
}
Enable-TlsCipherSuite -Name TLS_AES_256_GCM_SHA384
Enable-TlsCipherSuite -Name TLS_AES_128_GCM_SHA256
Enable-TlsCipherSuite -Name TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384
Enable-TlsCipherSuite -Name TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256
Enable-TlsCipherSuite -Name TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
Enable-TlsCipherSuite -Name TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256

上述操作会重置系统的TLS配置，优先使用兼容性更好的加密套件；成功后以下可掠过。

以下是备用执行代码：（上述代码执行后无效时启用）

foreach ($CipherSuite in $(Get-TlsCipherSuite).Name)
{

       "Disabling cipher suite: " + $CipherSuite
       Disable-TlsCipherSuite -Name $CipherSuite

}
Enable-TlsCipherSuite -Name  TLS_AES_256_GCM_SHA384
Enable-TlsCipherSuite -Name  TLS_AES_128_GCM_SHA256
Enable-TlsCipherSuite -Name  TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384
Enable-TlsCipherSuite -Name  TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256
Enable-TlsCipherSuite -Name  TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
Enable-TlsCipherSuite -Name  TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
Enable-TlsCipherSuite -Name  TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384
Enable-TlsCipherSuite -Name  TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256
Enable-TlsCipherSuite -Name  TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384
Enable-TlsCipherSuite -Name  TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256
Enable-TlsCipherSuite -Name  TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA
Enable-TlsCipherSuite -Name  TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA
Enable-TlsCipherSuite -Name  TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
Enable-TlsCipherSuite -Name  TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
Enable-TlsCipherSuite -Name  TLS_RSA_WITH_AES_256_GCM_SHA384
Enable-TlsCipherSuite -Name  TLS_RSA_WITH_AES_128_GCM_SHA256
Enable-TlsCipherSuite -Name  TLS_RSA_WITH_NULL_SHA256
Enable-TlsCipherSuite -Name  TLS_RSA_WITH_NULL_SHA
Enable-TlsCipherSuite -Name  TLS_PSK_WITH_AES_256_GCM_SHA384
Enable-TlsCipherSuite -Name  TLS_PSK_WITH_AES_128_GCM_SHA256
Enable-TlsCipherSuite -Name  TLS_PSK_WITH_AES_256_CBC_SHA384
Enable-TlsCipherSuite -Name  TLS_PSK_WITH_AES_128_CBC_SHA256
Enable-TlsCipherSuite -Name  TLS_PSK_WITH_NULL_SHA384
Enable-TlsCipherSuite -Name  TLS_PSK_WITH_NULL_SHA256
Enable-TlsCipherSuite -Name  TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256_P256
Enable-TlsCipherSuite -Name  TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384_P384
Enable-TlsCipherSuite -Name  TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256
Enable-TlsCipherSuite -Name  TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P384
Enable-TlsCipherSuite -Name  TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA_P256
Enable-TlsCipherSuite -Name  TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA_P384
Enable-TlsCipherSuite -Name  TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA_P256
Enable-TlsCipherSuite -Name  TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA_P384
Enable-TlsCipherSuite -Name  TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256_P256
Enable-TlsCipherSuite -Name  TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA_P256
Enable-TlsCipherSuite -Name  TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA_P384
Enable-TlsCipherSuite -Name  TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA_P256
Enable-TlsCipherSuite -Name  TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA_P384
Enable-TlsCipherSuite -Name  TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384_P384
Enable-TlsCipherSuite -Name  TLS_RSA_WITH_AES_128_CBC_SHA256
Enable-TlsCipherSuite -Name  TLS_RSA_WITH_AES_128_CBC_SHA
Enable-TlsCipherSuite -Name  TLS_RSA_WITH_AES_256_CBC_SHA256
Enable-TlsCipherSuite -Name  TLS_RSA_WITH_AES_256_CBC_SHA
Enable-TlsCipherSuite -Name  TLS_RSA_WITH_3DES_EDE_CBC_SHA