Server Times Out, Site Not Served

natcolley · 09-20-2007, 11:34 PM

I have an IIS 6.0 server on x.x.x.1 which times out without producing my site. I have an Apache server on x.x.x.2 which runs fine. I have the rest of my home network behind a Firebox hardware firewall appliance on x.x.x.3.

In addition to the time out problem, when I try accessing the IIS website from inside my network it keeps coming to the log in for my hardware firewall which the affected webserver isn’t even connected to, although they do share a hub to the modem. I’m thinking this different result from inside vs outside are two different problems, but I can’t figure out either one.

After much searching the net, I found the HTTPERR log and there are a slew of errors there with 400 - hostname. So, thinking maybe I had found something, I changed the host header on the default website to specify the subdomain. This server only handles the subdomain, the domain itself is on the Apache server. But that change did not work so I came here hoping for insight.

There is a connection idle message in the error log when referencing 443, but the connection timeout is set to 120 seconds and the keep alives is checked, so what else am I supposed to do?

thx.

09-20-2007, 11:34 PM	#1 (permalink)
natcolley Registered User Join Date: Sep 2007 Posts: 7 OS: XP Pro	Server Times Out, Site Not Served I have an IIS 6.0 server on x.x.x.1 which times out without producing my site. I have an Apache server on x.x.x.2 which runs fine. I have the rest of my home network behind a Firebox hardware firewall appliance on x.x.x.3. In addition to the time out problem, when I try accessing the IIS website from inside my network it keeps coming to the log in for my hardware firewall which the affected webserver isn’t even connected to, although they do share a hub to the modem. I’m thinking this different result from inside vs outside are two different problems, but I can’t figure out either one. After much searching the net, I found the HTTPERR log and there are a slew of errors there with 400 - hostname. So, thinking maybe I had found something, I changed the host header on the default website to specify the subdomain. This server only handles the subdomain, the domain itself is on the Apache server. But that change did not work so I came here hoping for insight. There is a connection idle message in the error log when referencing 443, but the connection timeout is set to 120 seconds and the keep alives is checked, so what else am I supposed to do? thx.