Re: Security Delegation between IIS and SQL Server

From: Hannes Mayer (hmayer@mis.at)
Date: 02/24/03


From: "Hannes Mayer" <hmayer@mis.at>
Date: Mon, 24 Feb 2003 16:28:24 +0100


Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'

I am sure i use tcpip - server and client a configured to only tcpip - sql
server manager shows me the libraries used.

The Connection Work if i open the Webpage on the Server direct.
If I a open the webpage from an other workstation with the same user then i
get an "Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'" on the sql
server. (In the web page i get the Error number "-2147217843" with no
description)
IIS must get the correct login information (because there are only read
rights for "Domain Users" on the files - and i get the correct file - my
errorhandler show me the errormessage)
Form the server each connection - IIS - Query Analyser and so on work - it
works too if I specifiy a username and password in the connection but i
cannot do this because the application work with different rights definied
in the database.

I cannot enable auditing, because therefore i must enable auditing for the
whole domain - therefore i dont get a OK.

any suggestings?
thanks

"Jeff Cochran" <jcochran.nospam@naplesgov.com> wrote in message
news:3e602909.2771337512@news.easynews.com...
> >2 Domain Controller
> >-DC1 is IIS with an ASP Web Application
> >-DC2 is SQL Server with the Database for the ASP Application
> >
> >Now i need Windows NT Authentication for the WebPage and for the
Database,
> >but the ADO Connection doesn´t work for a simple domain user.
> >
> >So what i have done:
> >- SQL Server uses only TCPIP:1433
> >- SQL Server run under Domainuser XY
> >- With SetSPN registered a Service Principal Name for the SQL Server on
Port
> >1433
> >- Domain Controllers are Default "Trusted for Delegation"
> >- Testuser - only member of Domain users - "Trusted for Delegation"
> >activated
> >- IIS Web App - only NT Auth.
> >- Testuser is a user in the SQL DB and hast correct Rights
> >- ADO Connection String is:
> > >WITH objADOConn
> > > .PROVIDER = "SQLOLEDB"
> > > .COMMANDTIMEOUT = 30
> > > .CONNECTIONTIMEOUT = 30
> > > .CURSORLOCATION = ADODB.adUseServer
> > > .PROPERTIES("INTEGRATED SECURITY") = "SSPI"
> > > .PROPERTIES("DATA SOURCE") = "DC2"
> > > .PROPERTIES("INITIAL CATALOG") = "MISAT"
> > > .PROPERTIES("PROMPT") = ADODB.adPromptNever
> > > .Properties("Application Name") = "MISAT_WEB"
> > >End With
> >
> >
> >Why does this not work - where else could be the problem - any
suggestions?
>
> Define "does not work" and we may beable to help. Error messages?
> Can you run Query Analyzer? Does this work embedding a user/password
> in the connection? Many issues are possible here...
>
> Jeff



Relevant Pages

  • Re: Connection issues between .Net framwok and SQl Express 2005
    ... You will no longer need the database MDF file name in the connection string. ... simply attach the ASPNETDB.mdf to SQL Server permenantly, ... as USER INSTANCE on existing SQL Server Express, ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Performance of ODBC
    ... if you have a software firewall; forward 1433/1434 to your server ... I've now created my own server with SQL Server 2005 Express, ... glitch concerns the Upsizing Wizard. ... I originally set up my ODBC connection via ...
    (microsoft.public.access.adp.sqlserver)
  • SQL 2005 Express and VS .Net 2003 wizard error More options
    ... Open the server explorer panel ... Go to the Provider tab and select SQL NAtive Client (DON'T use oledb ... Go back to the Connection tab and carry on setting up the connection ... I have installed Visual Studio 2005 Professional and then Visual Studio ...
    (microsoft.public.sqlserver)
  • Re: Timeout problem with SS2K, VS03
    ... I noticed calls in sql profiler: ... This is the server side debug stored procedure. ... a timeout issue that I cannot identify the source of. ... transaction is committed and the connection is closed cleanly and all ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: Cannot connect to SQL Express on 2003 Machine from XP machine
    ... listening on UDP 1434 using netstat -abn, ... And i double checked the connection string, and i did have it the right ... But I have another 2000 server that I can connect to fine, ... I am trying to connect from an XP SP2 machine remotely to a SQL Express ...
    (microsoft.public.sqlserver.connect)