SQL Server 找不到证书
背景信息:
我在 example.com 上有一个 Window VPS。 我让它运行 IIS 和 SQL Server。 我有一个 example.com 的证书,可以与 IIS 很好地配合。 我想对 SQL Server 使用相同的证书来允许与客户端的加密连接。 SQL Server 配置管理器不会在下拉列表中显示证书。
我相信问题在于 SQL Server 认为证书无效,因为 SQL Server 认为服务器名称与证书不匹配(example.com)。
如何检查 SQL Server 认为的服务器名称是什么?如果错了我该如何更改?
Background Information:
I have a single Window VPS at example.com.
I have it running IIS and SQL Server.
I have a certificate for example.com that works fine with IIS.
I want to use the same certificate for SQL Server to allow encrypted connections with clients.
SQL Server Configuration Manager does not present the certificate in the drop down.
I believe the problem is that SQL Server does not think the certificate is valid, because what SQL Server thinks the server name is does not match the certificate (example.com).
How do I check what SQL Server thinks the server name is? If it is wrong how would I change it?
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(1)
好吧我发现了这个问题。
我机器上的主机名错误。它不是“example.com”,而是Windows随机生成的一些名称。您可以在计算机的属性窗口中进行设置。
证书未注册以在端口 1433 上使用。我必须使用 netsh 来启用证书以在端口 1433 上使用。说明如下:http://msdn.microsoft.com/en-us/library/ms186362(v=SQL.100).aspx
这两个步骤完成后,我获得了在 SQL Server 配置管理器中显示的证书,但在尝试运行 SQL Server 时仍然遇到问题。它不会从日志中显示无法找到或读取 SSL 证书的消息开始。
完成这些步骤后,SQL Server 服务启动没有任何问题。
Okay I found out the issue.
The hostname on my machine was wrong. It wasn't "example.com", but some name randomly generated by windows. You can set this in the computer's properties window.
The certificate was not registered to be used on port 1433. I had to use netsh to enable the certificate to be used on port 1433. Instructions here: http://msdn.microsoft.com/en-us/library/ms186362(v=SQL.100).aspx
Those two steps where complete I got the certificate to show up in SQL Server Configuration Manager, but I still had a problem went I attempt to run SQL Server. It would not start with a message from the logs saying it could not find or read the SSL Certificate.
After those steps where complete the SQL Server Service start up with out any problem.