Re: Windows authentication/impersonation.. login failed for user null?
- From: "SAL" <SAL_@xxxxxxxx>
- Date: Tue, 19 Dec 2006 10:41:44 -0800
Chris, I just, agonizingly, went through this same scenario. Here was my
problem.
In IIS, I opened the properties of my web application and I had to change
the default user (on the Directory Security Tab) that was entered there to
my domain account (or some other user's domain account that could log on to
the machine that SQL Server was residing on). Then I had to uncheck the Let
IIS manage the password checkbox and enter in my own password. I had to
leave Integrated Windows Authentication checked.
In my web.config, I had to have this tag:
<identity impersonate="true" />
When publishing, I believe I had to uncheck the Integrated Windows
Authentication to make it work on machines other than my dev box.
HTH
S
"Not Me" <Not.Me@xxxxxxxxxxxxxxx> wrote in message
news:1166543081.728376@xxxxxxxxxxxxxxxxxxxx
Hey,
We have an sql server 2000 machine and IIS 6 machine running seperately
but on the same domain. I can connect fine to the database without using
impersonation, but when it's enabled I get the error:
"Login failed for user '(null)'. Reason: Not associated with a trusted SQL
Server connection."
When I check System.Security.Principal.WindowsIdentity.GetCurrent().Name I
get the valid domain user that I would expect, why isn't this user being
checked against the sql server?
cheers for any help,
Chris
.
- Follow-Ups:
- References:
- Prev by Date: Re: drop down list problems
- Next by Date: Re: drop if brackets
- Previous by thread: Re: Windows authentication/impersonation.. login failed for user null?
- Next by thread: Re: Windows authentication/impersonation.. login failed for user null?
- Index(es):
Relevant Pages
|
Loading