up vote 1 down vote favorite
1
share [g+] share [fb]

I have a .Net application on my IIS7 server it was working fine until I had to move it to another server.

I moved the exact same code to the new server and I noticed that after some hours the website stopped responding to remote requests but if I did remote desktop to the server it responded to the request done to localhost. If I stop the website and the application pool it started working fine again.

I was able to track the problem to hundreds of requests left in CLOSE_WAIT state to the http port that are never closed (I waited a few hours and they remain the same).

Any ideias?

link|improve this question
Did you ever find a solution? – Shiraz Bhaiji May 23 '11 at 21:13
feedback

1 Answer

up vote 0 down vote

Check out the article may help you understand and troubleshoot the issue. I will also check for NIC driver on the server and update it to the latest.

link|improve this answer
I already looked into the MaxUserPort and TcpTimedWaitDelay settings, but I didn't messed with those on the other server. The TcpTimedWaitDelay default value is 240 seconds but the connection remains in CLOSE_WAIT state for hours instead of been closed after 4min. – rjlopes Nov 11 '10 at 15:10
feedback

Your Answer

 
or
required, but never shown
discard

Not the answer you're looking for? Browse other questions tagged or ask your own question.