You are currently offline, waiting for your internet to reconnect

You receive a "SQL Server does not exist or access denied" error message when you try to connect to a SQL Server named instance in a cluster by using TCP/IP sockets

Extended support for SQL Server 2005 ends on April 12, 2016

If you are still running SQL Server 2005 after April 12, 2016, you will no longer receive security updates and technical support. We recommend upgrading to SQL Server 2014 and Azure SQL Database to achieve breakthrough performance, maintain security and compliance, and optimize your data platform infrastructure. Learn more about the options for upgrading from SQL Server 2005 to a supported version here.

Bug #: 471480 (SQL Server 8.0)

SYMPTOMS
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:
[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied.
You may receive this error message when the following conditions are true:
  • SQL Server 2005 or SQL Server 2000 is installed on a cluster.
  • You are connecting to a SQL Server named instance by using TCP/IP sockets.
  • IPSec policy is enabled on the client domain.
  • IPSec policy is not enabled on the server domain.
CAUSE
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.
WORKAROUND
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:
[oledb]; Hardcoded TCP OLE DB initstringProvider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security Info=False;User ID=clientID;Data Source=tcp:TcpIpAddress,port[oledb]; Hardcoded Named Pipes OLE DB initstringProvider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security Info=False;User ID=clientID;Data Source=np:\\ServerName\pipe\MSSQL$InstanceName\sql\query
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
MORE INFORMATION
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:
827422 How to troubleshoot connectivity issues in SQL Server 2000
SQL2000 UDP
Properties

Article ID: 888228 - Last Review: 04/06/2006 21:26:36 - Revision: 4.2

Microsoft SQL Server 2000 Standard Edition, Microsoft SQL Server 2005 Enterprise Edition, Microsoft SQL Server 2005 Standard Edition

  • kbsql2005cluster kberrmsg kbtshoot kbprb KB888228
Feedback
dy>