johnmci

Q: TimeMachine. Error while confirming network destination: Error Domain=NSOSStatusErrorDomain Code=89

Trying to setup a mac OS X server Time Machine Service (Server is 5.1.5 (15s7047)

We setup the Time Machine panel, set a disk location, etc, turn on.

 

This works fine, but on one client mac, when we try to pick the server it gives us

"Connecting to "x"...

There was a problem connecting to the server "X".

Check the server name or IP address, and then try again, if you continue to have problems contact your system administrator.   (OK)

 

In the console log we get

com.apple.prefs.backup.remoteservice[547]: Error while confirming network destination: Error Domain=NSOSStatusErrorDomain Code=89 "dsMDEFNotFound / ECANCELED: could not load MDEF / Operation canceled"

Posted on Jul 5, 2016 1:21 AM

Close

Q: TimeMachine. Error while confirming network destination: Error Domain=NSOSStatusErrorDomain Code=89

  • All replies
  • Helpful answers

  • by Linc Davis,

    Linc Davis Linc Davis Jul 5, 2016 5:59 AM in response to johnmci
    Level 10 (207,926 points)
    Applications
    Jul 5, 2016 5:59 AM in response to johnmci

    What version of OS X is that client running?

  • by johnmci,

    johnmci johnmci Jul 5, 2016 10:42 AM in response to Linc Davis
    Level 1 (8 points)
    Servers Enterprise
    Jul 5, 2016 10:42 AM in response to Linc Davis

    10.11.5 (15F34)

  • by Linc Davis,

    Linc Davis Linc Davis Jul 5, 2016 11:09 AM in response to johnmci
    Level 10 (207,926 points)
    Applications
    Jul 5, 2016 11:09 AM in response to johnmci

    Please read this whole message before doing anything.

    This procedure is a diagnostic test. It’s unlikely to solve your problem. Don’t be disappointed when you find that nothing has changed after you complete it.

    The purpose of the test is to determine whether the problem is caused by third-party software that loads automatically at startup or login, by a peripheral device, by a font conflict, or by corruption of the file system or of certain system caches.

    Disconnect all wired peripherals except those needed for the test, and remove all aftermarket expansion cards, if applicable. Start up in safe mode and log in to the account with the problem.

    Note: If FileVault is enabled in OS X 10.9 or earlier, or if a firmware password is set, or if the startup volume is a software RAID, you can’t do this. Ask for further instructions.

    Safe mode is much slower to start up and run than normal, with limited graphics performance, and some things won’t work at all, including sound output and Wi-Fi on certain models. The next normal startup may also be somewhat slow.

    The login screen appears even if you usually login automatically. You must know your login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.

    Test while in safe mode. Same problem?

    After testing, restart as usual (not in safe mode) and verify that you still have the problem. Post the results of the test.

  • by johnmci,

    johnmci johnmci Jul 11, 2016 10:39 AM in response to Linc Davis
    Level 1 (8 points)
    Servers Enterprise
    Jul 11, 2016 10:39 AM in response to Linc Davis

    Some further fiddling and use of tmutil from the command line showed that the Server would not accept AFP connections. We rebooted the server machine and the problem went away. Note on the server we did turn Time Machine off/on but that did not fix the problem. The client machine was the last one we tried to connect, so we can only assume some service on the server failed preventing us from configuring this last client.