Intranet web page accessing to a corporate internal SQL Server database with integrated connection string and connect to the server with the user’s own network/domain id.
Connection String:
Server=ourServer;Initial Catalog=ourDb;Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security Info=true;
World Wide Web Publishing Service is running under
Local System Account (default)
Server Level Authentication:
Windows Authentication is Enabled with Response Type HTTP 401 Challange
Every other Authentication type else is disabled.
WebSite (Default Web Site)
Windows Authentication is Enabled with Response Type HTTP 401 Challange
Every other Authentication type else is disabled.
Application Pools
Created a new pool “secPool” (secured pool)
.NET Framework version: No Managed Code
Managed pipeline mode: Integrated
We are using good old Classic .ASP.
When a hit comes I get the users login id, which proves that the web site/page is Authenticated.
But cannot login/connect to remote database with the User’s own id in an integrated fashion (pass-thru).
It works when I use the page; it goes and brings data back from the SQL Server. But when a different user hits the page…. They get an error:
|199|80040e4d|Login_failed_for_user_'NT_AUTHORITY\ANONYMOUS_LOGON'. 80 ourDomain\randomUser
What setting will make it pass the authentication info to the SQL Server – without touching the SQL Server’s security settings (under a different department/control)? Should it be running under I_USR [MachineName], etc, instead of Local System Account?
Thank you so much for your help, from coooooold Boston
Cornelia