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

Second thoughts ( besides finding out the process account user ) :

re:
>I've enabled anonymous access, setting it to the correct domain account,

Was that account NT Authority\Anonymous
.... or YourWebServerName\Anonymous ?

re:
> The specific domain account has been granted
> the correct permissions in sql server

Was that account NT Authority\Anonymous
.... or YourWebServerName\Anonymous ?

re:
> <identity impersonate="true" />

Since you *are* impersonating, it's the account that ASP.NET
is using as impersonation the one which needs permissions
everywhere.

That means the local user permissions, the SQL Server, etc.




Juan T. Llibre
ASP.NET MVP
http://asp.net.do/foros/
Foros de ASP.NET en Español
Ven, y hablemos de ASP.NET...
======================

"Buggyman" <Buggyman@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:75311680-27E8-4BF4-AC8C-37E018E0E441@xxxxxxxxxxxxxxxx
> Hi,
> I'm having problems with good old error... Login failed for user 'NT
> Authority\Anonymous logon'.
>
> The default web page comes up fine, but when the user attempts to log in
> (which checks stored usernames in the database etc) then the error occurs.
>
> a) The Web server is on a seperate box to SQL Server.
> b) I'm using forms authentication.
> c) I've enabled anonymous access, setting it to the correct domain account,
> and am not allowing IIS to control the password.
> d) The specific domain account has been granted the correct permissions in
> sql server
>
> e) web.config file is basically as follows..
>
> <?xml version="1.0" encoding="utf-8" ?>
> <configuration>
> <system.web>
> <compilation defaultLanguage="vb" debug="true" />
> <customErrors mode="RemoteOnly" />
> <authentication mode="Forms" />
> <authorization>
> <allow users="*" /> <!-- Allow all users -->
> </authorization>
> <identity impersonate="true" />
> <trace enabled="false" requestLimit="100" pageOutput="true"
> traceMode="SortByTime" localOnly="true" />
> <sessionState
> mode="InProc"
> stateConnectionString="tcpip=127.0.0.1:42424"
> sqlConnectionString="data source=127.0.0.1;Trusted_Connection=yes"
> cookieless="false"
> timeout="20"
> />
> <globalization requestEncoding="utf-8" responseEncoding="utf-8" />
> </system.web>
> <appSettings>
> <add
> key="DBConnectionString"
> value="server=servername;database=mydb;Integrated Security=SSPI"/>
> </appSettings>
> </configuration>
>
> It works fine from the web server.
>
> If anyone has any ideas, this would be most appreciated.
>
> Also (not sure if this will help me or not), how can I tell which user the
> aspnet worker process is running under?
>
> Many thanks.
>
> --
> Many thanks.
> :)


.

Relevant Pages

  • Re: Login failed for user NT AUTHORITYANONYMOUS LOGON
    ... >>I've enabled anonymous access, setting it to the correct domain account, ... >> the correct permissions in sql server ... > That means the local user permissions, the SQL Server, etc. ... >> c) I've enabled anonymous access, setting it to the correct domain account, ...
    (microsoft.public.dotnet.framework.aspnet)
  • Login failed for user NT AUTHORITYANONYMOUS LOGON
    ... The Web server is on a seperate box to SQL Server. ... I've enabled anonymous access, setting it to the correct domain account, ... It works fine from the web server. ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Linked Server Connection Problem
    ... Use SQL authentication to connect to the SQL server from the client, ... set the domain account used to start SQL Server to have permissions in the ... Establish a SPN for your domain account which will enable Kerberos ... Load the Active Directory Users and Computers MMC snap-in. ...
    (microsoft.public.sqlserver.connect)
  • Re: SQL Services account question...
    ... I wish you'd say the reason of not using a domain account as a service account for the SQL Server. ... Backup operations are performed by SQL Server service, at this point I don't know what goes on under hood exactly but SQL Server service may be needed to communicate to the AD for validation of the database owner and as the SQL Server service is a local one, it can't achieve this task. ... > Source: Security Event ID: 537 ...
    (microsoft.public.sqlserver.security)
  • Re: Problems changing the password for the service account in SQL
    ... Adding the domain account which runs SQL Server into SQL Server doesn't ... Server if it is running under the domain account. ... Admin-SQL, Logon Exec - exception from ...
    (microsoft.public.sqlserver.security)
Loading