I tried to deploy an ASP.NET application in IIS6. I created a virtual directory MyApp, mapped it to a folder on the hard drive, copied all the stuff from my application to that folder.

Now when I request http://host/MyApp/ I get HTTP 403 and that request is logged in the IIS log. When I request http://host/MyApp/default.aspc (there's no such file) I get HTTP 404 and that request is also logged.

But when I request http://host/MyApp/default.aspx (that file is present in the folder which the virtual directory is mapped to) Internet Explorer just says it "cannot display the web page", that request is not logged. When I trace requests with Fiddler it shows empty reply and HTTP code 0 on the client side. .aspx extension is of course mapped onto ASP.NET ISAPI extension.

ASP.NET 2.0 is installed into IIS. When I run aspnet_regiis -lk it produces the following output:

Yes, mapping is done at both site and directory levels, ASP.NET 2.0 is installed into IIS (aspnet_regiis -i). The folder is an application (gear icon).
–
sharptoothMar 31 '11 at 7:33

@sharptooth - what happens if you drop a simple .aspx page into the DefaultWebsite? Does that run? Are there any other ASP.NET sites on the machine?
–
KevMar 31 '11 at 8:21

There're two "web sites" on that machine and two other "applications" in the same "web site" Which exactly do I copy into "default website"? If I just copy the default.aspx file into the folder where "default website" is mapped the misbehavior is the same.
–
sharptoothMar 31 '11 at 8:36

@sharptooth - ok....so does ASP.NET work at all on the server?
–
KevMar 31 '11 at 8:38

I'd rather say it doesn't - I can't make any page that should normally trigger ASP.NET open.
–
sharptoothMar 31 '11 at 8:42

Although Google searches show that the typical reason is ASP.NET being misconfigured in my specific case the reason was Windows Sharepoint Services 3, installed onto the same machine. Once it has been installed, ASP.NET applications seem to no longer work. Reinstalling .NET and IIS doesn't help.