Re: problems with msde access from asp.net app

From: Mary Chipman (mchip_at_nomail.please)
Date: 09/28/03


Date: Sun, 28 Sep 2003 14:49:53 -0400


How the ASPNET account is configured is controlled by the
machine.config file on each machine in the processModel section. Your
default choices are to set the username to either system (not
recommended) or machine. You can also elect to run under a custom user
account for which you supply a username and password in machine.config
(can be encrypted in v1.1). The error message you got is telling you
that you are running under the system account on the production box,
and most likely are running under machine on your test server.

Grab the ASP.NET security best practices whitepaper, which explains
all this and more in great detail.
http://www.microsoft.com/downloads/release.asp?ReleaseID=44047
 
-- Mary
MCW Technologies
http://www.mcwtech.com

On Fri, 26 Sep 2003 22:27:30 +0100, "Ian" <no@spam> wrote:

>hi
>
>i have a problem with database access (SQL Server/MSDE) on my production
>server.
>
>the asp.net web app works fine in test.
>
>on the production server, it won't connect to the database!
>
>i'm pretty sure i have set up the ASPNET login correctly, with permissions
>identical to my test system
>
>it only fails when trying to use a Trusted connection for ASPNET - using an
>SQL connection.for use 'sa' works just fine.
>
>the only clue i have is a SQL security log entry of "login failed for 'NT
>AUTHORITY\NETWORK SERVICE'"
>
>if i add a login for 'NT AUTHORITY\NETWORK SERVICE' and the NamedPipes
>protocol, i can connect OK. This is good, but i'd love to know why ASPNET
>won't connect!
>
>Thanks
>Ian
>
>



Relevant Pages

  • Re: aspnet_wp wont execute on windows server 2003
    ... On Windows 2003, ... account but this is not the default context for ASP.Net. ... > I am struggling with this windows 2003 server with asp.net. ... > I can use ASPNET account as a local account. ...
    (microsoft.public.dotnet.framework.aspnet.security)
  • Re: userName="machine" didnt work
    ... The .210 dlls I had for ASP.NET are newer than the .42 dlls. ... Deleted the ASPNET account from "Local Users and Group - Users". ... This problem occurs because the process model user account (in our case, ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: userName="machine" didnt work
    ... The .210 dlls I had for ASP.NET are newer than the .42 dlls. ... Deleted the ASPNET account from "Local Users and Group - Users". ... This problem occurs because the process model user account (in our case, ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: userName="machine" didnt work
    ... so only the ASP.NET related dlls ... Deleted the ASPNET account from "Local Users and Group - Users". ... This problem occurs because the process model user account (in our case, ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Server 2003 problem with asp.net.
    ... ASP.Net does not run under ASPNET user account. ... The issue here is ASP.Net not active on Windows2003 server by default. ...
    (microsoft.public.dotnet.framework.aspnet.security)