Windows TCP connection - Still alive after process terminate

Posted by Kartlee on Stack Overflow See other posts from Stack Overflow or by Kartlee
Published on 2010-04-14T08:50:50Z Indexed on 2010/04/14 8:53 UTC
Read the original article Hit count: 381

Filed under:
|
|
|

Hi People,

I run a license server in linux and a process in Windows to check out tokens from it. It does a tcp socket connection to server to communicate and once the process in Windows is closed, the tokens are checked in back to server. But I see sometime the connection show as established in netstat output even when process in Windows is terminated. This happens when the process in Windows is running for a long time and terminate. It takes 2-3 hours for the connection to go away in neststat output.

TCP BABDT350:4505 180.190.40.34:51847 ESTABLISHED 2832 [app.EXE]

Can you guys tell me is this is a network stack configuration issue in Windows? Is it possible for the connection to go away once process terminate? Please let me know your answers to this.

© Stack Overflow or respective owner

Related posts about Windows

Related posts about tcp