I have IIS 6 installed on a Windows Server 2003 SP3 machine (x86). When I try to open a .aspx page (either locally on the server or remotely) I get a message stating "Internet Explorer Cannot Display The Webpage".
Nothing is entered in the W3SVC1 log files but the following is added to the HTTPERR log...
2013-04-11 20:01:51 10.129.1.49 58716 10.5.190.144 80 HTTP/1.1 GET /aspnetcheck.aspx - 1 Connection_Dropped DefaultAppPool
...when I try the WFetch app (localhost, server name, FQDN with any AUTH type) from the IIS Resources set of tools, I get following...
0x2746 (An existing connection was forcibly closed by the remote host.): Socket Error On Receive
.Net 2.0 SP2, .Net 3.0 SP2, .Net 3.5 SP1 and .Net 4 Client Profile and Extended are installed on the server. I have used aspnet_regiis to re-install .Net with no luck. I have uninstalled all versions of .Net and reinstalled them and even uninstalled IIS and re-registered .Net with no luck.
Nothing shows up in Event Logs. I initially thought it was an authentication issue as I had the Virtual Directory set to Integrated Windows Authentication and have since disabled that and have it set to Anonymous. I also forced NTLM under the NTAuthenticationProviders (as that has fixed this in past as it started out where IE would prompt for the credentials 3 times and then fail to display the page).
Debug Diagnostics when set to monitor for Crashes doesn't catch anything. Symantec AntiVirus v 10.0.2.2011 is installed but has been disabled. Running netstat -ano from a command line shows port 80 listening on local address 0.0.0.0:80 for the System process.
If I point to a .html, .gif or .jpeg file in IE, that item WILL display. I try to bring up .aspx, no dice. The reply of Socket Error On Receive should point me to the issue, but I cannot figure a way to show what is blocking these requests.
When I run Process Monitor, I can see the request for the .html, .gif and other requests (other than .aspx). Nothing is displayed in Process Monitor when I try to browse to a .aspx file. Bing, Google, Yahoo have all yielded little to nothing on this.
What have I missed?