On Sep 24, 10:58 pm, Homer <HomerS...@gmail.com> wrote:
> On Sep 23, 8:29 am, Alexey Smirnov <alexey.smir...@gmail.com> wrote:
>
>
>
>
>
> > On Sep 22, 1:47 am, Homer <HomerS...@gmail.com> wrote:
>
> > > Hi,
>
> > > I have an ASP.NET 2.0 Intranet app that works fine on a test server
> > > running on Win2003 Server with IIS 6.0. However, it fails when I port
> > > it over to the production server running on the same OS. I compared
> > > all the configurations and everything matches. I then re-run the
> > > aspnet_regiis; I even granted "NT AUTHORITY\NETWORK SERVICE" full
> > > access to aspnet_Membership and aspnet_Roles. I don't know why the
> > > app uses a local user account instead of the "NT AUTHORITY\NETWORK
> > > SERVICE" account. Please help me.
>
> > Hi Jonathan
>
> > the problem is in the database and not in the ASP.NET. Go to the
> > database and check if windows authentication is allowed and the aspnet
> > account is in the user list. You can also create a new database
> > account and use it to open database from ASP.NET application.
>
> > Hope this helps
>
> Hi,
>
> My app is an asp.net 2.0 app with no impersonation. By default, I
> expect Network Service be used. The database uses Windows
> Authentication. I added the "NT AUTHORITY\NETWORK SERVICE account to
> the database. I checked the security setting on the app folder at C:
> \Inetpub\wwwroot\HumanResources and verified that NETWORK SERVICE is
> added to the folder. Am I missing anything here?
>
> Thanks,
> Jonathan Kha- Hide quoted text -
>
> - Show quoted text -
Hi Jonathan
try to add into your pages
User: <%=User.Identity.Name%>
to see what user is running your application. It looks like in the
second case you would have the companyDomain\BOSIIS$
Check what authentication mode you have and also check the Security
tab on IIS to see if there any difference.
Hope it helps
|
Similar Threads
