wwwroot folder perms for web developer box are NOT right now?

[Guest]

Hey...
running XPPro and IIS6 on my dev box. NEVER had a problem getting my ASPEdit
software to serve up websites...till yesterday.

now, when I try to get a newly made folder (in C:\inetpub\wwwroot\Clients)
to serve up even a simple HTML file, I get that ACL 401.3 resource notice ie
access is denied!

so...after many Googles on same, I determined that somehow the wwwroot
folder, in the Security tab, is set to DENY my internet guest account access
to the file.

so...I tried to reset the complete wwwroot folder, to enable that
access...and while it "looks" like that worked, I can still no longer see ANY
HTML file in my edit software -- only files work that were already enabled.
that is, a brand new folder with a simple HTML file (even Hello World) gets
me that dang 401.3 again! yet a look at the Security tab for that new folder
shows me that the Internet Guest Account has FULL CONTROL!!!!!!

can someone help here? is there an OVERALL enabling way to allow ALL sub
folders in wwwroot to show my files? or, what am I doing wrong???

?

Jim

 

[Steven L Umbach]

Check the security permissions on the files you can not see. Possibly they
have not been changed and still have a deny permission applied either
explicity or via inheritance. When you change permissions in the advanced
page try selecting "replace entries on all child objects" if you have not
tried that yet. .

Steve

 

[Guest]

Thanks Steven....

that was EXACTLY the problem -- the sub folder had NOT a blessed perm in it...

I simply checked off the inherit box...and yup, can see it fine in my
ASPEditor.

question tho -- is there no ABSOLUTE overall way to ALWAYS have wwwroot
folder and all it's subfolders ALWAYS allow IUSR_machineName to see all files
in that environment....ie an overall way to do this once and for all?

Jim

 

[Steven L Umbach]

Permissions should not change on there own so something that had
administrator access caused it to happen. One way I can think of enforcing
it is to use a Scheduled Task to periodically make sure permisisons are
correct on that folder. You could create a batch file to do that using the
free utility fileacl or xcacls.vbs . Those are very powerful tools so test
them out on a test computer or folder with similar configuration before
putting into production.

http://support.microsoft.com/kb/825751 ---- xcacls.vbs
http://www.gbordier.com/gbtools/fileacl.htm --- flleacl


Steve