Re: Windows authentication/impersonation.. login failed for user null?
- From: "Norman Yuan" <NotReal@xxxxxxxxxxx>
- Date: Tue, 19 Dec 2006 10:55:14 -0700
You must make sure that domain user account or the domain security group
(that domain user account is in) ia mapped to a SQL server login/Sql Server
database user. That is, not all domain user account is automatically allowed
to access SQL Server, you need to explicitly create SQL Server login that
maps to a domain group/user, and then make specific SQL Server login as
given database's user/owner...
"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: Populating Dropdownlist in Formview
- Next by Date: Re: Windows authentication/impersonation.. login failed for user null?
- Previous by thread: Windows authentication/impersonation.. login failed for user null?
- Next by thread: Re: Windows authentication/impersonation.. login failed for user null?
- Index(es):
Relevant Pages
|