This is a continuation of thread: thread333-1289781
I implemented Windows Authentication, which worked to the SQL Server on the same server as the web server, however, when I tried to interact with a remote SQL Server (version 2005), it will not authenticate the windows account. This is not due to access problems, as the account has sysadmin rights, and is an administrative account across the internal domain. Whenever I try to connect, however, I get the following error message:
Either:
or...
I found a write-up from Microsoft at
It sounds like from this article that I either have to use SQL Authentication (not practical as there are hundreds of SQL Servers this needs to connect to, and I cannot create and manage that many ID's - especially with having to change their passwords every 90 days), or put the domain account and password into IIS itself, which will run the web service as that account.
My problem is this: I don't want to run the service under that account, I want it to run under the currently logged in user in windows, so I can track who's doing what, and log it. I just want the web interface to use the domain account while connecting to the remote sql servers as it has admin rights, so that passwords can be changed.
Why cannot ASP and SQL Server interact via ADO to authenticate the User ID / Password provided in the ADO connection string, and allow appropriate access just as if that user for the domain account were logged in?
Does anyone know how this can be done?
-Ovatvvon :-Q
I implemented Windows Authentication, which worked to the SQL Server on the same server as the web server, however, when I tried to interact with a remote SQL Server (version 2005), it will not authenticate the windows account. This is not due to access problems, as the account has sysadmin rights, and is an administrative account across the internal domain. Whenever I try to connect, however, I get the following error message:
Either:
Code:
Microsoft OLE DB Provider for ODBC Drivers (0x80040E4D)
[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user '{domain}\{user_id}'.
Code:
Microsoft OLE DB Provider for ODBC Drivers error '80040e4d'
[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.I found a write-up from Microsoft at
It sounds like from this article that I either have to use SQL Authentication (not practical as there are hundreds of SQL Servers this needs to connect to, and I cannot create and manage that many ID's - especially with having to change their passwords every 90 days), or put the domain account and password into IIS itself, which will run the web service as that account.
My problem is this: I don't want to run the service under that account, I want it to run under the currently logged in user in windows, so I can track who's doing what, and log it. I just want the web interface to use the domain account while connecting to the remote sql servers as it has admin rights, so that passwords can be changed.
Why cannot ASP and SQL Server interact via ADO to authenticate the User ID / Password provided in the ADO connection string, and allow appropriate access just as if that user for the domain account were logged in?
Does anyone know how this can be done?
-Ovatvvon :-Q