Web Site Wont work (HTTP 403)

"This error (HTTP 403 Forbidden) means that Internet Explorer was able to connect to the website, but it does not have permission to view the webpage."

Asp.net 4.0.

I created a new web site and it if giving error above.  It is exactly like another site that works.  I even tried pointing it at the same directory (web.config, files, etc).  Still doesn't work.

The site will serve htm files, but not aspx files.

The only thing I see different is the handler mappings (in the IIS console).  On the site that works, most are enabled.  On the one that doesn't, most are disabled, including *.aspx.  I don't see how to enable them.  Not sure if this is problem or not.

All permissions are the same.  IIS_USER has full read/write access.

Help!  Urgent!
No1CoderAsked:
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.

Paul JacksonSoftware EngineerCommented:
If you are using Internet Information Services 7.0, after installing ASP.NET you might need to enable ASP.NET in the Internet Information Services (IIS) management console. IIS 7.0 introduces a new security lockdown console, which allows an administrator to selectively enable and disable functionality in IIS. When ASP.NET 4.0 is installed on a computer that uses IIS 7.0, the installation script creates a metabase key for that version of ASP.NET. This metabase key allows ASP.NET to appear in the console as a configurable component. A separate key is created for each installed version of ASP.NET, allowing each version to be separately configurable in the console.

To enable the Web service extension for ASP.NET 4.0


1.Click Start, click Control Panel, click System Security, click Administrative Tools, and then click Internet Information Services (IIS) Manager.


2.If you need to connect to a remote IIS Server, right click the Internet Information Services node and click the Connect... option.


3.Type in the computer name for the remote IIS Server and credentials if necessary.


4.Click the Web Service Extensions folder. The security lockdown console appears in the frame on the right.


5.In the Web Service Extensions window, right-click the ASP.NET v4.X.XXXX, and then click Allow.

http://msdn.microsoft.com/en-us/library/aa560277.aspx
No1CoderAuthor Commented:
I am using IIS7 on W2008.  These instruction to not match my system.

I can get into IIS console.  When I expand the sites, there is no Web Service Extension folder.  Also, my sites do not have virtual directories or applications.  

I was able to take an existing site that works (which has handler mappings enabled), and point at my new web site directory.  If I change the bindings, I can make it work.  There is nothing wrong with my site or web.config, it is the site config is IIS that is bad.

I still don't see how to update the handler mappings.  Also don't understand how to enable the web service extensions, and mentioned in this article.  The instructions don't seem to apply to W2008, IIS7.

I tried connecting to the server from a w2012R2 box.  When I connect, I get a strange dialog (attached).  I installed these.  I still don't see the Web Service Extensions folder on w2012R2 console either.  Still doesn't work.
Capture.JPG
Member_2_2459312Commented:
Check your app pool for your new site.  You need to set the framework to 4.0, normally it defaults to 2.0
Learn Ruby Fundamentals

This course will introduce you to Ruby, as well as teach you about classes, methods, variables, data structures, loops, enumerable methods, and finishing touches.

No1CoderAuthor Commented:
The app pool is set to 4.0 (classic)
No1CoderAuthor Commented:
I am pretty sure it is the handler mapping thing.  How to I enable it?
No1CoderAuthor Commented:
Was able to fix by enabling  read and script permissions on the isappy-dll.  I don't know what turned this off on my server, but enabling fixed.

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
No1CoderAuthor Commented:
fixed problem
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 Development

From novice to tech pro — start learning today.