Jump to content


  • Content count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About chymb

  • Rank
  1. Sorry Lennart, I had written a longer message but then when it failed to post I didn't go into the same detail. I run it on the Windows server and set up a filter for port 497: Options -> Advanced Filters -> "include:remote:tcp:497" It then lists just the retrospect connections and when a machine has disappeared without disconnecting I highlight it and hit the X to disconnect it. It doesn't happen often, but it saves me having to restart the machine without closing Retrospect nicely.
  2. I use a utility named CurrPorts to sever the connection to the client. http://www.nirsoft.net/utils/cports.html
  3. I am seeing the same thing, although I have a public key so the client starts OK but isn't recognised as the same client by the server. If you take a backup of the state file, you can restore it and it seems to carry on like nothing happened, but it's possible that something is out-of-date. In my case it is most often the same clients (, but there are a lot of them, and I believe that it's been happening since we were on 6.3 clients, though I only suspected that the file was being truncated – this is the first time I've seen it. On a related note. you can set the password using: retroclient -setpass without the need for the installer.