Home / server / Questions / 180697
Accepted
joshperry
Asked: 2010-09-14 11:44:48 +0800 CST

IIS6 403.1 when Application is Accessed via a CNAME

  • 772

We have a server named slc-app-01 and an ASP.NET application in the default website configured as printflow. I set up a CNAME in DNS for printflow to point at slc-app-01 so the application could be accessed via http://printflow/printflow.

The problem is that when the application is accessed via http://printflow/printflow it returns:

403.1 Forbidden: Execute access is denied.

But when accessed via http://slc-app-01/printflow it works fine.

This has worked fine for over a year. The only thing I can think that we recently changed was installing .NET 4.0 and registering ASP.NET 4.0 with IIS. The application however is still configured for .NET 2.0 and we created a separate AppPool for the 4.0 application.

Thanks for any help.

iis-6 http-status-code-403

3 Answers

  1. Have you added "printflow" to the Host Headers for the website in IIS?

    • 2

  2. You could check the following things:

    1. Is there a web proxy involved when you try to access the server? Do you need to configure it for that host header?
    2. What happens when you do a nslookup printflow? Does it resolve to the right IP address?
    3. Did you check the http bindings of the website? Does it accept the "printflow" http host header?
    • 0
  3. Best Answer

    Turned out to be a HOST Header problem after-all. Someone had configured a site with printflow as a hostheader and it was co-opting all of the requests. Since this rogue site was configured with "None" for "Execute Permissions" it was throwing a 403.1 instead of a 404 for "*.aspx, asmx, etc..." even though the site was void of any files.

    • -1