Take the 2-minute tour ×

We have a Main application named "Trevor" installed in 2008R2 machine named "TEAMER12" which is slow now. One more application named "TVS" also running in and found there were many connections per second occurring to port 5009. netstat tool mentions that some fast connection open/close seen for port 5009 So first it will be listening mode like shown below

After that iwill become TIME_WAIT and i could see several entries like shown below


TCP        TEAMER12:microsoft-ds  ESTABLISHED

again it will go several entries like TIME_WAIT TCP TEAMER12:5009 TIME_WAIT

Can any body tell me whats the reason behind why many connections per second occurring to port 5009 and why application slow?

share|improve this question
What do you mean by "many connections per second"? That question seems to have come out of nowhere. Did you do a netstat twice a few seconds apart and see many connections in the second that weren't in the first? (As the output says, is the LISTENING socket.) –  David Schwartz Mar 19 '12 at 17:28
@avid Schwartz yes that was the one .Ok but now my question is why this entry " TCP TEAMER12:5009 TIME_WAIT " happening many times(around 100 times) and not establishing connection.Does this makes any issues for establishing connection with port5009 –  michale Mar 19 '12 at 18:47
@avid Schwartz do we need to get rid of this waiting " TCP TEAMER12:5009 TIME_WAIT " by manupulating registry? –  michale Mar 19 '12 at 18:55
No! Why would you want to do something like that?! That's been understood to be a boneheaded thing to do since 1992. –  David Schwartz Mar 19 '12 at 19:10
@David Schwartz These are occurring on, I believe there have been cases where all port numbers are used. So my question is how do you feel my netstat statics i posted nothiong abnormal? –  michale Mar 19 '12 at 19:22
show 6 more comments

1 Answer

All you've shown is that a reasonable number of connections are occurring and then those connections are closing. This may be perfectly normal or it may be abnormal. We don't know because we only know what you're telling us.

But the problem is that something isn't happening. If you can get logs of whatever it is that is supposed to do that something, perhaps they'll suggest why.

For example, the server might be closing the connection immediately. The client might be closing the connection without doing what it's supposed to be doing. The client might be sending the correct command but then the server closes the connection. You'll have to actually troubleshoot.

But all you've figured out so far is that a moderate number of connections are taking place.

share|improve this answer
yep,you may be correct i need to look trace files –  michale Mar 19 '12 at 21:05
add comment

Your Answer


