 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
.NET Forum / ASP.NET / Security / March 2008Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection
Hi there, I don't know if this is an IIS or SQL Server issue. I have an ASP.Net web application that is set up with Anonymous access turned off and Windows Authentication turned on. The SQL 2000 server (on another machine) is set up for Windows only authentication. The application won't logon to SQL Server, as I get the error above. I have searched for this error and most of the articles suggest activating mixed mode authentication. This is at a customer site however, and they want the server left as it is. How do I make it work as intended. Hello, since you have three machines involved in this scenario (client machine, web server, sql server) you most likely don't have kerberos configured, which is required for this scenario (delegation of account tokens). Search for "double-hop problem" and you'll find plenty of resources on this. If you want integrated authentication on the client side, you need kerberos. If you can live with people entering their credentials you could switch to basic authentication and authenticate to the sql server with those credentials. You should only do this if you have SSL enabled, otherwise the credentials would be transferred in clear-text over the network. Third option: Use integrated authentication from the client to the webserver and use the service account of the IIS (AppPool user under Windows 2003+) to authenticate to the SQL server. Kind regards, Henning Krause > Hi there, > I don't know if this is an IIS or SQL Server issue. I have [quoted text clipped - 5 lines] > authentication. This is at a customer site however, and they want the > server left as it is. How do I make it work as intended. Hi Henning, there is already a .ASP application on the web server that is working fine. It is only the ASP.Net application that has this problem. Hello Waldy, are the Impersonation settings equal on both asp.net applicaitons? Kind regards, Henning Krause > Hi Henning, > there is already a .ASP application on the web server > that is working fine. It is only the ASP.Net application that has this > problem. > Hello Waldy, > > are the Impersonation settings equal on both asp.net applicaitons? Hi Henning, there is only one ASP.Net app, the other one is classic .ASP and that works fine. Where are the Impersonation settings? If you are talking about the IIS Web Site Properties / Directory Security / Authentication Methods dialog, then yes, the settings are exactly the same. Hi Waldy, take a look at the web.config of the ASP.NET application. There should be a tag named <identity>. Check if it is set to <identity impersonate="true" /> if it's not there or impersonate="false", then impersonation is disabled. Kind regards, Henning Krause >> Hello Waldy, >> [quoted text clipped - 6 lines] > Authentication Methods dialog, then yes, the settings are exactly the > same. Free MagazinesGet these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...
|
Reply to this Message
|
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2008 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.