Article ID: 888228 - View products that this article applies to.
Bug #: 471480 (SQL Server 8.0)
When you try to connect to a clustered Microsoft SQL Server 2005 or Microsoft SQL Server 2000 named instance by using the "servername\instancename" syntax, you receive the following error message:
You may receive this error message when the following conditions are true:
[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied.
This problem occurs during the discovery phase of the connection. The IPSec policy on the client drops packets from the server when the source IP changes.
To work around this problem, you have to hardcode the TCP port or the Named Pipe of the SQL Server named instance. To do this, use a connection string that is similar to one of the following:
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For additional information about how to troubleshoot connectivity issues in SQL Server 2000, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/827422/ )How to troubleshoot connectivity issues in SQL Server 2000
Article ID: 888228 - Last Review: April 6, 2006 - Revision: 4.2
Contact us for more help