If you get a 401.3, it means that the IUSR account has the right
name/password, but the files are physically not ACL'd to give read access to
the IUSR account.
Make sure that your files are actually ACL'd to allow access to
IUSR_machinename. I suspect that when you repaired that directory's content,
you inadvertently brought over other ACLs such that IUSR no longer has
access.
All anonymous access means is that IUSR_machinename is automatically used to
access resources. It does *not* mean that resources are automatically
accessible to everyone. You can still deny access to IUSR_machinename to
deny anonymous access.
--
//David
IIS
http://blogs.msdn.com/David.Wang This posting is provided "AS IS" with no warranties, and confers no rights.
//
[quoted text, click to view] "RIP-C-B" <RIP-C-B@discussions.microsoft.com> wrote in message
news:47D4CB09-82AE-421C-95CD-D92876FBE7D0@microsoft.com...
Somebody gained access to one of my admins accounts on our website early
this
morning, and was using it to post a bunch of profanity and slander. In the
heat of the moment i quickly opened the properties to the web and changed
the
default directory to a different directory (one where the only file was a
default page saying down for repair).
After i repaired the damage he did to our files, i set the directory back to
the original, and now when people try accessing the site, they get the
windows popup asking for a user and pass. Anonymous is enabled with the
iusr
account. if i type in an admins account into that box it loads fine. from
what i have gathered is the password entered in the webs directory security
properties for iusr_machinename is incorrect. All the other webs (there are
many) work fine for anonymous access. The permissions are set on the folder
to allow iusr to read,execute and list.
any ideas?