11-17-05 11:12 PM
You say that file permissions have been checked, but this still sounds to me
like a permissions problem. Depending on the circumstances, the
IWAM_machinename, IUSR_machinename AND the user accounts used might be
missing needed permissions. And the permissions don't need to be applied
just to the content files of your web page, but to some Windows system files
as well. You may also need to grant more than just read permissions for
some of those places as well.
I would suggest troubleshooting this like any other file permission problem.
Checking the iis web server log after reproducing the web site failure may
show you what account if any is being denied access to what file. Look of
course for 400-level error messages relating to authentication and rights
first, and possibly 500-level messages as well. Next, run filemon [file
monitor] free from www.sysinternals.com on the server while reproducing the
web site failure.
You can also enable NTFS file access failure auditing for all users on the
content files, windows folder and program files folder, then reproduce the
error and check the Windows security event log for failures.
http://securityadmin.info/faq.asp#auditing
I'm guessing that when you are not being asked to authenticate, the web
browser has silently authenticated for the user, and you are asked to
authenticate when the browser is told that the user authentication failed
due to insufficient permissions.
Just a guess, but if in the IIS server properties for that folder you have
chosen Medium or High for Application isolation, then the IWAM_machinename
account by default is used to access those files, while IUSR_machinename is
used by default to access static files like HTML. This is most true when
anonymous authentication is used, but some of the articles I googled suggest
that this might also happen under some other scenarios as well.
Some articles suggest that in some instances, the user configured to run COM
/ DCOM might come into play, depending. I'm less knowledgeable in that
area, but running dcomcnfg or checking for user accounts in the Component
Services control panel might be something to try if all else fails.
You may have already seen these, but more information on what IIS
permissions are required where are at:
How to set secure NTFS Permissions on IIS directories and log files -
http://support.microsoft.com/?kbid=310361
Minimum NTFS file permissions required for IIS:
http://support.microsoft.com/?kbid=187506
If all that fails, some of these articles might have some other suggestions
and information:
http://www.joelonsoftware.com/print...c
o.html
www.windowsitpro.com/Articles/Index.cfm?ArticleID=45549
[url]www.google.com/search?q=iwam+anonymous+application-isolation+basic+OR+integrated[/
url]
"mushu" <tim.m.valdez@gmail.com> wrote in message
news:1132004889.746492.46310@z14g2000cwz.googlegroups.com...
> IIS 5.0 in a domain. IIS has Basic & Integrated selected, NOT
> anonymous. All users have I.E. browser. All users are members of the
> same domain. IIS Basic Auth MMC section has the correct domain entered.
> There is no global.asa file in the directory. All links in the .asp
> page have been validated and checked to ensure that they exist and have
> the correct ACL's.
>
> I'm wondering why the .asp pages are prompting for login but the .htm
> pages are not. I searched but was unable to find any solution to this
> question, however I see that others have asked it before...just no
> responses.
>
> TIA!
>
[ Post a follow-up to this message ]
| 
