Logon 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.


.



Relevant Pages

  • Windows Authentication with IIS on separate machines
    ... Yes, setting Basic Authentication in IIS works, but the ... >in SQL server but doesn't work if user account was ... >imported from a Windows account. ...
    (microsoft.public.sqlserver.security)
  • Re: Authentication problem
    ... As matt notes below, even if nothing on your box has changed it's possible ... > On your IIS box, check the HTTP Authentication tab of the SQL Server ...
    (microsoft.public.sqlserver.ce)
  • IIS vs ASP.Net Authentication problem
    ... Requirement is to use 'domain\iisuser' to authenticate in SQL Server ... Only Integrated Windows Authentication enabled (Anonymous/basic/digest ... unchecked) in IIS 5 ... Login failed for user 'CCMIWS05\ASPNET'. ...
    (microsoft.public.dotnet.security)
  • RE: Interdev not creating project (authenticate failure)
    ... | 1st Computer (for SQL Server and IIS): ... | Member of: Administrators ... Also in IIS console, rightclick the web site and go to properties/directory ... Integrated Windows and check Basic authentication. ...
    (microsoft.public.inetserver.iis.security)
  • Re: Windows Authentication in asp.net 2005 to SQL Server?
    ... If the domains do not trust each other, Windows authentication is not going ... Basic authentication sometimes makes the need for Kerberos delegation go ... generic account to do the backend data stuff on our SQL Server. ...
    (microsoft.public.dotnet.framework.aspnet.security)