Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I've been having a problem with my WS2008R2 server ever since I started IIS7 for the first time. I've been managing to work around it so far, because https access works normally. http, however, has never worked right. The server simply seems to randomly drop packets via http.

I've tried multiple ports and http servers, but all of them exhibit exact same behaviour. The connection takes extremely long and usually times out.

This hold true only for external network (the server acts as a NAT router with two network cards), however, trying to access from internal network works normally. Even attempting to access it from within the network via external IP will yield no result.

I'm guessing it has to do with NAT (although all the ports are correctly routed and this only happens with http), as the packets don't even reach :8000 if I listen to the interface with Wireshark.

Follows the Wireshark capture of the traffic, as seen from the internal network card when trying to access the resource through external IP: TCPFail

Wireshark capture of the successful access, if using the internal IP: TCPSuccess

Duly note how both of those links need to use https to function. To reproduce the problem, feel free to try to access them via http.

share|improve this question
A few things off the top of my head... Can you telnet to port 80 from various remote boxes? Are you sure DNS is configured correctly? Assuming that your server is dual homed, are you sure the routing is configured correctly? – Techie Joe Jul 19 '13 at 23:09
Everything else works, this server has been operational for months now. DNS resolves for everything, all other protocols are routed correctly. Telnet doesn't work, for internal or external IPs, for HTTP servers on any port. – Naltharial Jul 20 '13 at 11:53

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.