redleader Posted November 26, 2019 Report Share Posted November 26, 2019 My Retrospect Client suddenly refuses to give access to the External Drives It says they are offline ... these drives are not*, the Mac OSX High Sierra system is fine using them for all other activities. Server Was connecting to this client previously [6 days ago] 100% OK and backups from external drives worked fine.Only now Retrospect Client? refuses to allow access now and reports them offline. They are not* ☹ OSX High Sierra Retrospect Client OSX Catalina Retrospect Server Latest version of Retrospect 16.5.x Quote Link to comment Share on other sites More sharing options...
redleader Posted November 26, 2019 Author Report Share Posted November 26, 2019 Quote Link to comment Share on other sites More sharing options...
DavidHertzberg Posted November 26, 2019 Report Share Posted November 26, 2019 redleader, This Forum is a sub-Forum of Windows Products—Retrospect. Why are you posting here about a problem with what is obviously Retrospect Mac? Quote Link to comment Share on other sites More sharing options...
redleader Posted November 26, 2019 Author Report Share Posted November 26, 2019 delete it then. Quote Link to comment Share on other sites More sharing options...
Mayoff Posted December 9, 2019 Report Share Posted December 9, 2019 If Retrospect is having trouble seeing Macintosh Client volumes, make sure you are running the 16.6 version and not 16.5.1. Quote Link to comment Share on other sites More sharing options...
DavidHertzberg Posted December 16, 2019 Report Share Posted December 16, 2019 On 12/9/2019 at 10:11 AM, Mayoff said: If Retrospect is having trouble seeing Macintosh Client volumes, make sure you are running the 16.6 version and not 16.5.1. The explanation for the head of Retrospect Tech Support's comment, which turns out to not be applicable to the OP's problem, is in the P.P.S. of this post in the corresponding Mac 9+ Forum thread which the OP subsequently created. A subsequent post in that thread shows that the OP solved his/her problem, which appears to have been caused by administrator error—possibly resulting from confusion shown by the misleading use of the red-markup terms "Server" and "Client" in the OP's screenshots—which I attempted to explain in a later post in that thread. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.