Microsoft KB Archive/818519

= FIX: Cannot connect to named instance of SQL Server when a fully qualified domain name is specified =

Article ID: 818519

Article Last Modified on 1/2/2004

-

APPLIES TO


 * Microsoft ActiveX Data Objects 2.7
 * Microsoft Data Access Components 2.8

-



SYMPTOMS
When you try to establish a connection to a named instance of Microsoft SQL Server in another domain, if an instance of SQL Server with the same named instance (and the same SQL Server name) exists in the local domain, you are connected to the instance of SQL Server in the local domain instead of to the instance of SQL Server in the other domain.



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section of this article.



Steps to reproduce the behavior

 * 1) Install SQL Server 2000 on computer Computer1.Domain1 with a default instance and a named instance that is named Instance1.
 * 2) Install SQL Server 2000 on computer Computer1.Domain2 with a default instance and a named instance that is named Instance1.
 * 3) Run OSQL from a client computer on Domain1 and try to connect to tcp:Computer1.domain1\Instance1 by using SSPI or sa/password. You can successfully connect to the instance of SQL Server on Computer1.
 * 4) Run OSQL from the same client computer and try to connect to tcp:Computer1.Domain2\Instance1 by using SSPI or sa/password. You do not receive an error message. However, you are connected to the instance of SQL Server that is running on Computer1.Domain1 instead of Computer1.Domain2.

