We had an a Asp.Net 2 website setup for a client of ours some years ago which was working fine until a couple of days ago.
Here are the details:
- Windows 2003 Sp1
- 1 GB RAM
- IIS 6.0
Suddently, IIS stopped serving any HTTP requests (including HTML files) even though FTP is working fine. Running a ping also returns a proper IP.
Stuff that I have tried:
- Recycling the App Pool.
- Restarting IIS
- Uninstalling / Reinstalling IIS
- Trying to setup a simple Hello World, single page HTML website
But none of this works. I keep getting the following message (in FF) while trying to access the site:
The connection to the server was reset while the page was loading. The site could be temporarily unavailable or too busy. Try again in a few moments. If you are unable to load any pages, check your computer's network connection. If your computer or network is protected by a firewall or proxy, make sure that Firefox is permitted to access the Web.
All the bindings are correct and point to the IP. Has this happened to anyone before and could anyone help me out here?
I forgot to mention these points earlier. - Rebooting the server has no effect on this. I have tried this multiple times. - There are no IIS logs from 21st April 2011. From when the site has been down. Even event logs for 21st / 22nd don't show anything out of the ordinary.
EDIT 2 I got this tool from the IIS Debug Toolkit called WFetch and ran it for localhost which had the default IIS website with a Hello page. Following is the response:
started.... WWWConnect::Connect("localhost","80")\n IP = "127.0.0.1:80"\n source port: 1085\r\n WWWConnect::Close("localhost","80")\n closed source port: 1085\r\n cannot send data, because connection is closed finished.
EDIT 3 After almost 10 days of hell, IIS just started working automatically. Just like that. I had reinstalled it - but was getting the same issue even after reinstalling. However, we had given up all hope and started migrating to a new server when after 2 days of installing the damn thing started serving up pages again. Very weird and I have no idea what was going on.
Thanks to everyone for all their suggestions - they were of great learning and helpful in figuring out how to go about debugging IIS. Really appreciate it.