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

From: Justin (Justin_at_discussions.microsoft.com)
Date: 07/01/05 

Date: Fri, 1 Jul 2005 10:05:03 -0700

Yeah, I was afraid that that was the answer. At least I can rest assured in
my knowledge that the answer wasn't completely obvious. :-)

I was trying to get this working so I could develop on my local machine, no
intention of putting it into production in this way. Actually, the project
is already in production where the IIS server and SQL are on the same domain
and no impersonation problems there.

Well, thanks for the time.

Justin

"Joe Kaplan (MVP - ADSI)" wrote:

> Yeah, I'm not sure if you can get this to work in that case. You would
> essentially be looking for the "hack" way of doing this with matching local
> machine accounts. I'm not really too familiar with how or why that even
> works, so I'm probably not the right guy to ask.
>
> Is there any way that you can actually just get this working correctly,
> possibly by using a machine that is a domain member? It seems like a bad
> idea to pin your integration scenario on what is basically a hack.
>
> Joe K.
>
> "Justin" <Justin@discussions.microsoft.com> wrote in message
> news:3BB8FB68-FB4F-4B8B-AB9A-A7B9F37B89C2@microsoft.com...
> > Hi Joe,
> >
> > Thank you for responding. Unfortunately I'm running the webserver on my
> > computer, which is not on the same domain as the SQL Server. This is
> > because
> > I just VPN into my client to do my work. I know that there is "the rub".
> > :-)
> >
> >
> > "Joe Kaplan (MVP - ADSI)" wrote:
> >
> >> 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
> >>
> >>
> >>
>
>
>

Relevant Pages

  • Re: DAO vs ADO
    ... In the past I have had my differences with Joe as he comes from the SQL side ... I am not sure if SQL Server 2005 has blown it or not, ... Access is a wonderful front end development tool for database developers ... maybe we could let all the programmers go and use whatever the latest ...
    (microsoft.public.access.conversion)
  • Re: DAO vs ADO
    ... In the past I have had my differences with Joe as he comes from the SQL side ... I am not sure if SQL Server 2005 has blown it or not, ... Access is a wonderful front end development tool for database developers ... maybe we could let all the programmers go and use whatever the latest ...
    (microsoft.public.access.adp.sqlserver)
  • Re: Production statistics data storage
    ... If you're concerned with performance, LINQ should not be considered--not until they figure out how to get it working. ... SQL Server is fully capable of good performance--even when polled frequently. ... Production statistics with quality indications is a major part of the ... statistics over number of produced units and percent produced in each grade. ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: Is the msdn sql enterprise 2005 version downloadable production?
    ... Jasper Smith (SQL Server MVP) ... >> keys so I don't see why it matters what media you install it from). ... >> Edition on MSDN subscriber downloads cannot be installed in a production ...
    (microsoft.public.sqlserver.setup)
  • Re: Cost of ownership: MV vs. SQL Server
    ... >>> Licensing for SQL server on par with or lower than most MV ... I'm doing phone chats with people related to their production ... environments too so I'm not just theorizing on it. ... opinions on this matter for customers of this var, ...
    (comp.databases.pick)