After installing and configuring CruiseControl.NET on my Windows XP development station I was getting a File not Found (HTTP 404) error when trying to see the details of a given build, i.e. selecting Latest Build from the main menu.

Since these URLs don't point to a file in specific but to a "fake" location that is in place handled by CruiseControl.NET I wasn't sure if there was something wrong with the directories I was using on my project's configuration.

Luckily for me I checked the IIS logs and noticed that UrlScan was the one blocking the calls and returning the HTTP 404 error because the URLs contained dots as part of the path, for example:
http://localhost/ccnet/server/local/project/testproject/build/log20090629092945Lbuild.1.xml/ViewBuildReport.aspx

After setting "AllowDotInPath=1" and saving urlscan.ini, I was able to get the build details. Restarting IIS was not required.

The UrlScan configuration file is usually located at the following location:
%windir%\system32\inetsrv\urlscan\urlscan.ini