Re: Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'

From: Joe Kaplan \(MVP - ADSI\) (joseph.e.kaplan_at_removethis.accenture.com)
Date: 07/01/05

  • Next message: Justin: "Re: Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'" 
    Date: Fri, 1 Jul 2005 08:55:17 -0500

    Is the SQL server box in the same domain as the web server (or do they have
    a trust)? When you impersonate via web.config this way, it should work.
    There should be no reason to have machine accounts with matching IDs if the
    domain stuff is configured correctly.

    As you have discovered, these types of issues can be really painful to debug
    as there is no well known, straightforward technique for diagnosing what
    went wrong with your impersonation.

    Joe K.

    "Justin" <Justin@discussions.microsoft.com> wrote in message
    news:2CDF22AC-CA14-490D-8799-927DEF54B141@microsoft.com...
    >I know this has been out there a thousand times. I've looked and looked
    >and
    > can't find anything that will solve my problem. I'm not even sure it is
    > solveable.
    >
    > I have a client that I VPN into. My computer is not on their domain.
    >
    > I have a local webservice and I was to use to access a SQL server on their
    > domain. I have set impersonation to true and put the username and
    > password
    > of the domain user in the web.config.
    >
    > <identity impersonate="true" userName="domain\user" password="password" />
    >
    > I also created a local user on my computer with the same username and
    > password. (This is how I was able to get the webservice asmx page to
    > successfully load and display the available webservices).
    >
    > However, when I try to actually call the webservice and access the sql
    > server I get the classic "Login failed for user 'NT AUTHORITY\ANONYMOUS
    > LOGON'" error.
    >
    > I've tried everything I can think of, even creating a
    > WindowsImpersonationContext object. No luck.
    >
    > The sql server *has* to use integrated security so a connection string is
    > "right out".
    >
    > Any ideas?
    >
    > Thanks,
    >
    > Justin

  • Next message: Justin: "Re: Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'"

    Relevant Pages

    • Re: Login failed for user NT AUTHORITYANONYMOUS LOGON
      ... which is not on the same domain as the SQL Server. ... > went wrong with your impersonation. ... >> I have a local webservice and I was to use to access a SQL server on their ... I have set impersonation to true and put the username and ...
      (microsoft.public.dotnet.framework.aspnet.security)
    • Re: Login failed for user NT AUTHORITYANONYMOUS LOGON
      ... >> I have a local webservice and I was to use to access a SQL server on ... I have set impersonation to true and put the username and ... >> of the domain user in the web.config. ...
      (microsoft.public.dotnet.framework.aspnet.security)
    • IIS / SQL Server impersonation
      ... I am attempting to implement impersonation from a windows application ... I have configured the host virtual directory in IIS to require windows ... the database permits Windows Authentication. ... When I try and open a connection to SQL Server: ...
      (microsoft.public.dotnet.security)
    • Re: ThreadAbort Exceptions !! HELP !!
      ... Well we checked for queued requests last night and there were none during ... Looks like our SQL server box is ... trace seems to usually point at a webservice not an aspx page. ... System.Threading.WaitHandle.WaitOne(Int32 millisecondsTimeout, Boolean ...
      (microsoft.public.dotnet.framework.webservices)
    • Re: Scalability questions....
      ... Hardware code is faster than software code (i.e. hardware SSL is faster than software SSL). ... We averaged 60 MB/sec of bandwidth and used SQL Server to log and analyze the downloads. ... But how do I write a data intensive webservice that can be ...
      (microsoft.public.dotnet.general)