I'm in a bit of a situation and hope someone in the community can help me out.

I just came back from a short vacation to find that a junior admin at my work had re-installed IIS on the webserver I have been using for my DNN implementation.  So, now our Intranet (DDN site) is broken.  I didn't think it would be so bad b/c I have backups and took notes on all the settings.  But, so far, I can't get it working.  Would a re-install of IIS break some kind of connection w/ SQL or something else I'm missing? 

Here are my settings and info:

IIS Default Web Site Properties/settings

IP address: 192.168.1.40
Home Directory: a dir. on this computer: C:\Inetpub\wwwroot\"DNN site folder"
App. Name: default app
Starting point: <default web site>
execute: scripts only
App pool: ASP.NET V2.0
Documents: default.aspx (at the top)
Directory security: enable anonymous access - IUSR_"SeverName"
ASP.NET version : 2.0.50727
   Virtual path: default
   File location: C:\Inetpub\wwwroot\"DNN site folder"\web.config

Other Info:

DNN v4.3.4, IIS V6.0, SQL Express

As far as I can tell, I have set up the website under IIS just as it was before.  Do I need to re-install DNN?

Thanks for the help,  mike

If the installation directory is c:\Inetpub\wwwroot\"DNN site" , then yes, NETWORK SERVICE has full permissions to that folder. 

Right now I'm getting a "page cannot be found"  when trying to browse to it from the server itself or another network computer, w/ either IP or name.

from the install guide:

"The required permissions for the various directories in DotNetNuke are as follows:
  Root (and all child folders) – Read Access  
  Root – Write Access (and Modify Access if expecting to create child
portals)
  DesktopModules – Write, Modify Access (if installing 3rd party Private
Assemblies)
  Portals (and all child folders) – Write, Modify Access (to allow File Manager access and Skin/Container access) "

is all that setup correctly?