J
Julie Cooper
Hello,
I have been attempting to configure an intregrated (AD and Windows)
authentication between two servers running an ASP.NET/SQL Server 2000
environment for months. I have not been able to make this work as
documented, no matter what KB articles I follow or how much I upgrade
software.
Right now, I have upgraded the IIS server to Windows 2003 Server with
FPSE, Service Pack 2 of .NET Framework 1.0, and set authentication to
Windows Integrated authentication only. We are using Visual
Studio.NET 2002, and upgrading to 2003 is not currently an option.
The SQL Server 2000 box has also been upgraded to Windows 2003, uses
mixed authentication, and has the AD group in the database.
The user authenticates properly to the main page, but when he attempts
to authenticate to the database (on a separate Windows 2003 Server)
via a Web Form, the following error message occurs (yes I know it's a
common one):
Error=Login failed for user '(null)'. Reason: Not associated with a
trusted SQL Server connection.
I've tried a variety of connection strings, even played with OLE DB,
but nothing works. The string I am using right now is:
"Data Source=MYSERVER;Initial Catalog=MYDB;Integrated Security=SSPI;"
In my web config fille, I also have the following settings.
<authorization>
<allow roles="mydomain\mygroup" />
<deny users="*" />
</authorization>
<identity impersonate="true" />
The AD group has been granted public, datareader, and datawriter
permission in the SQL Server database, and basic permissions on the
web site. Standard database password and userid connection strings
work, but that's not acceptable for this application.
I do not have DBA or Administrator access to the SQL server box, so if
the problem is on that end, I need an explanation in very plain terms
to convey to the DBA as to what needs reconfiguring.
Please email me as well as post to the groups, as I am desparate for
an answer, and the next step is a support ticket with Microsoft that
will have to be coordinated amongst organziations and vendors. Need I
say more?
Thanks in advance,
Julie Cooper
(e-mail address removed);
(e-mail address removed)
I have been attempting to configure an intregrated (AD and Windows)
authentication between two servers running an ASP.NET/SQL Server 2000
environment for months. I have not been able to make this work as
documented, no matter what KB articles I follow or how much I upgrade
software.
Right now, I have upgraded the IIS server to Windows 2003 Server with
FPSE, Service Pack 2 of .NET Framework 1.0, and set authentication to
Windows Integrated authentication only. We are using Visual
Studio.NET 2002, and upgrading to 2003 is not currently an option.
The SQL Server 2000 box has also been upgraded to Windows 2003, uses
mixed authentication, and has the AD group in the database.
The user authenticates properly to the main page, but when he attempts
to authenticate to the database (on a separate Windows 2003 Server)
via a Web Form, the following error message occurs (yes I know it's a
common one):
Error=Login failed for user '(null)'. Reason: Not associated with a
trusted SQL Server connection.
I've tried a variety of connection strings, even played with OLE DB,
but nothing works. The string I am using right now is:
"Data Source=MYSERVER;Initial Catalog=MYDB;Integrated Security=SSPI;"
In my web config fille, I also have the following settings.
<authorization>
<allow roles="mydomain\mygroup" />
<deny users="*" />
</authorization>
<identity impersonate="true" />
The AD group has been granted public, datareader, and datawriter
permission in the SQL Server database, and basic permissions on the
web site. Standard database password and userid connection strings
work, but that's not acceptable for this application.
I do not have DBA or Administrator access to the SQL server box, so if
the problem is on that end, I need an explanation in very plain terms
to convey to the DBA as to what needs reconfiguring.
Please email me as well as post to the groups, as I am desparate for
an answer, and the next step is a support ticket with Microsoft that
will have to be coordinated amongst organziations and vendors. Need I
say more?
Thanks in advance,
Julie Cooper
(e-mail address removed);
(e-mail address removed)