I am working on a test installation of DotNetNuke Community Edition running on a 64bit Windows 7 box with IIS Express and SQL Express Server 2008 through WebMatrix. DNN's version is 6.01.02(98) and it is using .NET 3.5.
Occasionally, as I look through the default test site, try to enter edit mode, access the admin or host pages it will stop loading and leave me with a white screen. Checking the page in Firebug on Firefox or Chrome shows me that module.css, skin.css, or another seemingly static file is failing to load.
If I let the connection time out on these files, and refresh the page, everything will load fine and I will be able to continue on my way. If I try to refresh the page without letting the css connection time out, the wait seems to be indefinite.
I have not touched the site's css and as far as I can tell, that is the only thing keeping pages from being accessible: manually terminating the downloads gives me a usable but ugly page.
The problem seems to be tied to the CMS, IIS Express can serve up ordinary C# and VB pages fine.
Does anyone know why this would happen, or what I can do so I can start experimenting with DotNetNuke?