I have an application using DCOM accross a WAN to access data at 10 sites, from time to time lines in the WAN go down or the remote server is rebooted.

When this happens my application waits for ages and then comes up with Remote process is busy - Retry, and then eventually with RPC server not available. I want to avoid this as it takes ages and resultes in an error which my on error routines don't seem to catch.

Want I want is a simple method to "ping" and prove the link is up (ideally Windows API calls rather than an OCX), and then some way to verify the RPC server.

Anyone have any ideas?


Gary.