I try to search for this problem, and could not find an answer.  I am not sure what I have done wrong with the installation.  I am using windows XP IIS locally to develop the site (content and custom pages as a intranet).  When I try http://computername it comes up with the "We're sorry but we could not find the page you are looking for. Please try the Site Map".  When I put in http://computername/default.aspx I am able to see the page and every other page (except for when I click on home on the sitemap - home.aspx or the home link on the top of the page).  Also when I go to site settings and do a Preview/Browse on a skin it also shows the "We're sorry but we could not find the page you are looking for. Please try the Site Map" page. (On a side note, when I do select a skin and click preview it always starts on number 1 instead of the one I have selected).  IIS is setup with default document of "Default.aspx" on top of the list.

Any ideas on how to fix this?  Thanks in advance for any help.

mojoPortal Version: 2.3.5.8 MSSQL
Operating System: Microsoft Windows NT 5.1.2600 Service Pack 3
ASP.NET Info: v4.0.30319 Running in Full Trust

Joe,

Thank you for your reply and time. I think I may have narrowed the problem down, but not sure how to fix it. Something with my IIS settings.  When I use visual studio web developer 2010 express to view the web page it loads just fine with http://localhost:1602/wwwroot/. I created a page called new-page.aspx, but when I go to http://localhost/new-page.aspx, I get a HTTP 404.  Same thing with home.aspx.  I can go to default.aspx (that file exists).  I double checked my site properites, and enable default document is checked and "Default.aspx" is on top. The reason I am using my local IIS is for getting feedback during development before it goes live. 

Thank you again.

Jonathan

Just thought of one other thing like this that someone reported a while back using Win 2003/IIS 6, they had a misconfiguration in the handler mapping .aspx extension for ASP.NET where the "Verify that file Exists" was checked so if the file does not exist on disk IIS returns a 404 without handing the request to ASP.NET.

These screen shots are what they guy sent me showing the box he had to uncheck

The reason is pages you create don't really exist on disk, they are all served by  /Default.aspx?pageid=x but through the magic of url re-writing we have friendly urls. Those friendly urls do not correspond to files on disk so IIS needs to just let ASP.NET handle the reuest and ASP.NET can return a 404 if it can't handle the request.

Hope it helps,

Joe

Your solution worked.  Thanks again.