iNikoF1
Level 1 (0 points)

Q: Login to network accounts don't work

Hello everyone, I have a Mc OSX Server (10.9) and some Mac clients also 10.9.

 

I need of the account network on the server and authenticating to mine account from any client independently.

I set server for Open Directory, File sharing and I create my network accounts with their home folder in a shared folder.

I join my client on server and I check for login network accounts in windows login, my clients have green button on server, but when I try to login at my account it don’t work.

 

I try many tutorial about it, but without success.

 

Have you any ideas or suggestions?

 

 

Thanks a lot!

 

Niko 

OS X Mavericks (10.9.3)

Posted on May 28, 2014 5:52 AM

by iNikoF1,Solvedanswer
iNikoF1 iNikoF1
Level 1 (0 points)
A:

Thanks Davis, with your suggestions I think to check DNS on my router and I solved my problem. I assign server IP at primary DNS in router setting and now it work perfectly.

 

Thank you very much!

 

Niko

Posted on May 28, 2014 10:29 AM

Close
iNikoF1

Q: Login to network accounts don't work

  • All replies
  • Helpful answers

  • by Linc Davis,Helpful

    Linc Davis Linc Davis May 28, 2014 8:15 AM in response to iNikoF1
    Level 10 (207,995 points)
    Applications
    May 28, 2014 8:15 AM in response to iNikoF1

    Many, if not most, 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 master'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. On the Accessing your Server sheet, 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 master 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. Export all OD users, delete them, turn off OD, turn it back on, and import. Ensure that the UID's are in the 1001+ range.

  • by iNikoF1,Solvedanswer

    iNikoF1 iNikoF1 May 28, 2014 10:29 AM in response to Linc Davis
    Level 1 (0 points)
    May 28, 2014 10:29 AM in response to Linc Davis

    Thanks Davis, with your suggestions I think to check DNS on my router and I solved my problem. I assign server IP at primary DNS in router setting and now it work perfectly.

     

    Thank you very much!

     

    Niko