I have - or had - a DNN install running on a Win2k3 SBS server w/ IIS 6 that I was unaware of until just this afternoon. I inherrited this system's administration tasks from a guy who left several months ago; there was no documentation left as to its functionings. The only thing I was aware of running on this system was WSUS, which I've since removed.
I've since learned that they share the same database server. I removed the WSUS database, but the DNN database is still there.
HOWEVER.
It would appear that the IIS configuration was purged or somehow manipulated by the WSUS 2.0 removal process, or the update to w2k3 SBS SP2 I ran about two weeks ago. The DNN install is unfunctional, and there is no apparent configuration. I restored the config from 11/20, which appears to have a site entry for DNN; however, when I attempt to acess the site (domain pointer to the host, site set up to listen for it) I'm getting a 404. The site is set up to point to the root of the DNN directory. 404/file not found is received when trying to access localhost or any of the hostnames; this happens while attempting to access teh site over the intranet, from the actual host, as well as from within IIS Manager when I right click on a file and go to "Browse".
ASP.NET 2.x and Active Server Pages are both allowed extensions, as is BITS server extension.
Can anyone help a guy out? What might be the cause of this problem, and what might I do to go abotu fixing it?
Any help is most certainly appreciated!