Hello Eveyone - I could use some advice on getting my DNN 5.1 site running again.  I have been (trying) to troubleshoot the problem(s) for over two weeks now.  I think that I am too close to the problem sor have been working on the problems so long now that I am no longer seeing things logically and can use some fresh eyes and advice.

The background.........I decided to consolidate my network - I had a Winows 2003 and Windows 2000 server.  I decided to take my old workstation and put W2K3 on it - it was newer hardware and had more disk space and a faster processor.  I got that working and next installed DNN 5.1 in the web root on the updated W2K3 server and triggered the installaion process sucessfully.  I then started to add content................so the new DNN installation was working.  I had to physically log into the website to view it - which was fine since I did not want public access until I got the content and modules configured and I stopped working on the site to correct some DNS and other errors from the server move.  When I went back to the site - I couldn't access it - I was encountering "Cannot Display The Webpage"  HTTP errors...my first thought was maybe I trashed DNS - so I spent several days reading and researching DNS to see if I accidentally deleted some record but (to me) it (DNS) looks fine. I have the A (host) record and CNAME record in place  So I started to think that maybe it was a networking problem - and I still don't see anything.  I can access the server using Remote Desktop

This is what I know - I can ping any server and workstation on the network using server_name or server_IP.  If I try to acess the server using http://server_name or http://server_IP from a workstation, I'm prompted for my username and password - when they are entered, I still encounter the error.  "Cannot Display Webpage" I get the same if I go to the server and enter the server_name or server_IP(prompted for username/password then the error) but if I use http://localhost or http://127.0.0.1 on the server, I get an HTTP error 400 (Bad Request)

I went to the log files and looked at HTTPERR and it showed that there was a 400 error using localhost but the W3SVC logs show a 401.1 error when trying to access from the workstation.  Anyone have any ideas?

Yeah - tried to give as much info as possible - as far as it being an IIS problem - I am working on that being a possibility.  spent the last couple of days going thru the configuration but I don't think that is the problem.  The site WORKED when I originally installed it.  As a matter of fact, I was adding content - My thinking is something in the overall server configuration - since that was what I was working on last when it quit.