roberting
Level 1 (0 points)

Q: Mavericks Server sync trouble with mobile account

Hi all,

 

I have a Mac mini home server with mavericks server 3. I have managed so far to set up a home network.

I have a local network user installed on the server and set it up as a mobile account. When I log in to that account from a MacBook within the network. it asked me if I would set up a mobile account. However, my data from the server is not there - it's a blank new user (Although I set up the network user from an existing account with documents and stuff).

 

When trying to sync manually via the menu, a progress bar appears briefly, the I get an error message saying something like "Sync could not be finished because your network user folder in ("null") does not allow write access. please try again later or ask your system administrator" (my OSX is in german, so this is not literal).

 

What can i do about this? Thanks for your help

Mac mini, OS X Mavericks (10.9.4), Server

Posted on Aug 3, 2014 12:59 PM

Close
roberting

Q: Mavericks Server sync trouble with mobile account

  • All replies
  • Helpful answers

  • by Linc Davis,

    Linc Davis Linc Davis Aug 3, 2014 2:27 PM in response to roberting
    Level 10 (207,995 points)
    Applications
    Aug 3, 2014 2:27 PM in response to roberting

    In the sidebar of the Server.app window, select the icon at the top with the name of the server. Then select the Storage tab in the main window pane.

    Navigate to the folder in question and select it. From the popup menu at the bottom with a gear icon, select

              Edit Permissions...

    Verify that the permissions are what they should be, and make changes if necessary. Then, from the same menu, select

              Propagate Permissions...

    Check all applicable boxes, including Access Control List. If in doubt, check all boxes. Click OK.

  • by roberting,

    roberting roberting Aug 4, 2014 10:36 AM in response to Linc Davis
    Level 1 (0 points)
    Aug 4, 2014 10:36 AM in response to Linc Davis

    Thanks for the hint. however, this didn't change anything. From the error message "your network user folder in ("null")"  I suspect, that the location of the network folder somehow could not be retrieved, I would expect something like "myserver.mydomain.private" rather than ("null"), but this ist just guessing...

  • by dridas,

    dridas dridas Aug 4, 2014 11:19 AM in response to roberting
    Level 1 (0 points)
    Aug 4, 2014 11:19 AM in response to roberting

    if you use Workgroup Manager, authenticate to your server and then select the user, on the right hand side select the home tab, highlight the folder and then click on the button "Create Home Folder" and save...

     

    then try login in again with the user...

  • by Linc Davis,

    Linc Davis Linc Davis Aug 4, 2014 12:23 PM in response to roberting
    Level 10 (207,995 points)
    Applications
    Aug 4, 2014 12:23 PM in response to roberting

    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.

    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. 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.