1
I added the IIS role to my Windows 2003 server for a client that is running ASP. They have a default.aspx
page in the site they sent me. I added a site and gave it a path of C:\Inetpub\wwwroot\_client_site
When I try to browse to it at http://my_public_ip/_client_site
I am getting the error This page cannot be found.
I went into the site properties and made sure that default.aspx
was the first entry for default content pages. Anonymous access is turned on and Read/Write/Directory Browsing are checked off. I also checked the folder on the file system to make surethat
IUSR_Client` has read/write/list folder permissions.
What things can I look for to fix this?
@Wil - When I do the simple HTML page, and hit the IP it asks me to log-in. I set anonymous access I thought and I know the wwwroot folder allows IUSR-Client to read and list contents. – None – 2009-10-20T00:08:42.193
@Will - ok, I turned off all other sites, just enabled the default website, created a page in wwwroot called default.htm and hit my IP and I get a directory listing now vs the page being served. – None – 2009-10-20T00:16:14.473
@Will - OK works now after IIS restart. I get the default.htm page. When I try to hit http://my.ip/_client_site I get an error 'you are not authorized to view this page'
– None – 2009-10-20T00:19:52.520ok, what you need to do is go to the default documents section and simply add the file to it or rename it, I am always getting it wrong off the top of my head, it is usually a combination of - default / index then .htm or .html, anyway, this is good that it is all working. The page cannot be displayed on asp.net applications is usually for security, when you have confirmed that the site is actually working, you need to enable remote debugging so you can see the errors and what is going on. – William Hilsum – 2009-10-20T00:20:46.357
you posted your last one before I did my last comment... Anyway, it sounds to me like a bog standard permission issue. Go to the folder holding _client_site and manually reapply the permissions and/or set inheritance. They can get lost if moving the folder from another machine. Next, through IIS itself, go to directory view and just double check the permissions there. – William Hilsum – 2009-10-20T00:22:51.083
@will - re-applying the permissions worked, it did then serve an index.html page. When I remove the index.html page and try to get to serve default.aspx I get a page cannot be found. Although it is there. default.aspx is listed as the first file to be served. – None – 2009-10-20T00:32:32.980
ok, this is a bit more complicated - sometimes weird things can happen with the default / first application. Now we know the server exists and can serve, I would stop this site and create a new one. Make sure ASP.net is installed (it is seporate to IIS) andthat it is enabled and the site has execution/application permissions which is different from serving static content. – William Hilsum – 2009-10-20T01:25:35.877