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

Meet "S" and "P" two server side apps connected via some TCP socket, both running on Windows 2008.
In fact, S connects to P using port 20202

At some point over the week end, P is killed without notice, which S finds with a connection reset.
S enters a connection retry loop for about 20seconds, then can connect back to port 20202 for about 1 second, then the connection gets dropped with proper TCP termination.

Hence my question : Is Windows 2008 capable of sending TCP termination after P has been killed? Or I am looking for a zombie?

share|improve this question

closed as not a real question by John Gardeniers, Greg Askew, Tom O'Connor, Khaled, Alex Jan 28 '13 at 13:47

It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center.If this question can be reworded to fit the rules in the help center, please edit the question.

By "TCP termination" do you mean resetting the TCP connection? Or do you mean an orderly shutdown? – David Schwartz Jan 28 '13 at 9:51

It's not Window sending the packet but the application. And yes, of course it can send the packet. I'd only be concerned if it got a reply from P, which is not running.

share|improve this answer