I've got a problem on a Windows Terminal Server (2003 R2): after having launched a particular application and disconnected from TSE, the session is left on the server with the 'Down' state.
I'm not able to kill that session and the only process remaining is csrss.exe (which I can't kill).
The application is the Cygwin X server. I don't know what is done by the application to trigger that problem.
What can cause a 'Down' state? How to investigate why a session is left in this state? What tools would you recommend? I have seen nothing related in the event viewer.