ACL Problems after OWA Redirect

Posted on 2006-11-16
Medium Priority
Last Modified: 2008-02-01
I followed the directions from KB 555053 (http://support.microsoft.com/default.aspx?scid=kb;en-us;555053) exactly but have ran into an interesting AACL issue. I can not verify this, but our Exchange server (before it was an Exchange Server) had another computer name before it was joined to the domain, renamed, and made the Exchange server. Now I see that the IUSR_*** account is for the machine's previous name and not the current name. The ACL on the default web site is to allow Anonymous Accesss via the IUSR_**OldMachineName** account. I do not see a IUSR account for the new machine name. What do I need to do here? After following the instructions in  the article (which I have succesfully followed on other 2003 ExServers)- it will not redirect to HTTPS- nor will it redirect to /exchange by browsing to the default website. I get the follwoing error when I browse using either method (http to https or *.*.com to *.*.com/exchange) :

" 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.

Please try the following:

Contact the Web site administrator if you believe you should be able to view this directory or page.
Click the Refresh button to try again with different credentials.
HTTP Error 401.3 - Unauthorized: Access is denied due to an ACL set on the requested resource.
Internet Information Services (IIS) "

Question by:Trihimbulus
LVL 20

Expert Comment

ID: 17955634
Read the link below for diagnosing the problem


Your last option would be to reset the OWA, but wait for some more suggestions from the experts.


How to reset the default virtual directories that are required to provide Outlook Web Access, Exchange ActiveSync, and Outlook Mobile Access services in Exchange Server 2003 http://support.microsoft.com/kb/883380

Cheers !!
LVL 31

Accepted Solution

LeeDerbyshire earned 2000 total points
ID: 17956143
If OWA worked okay before (i.e. without the redirect), then the permissions on your newly created owahttps.asp file are probably too restrictive.  Try setting the permissions in Explorer so that All Users have Read and Execute rights on it.

Author Comment

ID: 17956759
And THAT is why I have an EE account lol. Thanks guys! Too restrictive - what an oversight on my part!

Featured Post

Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

If there is anything erroneous with Exchange Database, it causes a significant effect on email communication till the user remounts the database. Further, database crash directly affects Outlook users due to which they are unable to access their ema…
Configure external lookups on for external mail flow on Exchange 2013 and Exchange 2016.
This video shows how to quickly and easily deploy an email signature for all users in Office 365 and prevent it from being added to replies and forwards. (the resulting signature is applied on the server level in Exchange Online) The email signat…
Watch the video to know how one can repair corrupt Exchange OST file effortlessly and convert OST emails to MS Outlook PST file format by using Kernel for OST to PST converter tool. It can convert OST to MSG, MBOX, EML to access them. It can migrate…

600 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question