直接连接到SQL Azure导致登录前握手失败 [英] Pre-login handshake woes with connecting directly to SQL Azure
问题描述
我们目前在开发环境中遇到一个非常麻烦的问题，并显示以下消息...
We are currently experiencing a rather troublesome problem in our development environment with the following message...
A connection was successfully established with the server,
but then an error occurred during the pre-login handshake.
(provider: SSL Provider, error: 0 - The certificate's CN
name does not match the passed value.)
...解决此问题的公认方法是将连接的 TrustServerCertificate 部分设置为 True .但是，这不能可靠或始终如一地工作.
...the commonly accepted wisdom to resolving this problem is to set the TrustServerCertificate portion of the connection to True. However, this does not work reliably or consistently.
在许多情况下都会发生此特定错误，例如在与实时/托管SQL Azure实例进行对话的Azure模拟器中甚至在使用SQL Management Studio的情况下测试我们的WCF服务.我们发现的唯一共同点是，仅当我们直接连接到SQL Azure时才发生这种情况，而不是在托管时和Azure直接与SQL Azure进行对话时(确实起作用).
This particular error occurs in a number of instances, for instance testing our WCF Service in our Azure Emulator talking to live / hosted SQL Azure Instance or even using SQL Management Studio. The only common denominator we've found is that this occurs only when we connect directly to SQL Azure as opposed to when its hosted and Azure is talking directly to SQL Azure (which does work).
I've tried a number of tactics to resolve the problem (such as the one detailed here), i.e. believing it was connection related and removing pooling and other modifications to the connection string. But alas, none are conclusive and more irritating is that the error is intermittent and will prevent access for a short period of time before magically resolving itself.
我消除的其他因素.
- 我们正在使用Transcient Application Block尝试从这些错误中恢复，但没有.
- 我们的办公室没有与Azure托管服务建立连接的代理服务器.
其他人遇到此问题或有任何建议吗?
Has anyone else experienced this problem or has any suggestions?
推荐答案
您需要扫描与FILE_SKIP_COMPLETION_PORT_ON_SUCCESS标志不兼容的非IFS Winsock BSP或LSP，问题主要来自非IFS LSP strong>正在安装.
You need to scan for Non-IFS Winsock BSPs or LSPs which not compatible with the FILE_SKIP_COMPLETION_PORT_ON_SUCCESS flag ,problem results primarily from non-IFS LSPs Being installed.
只需在命令提示符下运行"netsh WinSock显示目录" ，然后检查任何看起来不是 0x20xxx
Just run "netsh WinSock Show Catalog" from command prompt , and check any "service flag" which doesn't look in the format of 0x20xxx
对于我来说，我发现带有服务标志0x66的"Speed Accelerator"可以通过删除此软件解决我的问题.
In my case I found that "Speed Accelerator" with service flag 0x66,removing this software solve my Problem .
可以在这里找到更多信息: http://support.microsoft.com/kb/2568167
More information can be found here : http://support.microsoft.com/kb/2568167
这篇关于直接连接到SQL Azure导致登录前握手失败的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
