Re: Problem running ASP.NET 2.0 on Win2K domain controller
- From: "Rob Roberts" <robr@xxxxxxxxxxxxxxxx>
- Date: Fri, 10 Feb 2006 09:08:27 -0700
Luke,
This problem may be caused that the account used by ASP.NET ('aspnet' or
'network service') hasn't been add to a policy, you may opened the Default
Domain Controllers policy and added system to the Impersonate a Client
After Authentication right and rebooted the box.
Thanks for the response, but as I mentioned in my initial post, I already
tried that and it didn't work.
The .NET 2.0 installation set ASP.NET up to run as the IWAM_MachineName
user. I gave this user the "Impersonate a client after authentication"
right, rebooted, and tried my test aspx page again. The same error still
occurred.
Are you saying that I need to give the SYSTEM account the "Impersonate a
client after authentication" right? That doesn't make much sense to me, but
I tried it anyway and it also had no effect. (I still get the same error
when trying to access an aspx page on the server.)
Any other ideas?
Thanks,
--Rob Roberts
.
- Follow-Ups:
- Re: Problem running ASP.NET 2.0 on Win2K domain controller
- From: Luke Zhang [MSFT]
- Re: Problem running ASP.NET 2.0 on Win2K domain controller
- References:
- Problem running ASP.NET 2.0 on Win2K domain controller
- From: Rob Roberts
- RE: Problem running ASP.NET 2.0 on Win2K domain controller
- From: Luke Zhang [MSFT]
- Problem running ASP.NET 2.0 on Win2K domain controller
- Prev by Date: Use Form Authentication to control visibility of tag for logged-in users
- Next by Date: Cannot open log Application on machine
- Previous by thread: RE: Problem running ASP.NET 2.0 on Win2K domain controller
- Next by thread: Re: Problem running ASP.NET 2.0 on Win2K domain controller
- Index(es):
Relevant Pages
|
