Dilan77
asked on
HTTP Error 401.3 - Unauthorized: Access is denied due to an ACL set on the requested resource
Hello
I have recently built a Software Update Service server on Windows 2003.
When I am trying to launch the config page (http://<machine_name>/SUSAdmin), I receive the following error;
You are not authorized to view this page
You do not have permission to view this directory or page due to the access control list (ACL) that is configured for this resource on the Web server.
HTTP Error 401.3 - Unauthorized: Access is denied due to an ACL set on the requested resource
The IIS version is 6.0. Anonymous access is being used with IUSR_<machine_name> account.
Any IIS gurus out there to help?
I have recently built a Software Update Service server on Windows 2003.
When I am trying to launch the config page (http://<machine_name>/SUSAdmin),
You are not authorized to view this page
You do not have permission to view this directory or page due to the access control list (ACL) that is configured for this resource on the Web server.
HTTP Error 401.3 - Unauthorized: Access is denied due to an ACL set on the requested resource
The IIS version is 6.0. Anonymous access is being used with IUSR_<machine_name> account.
Any IIS gurus out there to help?
see if IUSR_<machine_name> has READ permissions under the directory where is configured /SUSAdmin
ASKER
Do you mean the directory in C or D drive, or the directory of the web content?
I mean NTFS permissions. To see wich directory is configured under /SUSAdmin, open IIS manager, right-click SUSAdmin virtual dir, and choose Open. Then see if IUSR_<machine_name> has read permissions on that folder.
ASKER
Thanks.
The user wasn't there, I added the user and gave it READ writes, however I'm still getting this error.
The user wasn't there, I added the user and gave it READ writes, however I'm still getting this error.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
that seems to work...excellent.
is there any downside to keeping at this (apart from the need to log into the SUS site, which is not necessarily a bad thing)?
is there any downside to keeping at this (apart from the need to log into the SUS site, which is not necessarily a bad thing)?
No, it depends on your needs, but I think that a SUSAdmin site should have windows authentication, not anonymous, for security reasons. I would also restrict NTFS permissions to admins only, or something like that.
ASKER
Brilliant, thanks a lot for the prompt help