403 - Forbidden: Access is denied. You do not have permission to view this directory or page using the credentials that you supplied.

#1 - 2008 R2 Server - IIS 7.5   ( not a domain controller )
#2 - DC is server 2003

Accessing a simple hmtl file locally on the 2008 server is OK - page renders
Accessing the same file elsewhere in the lan/domain results in the error...

403 - Forbidden: Access is denied.
You do not have permission to view this directory or page using the credentials that you supplied.

IIS_IUSRS ( 2008server\iis_iusrs ) have full perms to the directory where this html file is located.

This appears to be a network permission issue, but I can't seem to find the right combo in IIS / directory permissions.
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

It is the Firewal"  that blocks the World Wide Web Services port by default (Port 80).

To fix this: goto control panel,  Windows firewall

goto the Exceptions tab and Scroll  down to World Wide Web Services (HTTP).

Click the check box and click OK.

Now your machine is accessible to the outside world.

Click the check box and click OK.
ziivaAuthor Commented:
Ah, sorry, should have provided more details...

Windows firewall is off.

In IIS --> website #1 points to c:\inetpub\wwwroot

In IIS --> website #2 points to c:\inetpub\wwwroot\realcode

 Any file I attempt to open via website #1 generates the 403 error.  So for the same file...

                 website#1\realcode\hello.html generates the access error

                 website#2\hello.html renders OK

The IIS permissions appear to be the same for both sites.
Emmanuel AdebayoGlobal Windows Infrastructure Engineer - ConsultantCommented:

The issue here is related to permission,

What you need to do is to reset the security permission on the folder :\inetpub\wwwroot\realcode . Please ensure that you check , Permission from the parent to propagate to child object.


Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

Create an account on domain (active directory), assign that user as application pool's user for this website. Also provide permission to that user on that share or NAS location.
ziivaAuthor Commented:
A solution...


for some reason had this entry for the website #1...

                <ipSecurity allowUnlisted="false">

I set this to "true" and users are able to access files OK
ziivaAuthor Commented:
This solution might have worked - but found the config file issue.

Without adding the app pool user (  changing only the the config file ) - domain users have access to the site's pages/content.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft IIS Web Server

From novice to tech pro — start learning today.