Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved.
Terms
of Use |
Trademarks
Article ID: 916782 - Last Review: November 20, 2007 - Revision: 2.3
You may receive an error message when a SQL Server 2005 client requests encryption and connects to 127.0.0.1 on a Windows XP-based computer
Notice
Bug #: 429587 (SQLBUDT)
Bug #: 430805 (SQLBUDT)
When a Microsoft SQL Server 2005 client requests encryption and
connects to 127.0.0.1 on a Microsoft Windows XP-based computer, you may receive an error message that is
similar to one or more of the following error messages:
Error message 1
Error message 2
[SQL
Native Client] SSL Provider: The certificate's CN name does not match the
passed value.
Error message 3
[SQL Native Client] Client
unable to establish connection
This issue occurs when the following
conditions are true:
- The SQL Server client requests protocol
encryption.
- The SQL Server client connects through the
IPv4 loopback address.
- The local loopback address is represented as IP address
127.0.0.1.
This issue affects all client libraries. Client libraries that are affected by this issue include the following:
- The SQL Server .NET data
provider (Sqlclient)
- The SQL Native client
- Microsoft Data Access Components (MDAC)
Additionally, this issue prevents
successful dedicated administrator connections (DAC) to SQL Server 2005 on
Windows XP.
To work around this issue, use an alternative representation
of the name of the local host address instead of 127.0.0.1. The possible alternative representations include the following:
Note This issue is expected behavior of the Windows secure sockets layer (SSL).
This
behavior is by design.
For more information about the ForceEncryption option in SQL Server
2005, click the following article number to view the article in the Microsoft Knowledge Base:
318605Â
(http://kbalertz.com/Feedback.aspx?kbNumber=318605/
)
How SQL Server uses a certificate when the Force Protocol Encryption option is turned on
For more information about how to encrypt
connections to SQL Server 2005, visit the following Microsoft Developer Network
(MSDN) Web site:
APPLIES TO
- Microsoft SQL Server 2005 Developer Edition
- Microsoft SQL Server 2005 Enterprise Edition
- Microsoft SQL Server 2005 Express Edition
- Microsoft SQL Server 2005 Standard Edition
- Microsoft SQL Server 2005 Enterprise Edition for Itanium-based Systems
- Microsoft SQL Server 2005 Enterprise X64 Edition
- Microsoft SQL Server 2005 Standard X64 Edition
- Microsoft SQL Server 2005 Standard Edition for Itanium-based Systems
- Microsoft SQL Server 2005 Workgroup Edition
| kbtshoot kbnofix kbprb KB916782 |
Community Feedback System
Very often, it takes hours to solve a problem. Very often, you've looked high
and low, and have tried a lot of solutions. When you finally found it, chances
are, it was because someone else helped you. Here's your chance to give back.
Use our community feedback tool to let others know what worked for you and what
didn't.
Please also understand that the community feedback system is not warranted to be
correct, it's simply a system that we've built to let people try and help each
other. If something in a feedback response doesn't make sense to you, or you're
not comfortable making changes that the feedback talks about (like registry
edits), please consult a professional.
Thank you for using kbAlertz.com Feedback System.
-- Scott Cate