OK, I guess this is a good location for this question.
I have a W2K server, running IIS 6 and Active Directory Services. I have an ASP.Net application off the root web directory named "Apps". Within the IIS Manager I have the Authentication method set to "Anonymous Access" as well as "Authenticated Access" using "Integrated Windows Authentication" for both the root web and the "Apps" sub-directory. All files and directories under the "Apps" folder are set in this manner.
The web config file is set to use "Windows" for Authentication and "*" for Authorization.
Using Explorer I have changed the permissions for one file in the "Apps" directory. For this file, let's call it "myfile.aspx", I have removed the "Everyone" group. The permissions for this file are as follows:
Creator Owner - Full Control
System - Full Control
mydomain\Administrators - Full Control
mydomain\MyGroup - Read, Read/Execute
If I attempt to access any file on this web via a web browser it works as it should with the exception of this single file, "myfile.aspx". When attempting to access this file it will ask for a username/password/domain and will not accept anyone, including anyone from the "Administrators" or "MyGroup" groups.
The error I get in the browser is:
Server Error in '/Apps' Application.
--------------------------
----------
----------
----------
----------
----------
----
Access is denied.
Description: An error occurred while accessing the resources required to serve this request. You might not have permission to view the requested resources.
Error message 401.3: You do not have permission to view this directory or page using the credentials you supplied (access denied due to ACLs). Ask the Web server's administrator to give you access to 'c:\inetpub\wwwroot\apps\m
yfile.aspx
'.
--------------------------
----------
----------
----------
----------
----------
----
Version Information: Microsoft .NET Framework Version:1.1.4322.573; ASP.NET Version:1.1.4322.573
This is the same basic configuration I use on other web servers for security and have not had this problem before. I have another server within this domain that is configured in the same manner that works although it is not an ASP.Net application. I have tried this from systems logged into the domain and from systems not logged into the domain with the same results.