Logon failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Waldy - 25 Mar 2008 16:43 GMT

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.

Reply to this Message

Ekrem Önsoy - 25 Mar 2008 23:56 GMT

Mostly you get this error because of trying to log in to a SQL Server
Instance using a Windows Account Login \ Windows Authentication but you are
not a member of the trusted domain so you get this error.

Signature

Ekrem Önsoy

> Hi there,
> I don't know if this is an IIS or SQL Server issue. I have
[quoted text clipped - 10 lines]
> do
> I make it work as intended.

Reply to this Message

Erland Sommarskog - 26 Mar 2008 00:32 GMT

> 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
[quoted text clipped - 4 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.

As far as I understand, best practice with IIS is to use an SQL
login with SQL Server. But an IIS forum surely has greater expertise
on the issue.

Signature

Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx

Reply to this Message

Jan - 27 Mar 2008 10:11 GMT

Waldy,

This has something to do with inner restrictions of NTLMv2 authentication:
it cannot pass over 2 hops (machine boundaries). Your client + IIS + SQL
makes 3.
I think the easiest would be to activate mixed security and create an sql
account to be used in your IIS. (Although then you lose track of which user
is accessing which data)

regards,
Jan

> Hi there,
> I don't know if this is an IIS or SQL Server issue. I have an
[quoted text clipped - 5 lines]
> at a customer site however, and they want the server left as it is. How do
> I make it work as intended.

Reply to this Message