Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved.
Terms
of Use |
Trademarks
Article ID: 818519 - Last Review: January 2, 2004 - Revision: 1.0
FIX: Cannot connect to named instance of SQL Server when a fully qualified domain name is specified
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.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section of this article.
Steps to reproduce the behavior
- Install SQL Server 2000 on computer Computer1.Domain1 with
a default instance and a named instance that is named Instance1.
- Install SQL Server 2000 on computer Computer1.Domain2 with
a default instance and a named instance that is named Instance1.
- 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.
- 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.
For more information about Microsoft Data Access
Technologies, visit the following Microsoft Web site:
APPLIES TO
- Microsoft ActiveX Data Objects 2.7
- Microsoft Data Access Components
Retired KB Content DisclaimerThis article was written about products for which Microsoft no longer offers support. Therefore, this article is offered "as is" and will no longer be updated.
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