G
Guest
Hi,
My development machine is running Win XP SP2 and IIS. I'm developing an
ASP.NET application on this machine that accesses data from a SQL Server
database on another machine.
That machine that contains the SQL Server runs Win 2003 and is the primary
controller for our domain.
When I connect I receive the error "Login failed for user '(null)'. Reason:
Not associated with a trusted SQL Server connection."
My connection string is ""integrated security=SSPI;data
source=SDI-SERVER01;persist security info=False;initial catalog=Contacts"
In IIS, I have anonymous access checked and Integrated Windows Security set.
In SQL Server, I have included the ASPNET account as a login, and also as a
user within the database I'm accessing.
This problem seems to have been encountered plenty of times, and there are
quite a few solutions (eg impersonation, sql server authentication, etc), but
I'd like to find out why the error is occurring.
Am I right in saying that the problem is happening because the local ASPNET
account credentials are being passed through and they are not seen as being
the same as the credentials for the ASPNET account on the server?
If someone could help my understanding or point me in the direction of some
info, that would be great.
Thanks,
David.
My development machine is running Win XP SP2 and IIS. I'm developing an
ASP.NET application on this machine that accesses data from a SQL Server
database on another machine.
That machine that contains the SQL Server runs Win 2003 and is the primary
controller for our domain.
When I connect I receive the error "Login failed for user '(null)'. Reason:
Not associated with a trusted SQL Server connection."
My connection string is ""integrated security=SSPI;data
source=SDI-SERVER01;persist security info=False;initial catalog=Contacts"
In IIS, I have anonymous access checked and Integrated Windows Security set.
In SQL Server, I have included the ASPNET account as a login, and also as a
user within the database I'm accessing.
This problem seems to have been encountered plenty of times, and there are
quite a few solutions (eg impersonation, sql server authentication, etc), but
I'd like to find out why the error is occurring.
Am I right in saying that the problem is happening because the local ASPNET
account credentials are being passed through and they are not seen as being
the same as the credentials for the ASPNET account on the server?
If someone could help my understanding or point me in the direction of some
info, that would be great.
Thanks,
David.