BUG: Domain Credentials Inappropriately Requested
Article ID: 154631
Article Last Modified on 10/3/2003
APPLIES TO
- Microsoft SQL Server 6.5 Standard Edition
This article was previously published under Q154631
SYMPTOMS
When you make a trusted connection to a SQL Server using the 16-bit Multi-
protocol Netlibrary on a Windows for Workgroups client computer, which is
simultaneously logged on to a Microsoft domain and a NetWare network, the
client computer is inappropriately requested to supply domain credentials.
This occurs even if the connection is forced over named pipes
(ncacn_np:servername).
WORKAROUND
To work around this problem, do one of the following:
- Enter in the domain credentials at each connection
-or-
- Remove the NetWare network shell from the client computer.
STATUS
Microsoft has confirmed this to be a problem in Microsoft SQL Server
version 6.5. We are researching this problem and will post new
information here in the Microsoft Knowledge Base as it becomes available.
MORE INFORMATION
The multi-protocol network library uses the features of the Windows NT RPCs
to pass domain credentials to the server when making integrated security
connections to SQL Server. This is useful if a non-Microsoft client, such
as a NetWare client, needs to make an integrated security connection to SQL
Server.
If the Windows for Workgroups client has not logged into the Microsoft
domain, then a Domain Credentials dialog box is displayed prompting the
user for a domain, user ID and password.
If the Windows for Workgroups client successfully logs on to the Microsoft
domain, the domain credentials are passed at the time of the connection and
the Domain Credentials dialog is not displayed.
If the Windows for Workgroups client has a NetWare network shell installed
as a second network, and has logged on to and validated by the Microsoft
network, then the Domain Credentials is displayed inappropriately.
Additional query words: multiprotocol
Keywords: kbnetwork KB154631