Graphics80
Level 1 (0 points)

Q: Unable to locate network home folder

When I try and log into my Mac mini server from a clint computer I get the error message Can't locate home folder. This just started happening and I've reinstalled the OS on client computer with the same result, I'm able to log in on any of my other networked computer just fine. I even made sure the network settings on the computer getting the error message is the same as a client computer that functions properly. Can anyone help to solve this issue?

Posted on Aug 17, 2014 8:29 PM

Close
Graphics80

Q: Unable to locate network home folder

  • All replies
  • Helpful answers

  • by Linc Davis,

    Linc Davis Linc Davis Aug 17, 2014 9:28 PM in response to Graphics80
    Level 10 (207,995 points)
    Applications
    Aug 17, 2014 9:28 PM in response to Graphics80

    Log out on the other client and try again.

  • by Graphics80,

    Graphics80 Graphics80 Aug 18, 2014 6:35 AM in response to Linc Davis
    Level 1 (0 points)
    Aug 18, 2014 6:35 AM in response to Linc Davis

    Same result, still not able to locate home folder.

  • by Linc Davis,

    Linc Davis Linc Davis Aug 18, 2014 7:05 AM in response to Graphics80
    Level 10 (207,995 points)
    Applications
    Aug 18, 2014 7:05 AM in response to Graphics80

    Many Open Directory problems can be resolved by taking the following steps. Test after each one, and back up all data before making any changes.

    1. The OD master must have a static IP address on the local network, not a dynamic address.

    2. You must have a working DNS service, and the server's hostname must match its fully-qualified domain name. To confirm, select the server by name in the sidebar of the Server application window, then select the Overview tab. Click the Edit button on the Host Name line. On the Accessing your Server sheet, Domain Name should be selected. Change the Host Name, if necessary. The server must have at least a three-level name (e.g. "server.yourdomain.com"), and the name must not be in the ".local" top-level domain, which is reserved for Bonjour.

    3. The primary DNS server used by the server must be 127.0.0.1 (that is, itself) unless you're using another server for internal DNS. The only DNS server set on the clients should be the internal one, which they should get from DHCP if applicable.

    4. Follow these instructions to rebuild the Kerberos configuration on the master.

    5. If you use authenticated binding, check the validity of the master's certificate. The common name must match the hostname and domain name. Deselecting and then reselecting the certificate in Server.app has been reported to have an effect in some cases. Otherwise delete all certificates and create new ones.

    6. Unbind and then rebind the clients in the Users & Groups preference pane. Use the fully-qualified domain name of the master.

    7. Reboot the master and the clients.

    8. Don't log in to the server with a network user's account.

    9. Disable any internal firewalls in use.

    10. As a last resort, export all OD users. In the Open Directory pane of Server, delete the OD server. Then recreate it and import the users. Ensure that the UID's are in the 1001+ range.

  • by Graphics80,

    Graphics80 Graphics80 Aug 18, 2014 1:34 PM in response to Linc Davis
    Level 1 (0 points)
    Aug 18, 2014 1:34 PM in response to Linc Davis

    Thank you for the help, but this still didn't resolve the issue on this one client computer.

  • by Linc Davis,

    Linc Davis Linc Davis Aug 18, 2014 4:42 PM in response to Graphics80
    Level 10 (207,995 points)
    Applications
    Aug 18, 2014 4:42 PM in response to Graphics80

    You've taken all 10 of those steps? If so, what's in the logs?