You might consider elaborating further - self-evidently a remote process has stopped responding when a connection (of some sort) cannot be established with it aka it's stopped responding.
For example, try identifying...
- The protocol &/or port over which you're attempting communication
- The OS at both ends of the connection
- Whether the (behaviour of the) remote process is modifiable (in any way)
- What you've tried thus far - in an attempt to reduce effort by eliminating repetition (of solutions you may have already tried)
A user level that continues to overstate my experience :-))