The information in this article applies to:
SYMPTOMSOn a Windows NT Server computer running Internet Information Server (IIS) version 3.0, 4.0, or 5.0, the following ODBC error message appears when you try to verify a connection to a remote SQL database:
CAUSE
Microsoft SQL Server Integrated Security requires NTLM authentication in order to map user accounts to SQL Server accounts. STATUSMicrosoft has confirmed this to be a problem in the Microsoft products listed at the beginning of this article. MORE INFORMATIONTo work around this issue, use one of the following methods: Method 1: Host IIS and SQL Server on the Same ComputerBy eliminating the need for IIS to create an authenticated connection to SQL Server, you can work around this issue.To do this, you must use a data source name (DSN) that looks directly to the local computer for the SQL Server, and not to the network. This can be done by using the "(local)" setting in a System DSN. Method 2: Use Basic Authentication Instead of NTLM in IISBy using Basic Authentication, the password is BASE64 encoded and sent to IIS during the authentication process. With the password, IIS can now complete the NTLM authentication process when connecting to SQL Server.Method 3: Map the Anonymous User Account from IIS to a SQL Server Guest AccountThis method assumes that all users will have the same level of privileges to the SQL Server resources. Every user browsing to the Web will have access to the database.For additional information about creating connections to SQL Server, click the article numbers below to view the articles in the Microsoft Knowledge Base: Q176377 INFO: Accessing SQL Server with Integrated Security from ASP Q176378 HOWTO: SQL Server with Integrated Security, IIS on Same Machine Additional query words: front page
Keywords : kbdta |
Last Reviewed: December 16, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |