Why doesn"t ASP.NET 2.0 use the Network Service account

Hi,

I have an asp.net 2.0 Intranet app that is installed to a Win2003
Server running IIS 6.0. This production server also hosts asp.net 1.1
apps also. I isolated the two into separate application pool on the
IIS. My Intranet app loads but on login authentication, for some
strange reason, IIS passes in a network user account rather than the
Network Service account. Naturally authentication failed because the
database is set up to allow Network Service in and not the network
user account, which I know nothing about. This same Intranet app
works fine in the test server that also runs on Win2003 server with
IIS 6. I spent two days on this and I can't go any further. Does
anybody knows what is going on? Thank you for your help in advance.

Thanks,
Jon

Re: Why doesn"t ASP.NET 2.0 use the Network Service account

On Sep 22, 12:50 am, Homer wrote:
> Hi,
>
> I have an asp.net 2.0 Intranet app that is installed to a Win2003
> Server running IIS 6.0. This production server also hosts asp.net 1.1
> apps also. I isolated the two into separate application pool on the
> IIS. My Intranet app loads but on login authentication, for some
> strange reason, IIS passes in a network user account rather than the
> Network Service account. Naturally authentication failed because the
> database is set up to allow Network Service in and not the network
> user account, which I know nothing about. This same Intranet app
> works fine in the test server that also runs on Win2003 server with
> IIS 6. I spent two days on this and I can't go any further. Does
> anybody knows what is going on? Thank you for your help in advance.
>
> Thanks,
> Jon


ASP.Net is flexible and allows configuration of user account to run
its code.

By default for ASP.Net 2.0 it is process identity, which is Network
Service on IIS6 by default. If you do not see that, it means that you
either configured the Application Pool to use another user identity,
or you configured ASP.Net to use another identity.

In either case, the problem is not "why doesn't ASP.NET 2.0 use the
Network Service account", nor is it "why is IIS passing in a network
user account". The problem is "Why did the user misconfigure the wrong
user account for their application and don't even know it".

Because by default, it should just work, according to your other
configuration..


//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//

Re: Why doesn"t ASP.NET 2.0 use the Network Service account

As David says, something is up with your configuration:

Places to check:
a) What is the web application pool configured to use in IIS Manager?

b) Do you have enabled in your web.config file for the
application?

Cheers
Ken

--
My IIS Blog: www.adOpenStatic.com/cs/blogs/ken

"Homer" wrote in message
news:1190447425.532211.21630@22g2000hsm.googlegroups.com...
> Hi,
>
> I have an asp.net 2.0 Intranet app that is installed to a Win2003
> Server running IIS 6.0. This production server also hosts asp.net 1.1
> apps also. I isolated the two into separate application pool on the
> IIS. My Intranet app loads but on login authentication, for some
> strange reason, IIS passes in a network user account rather than the
> Network Service account. Naturally authentication failed because the
> database is set up to allow Network Service in and not the network
> user account, which I know nothing about. This same Intranet app
> works fine in the test server that also runs on Win2003 server with
> IIS 6. I spent two days on this and I can't go any further. Does
> anybody knows what is going on? Thank you for your help in advance.
>
> Thanks,
> Jon
>

Re: Why doesn"t ASP.NET 2.0 use the Network Service account

On Sep 23, 5:37 am, "Ken Schaefer"
wrote:
> As David says, something is up with your configuration:
>
> Places to check:
> a) What is the web application pool configured to use in IIS Manager?
>
> b) Do you have enabled in your web.config file for the
> application?
>
> Cheers
> Ken
>
> --
> My IIS Blog:www.adOpenStatic.com/cs/blogs/ken
>
> "Homer" wrote in message
>
> news:1190447425.532211.21630@22g2000hsm.googlegroups.com...
>
>
>
> > Hi,
>
> > I have an asp.net 2.0 Intranet app that is installed to a Win2003
> > Server running IIS 6.0. This production server also hosts asp.net 1.1
> > apps also. I isolated the two into separate application pool on the
> > IIS. My Intranet app loads but on login authentication, for some
> > strange reason, IIS passes in a network user account rather than the
> > Network Service account. Naturally authentication failed because the
> > database is set up to allow Network Service in and not the network
> > user account, which I know nothing about. This same Intranet app
> > works fine in the test server that also runs on Win2003 server with
> > IIS 6. I spent two days on this and I can't go any further. Does
> > anybody knows what is going on? Thank you for your help in advance.
>
> > Thanks,
> > Jon- Hide quoted text -
>
> - Show quoted text -

Hi,

I created a new application pool in IIS 6 to isolate my asp.net 2.0
apps from asp.net 1.1 apps. I left the pool configuration at default
and verified that the predefined identity is "Network Service". I
have the same configuration in the test server and it works just
fine. I do not turn on imperation in my app so by default IIS should
use the Network Service account. Here's my web.config:

















slidingExpiration="true" />



type="System.Web.Security.SqlMembershipProvider"
connectionStringName="csEmployeeSelfService"
enablePasswordReset="true" requiresQuestionAndAnswer="false"
applicationName="EOIntranet" passwordFormat="Hashed"
maxInvalidPasswordAttempts="5" minRequiredPasswordLength="7"
minRequiredNonalphanumericCharacters="0" passwordAttemptWindow="10"
passwordStrengthRegularExpression=""/>


defaultProvider="CustomizedRoleProvider">

applicationName="EOIntranet"
name="CustomizedRoleProvider"
type="System.Web.Security.SqlRoleProvider" />





>




















type="System.Web.XmlSiteMapProvider" securityTrimmingEnabled="true"/>





Thanks,
Jon

Re: Why doesn"t ASP.NET 2.0 use the Network Service account

The impersonation could eventually be set at the root level.
To make sure set

Leave no room for assumptions.

Other options are to set a sample .ashx file on the AppDomain where you're
seeing this and dump the WindowsIdentity account.

Tiago Halm