That's all very well, graff, but it can only identify the situation whereby the remote server process has stopped running.

I'm guessing, since the OP hasn't (yet) responded to a couple of requests for further information, that the OP has encountered the situation whereby the process appears to be running but is no longer responding to connection requests...hence either the heartbeat or polled approach (as mentioned elsewhere) would be the logical solution.