This article was previously published under Q176378
This article has been archived. It is offered "as is" and will no longer be updated.
This article describes how to set up Microsoft SQL Server using IntegratedSecurity on the same physical machine as Microsoft Internet InformationServer.
When using SQL Server through a Trusted Connection, it may be necessary tohost SQL Server and Internet Information Server on the same machine. Thisis commonly done with IIS 3.0 to work around limitations in accessing SQLServer through a Trusted Connection.
To allow access to SQL Server through a Trusted Connection, the SQL ServerLogin Security Mode needs to be set to either Mixed, or Windows NTIntegrated. This can be changed from the Microsoft SQL Server EnterpriseManager,. From the Server menu, select SQL Server and Configure. Thelogin settings are on the tab labeled Security Options.
To properly facilitate ActiveX Data Objects (ADO) connections from ActiveServer Pages (ASP), a System data source name (DSN) must be used.
Use the following steps to set up this DSN
On the machine running Windows NT 4.0 that hosts these two products, click the Start menu.
Click Control Panel.
Select the System DSN tab from the tabbed dialog box.
Select the SQL Server ODBC driver from the list.
Name your new data source.
In the Server combo-box, type "(local)" without the quotes.
Check the "Trusted Connection" check box.
Change whatever additional settings are necessary for your DSN.
By setting the server to (local) we are preventing anyone using this DSNfrom looking out to the network for the SQL Server. By avoiding this step,you prevent the NTLM authentication process necessary to establish atrusted connection to SQL Server.
After setting up this DSN, you may access it as you would normally in ASPcode.
For the latest Knowledge Base artices and other support information onVisual InterDev and Active Server Pages, see the following page on theMicrosoft Technical Support site: