david_austin
Level 1 (0 points)

Q: OD users unable to connect to a server via afp

We have a Mac OS 10.9.2 with Server 3.1.2.  We are able to access the server for file sharing via smb with OD accounts just fine.  But we are unable to connect to the server using afp with any OD account, only local system accounts.  I have tried turning off SMB for all of the file shares, but this did not help resolve the issue.

 

The log shows a login attempt immediately followed by a logout.

 

Aug  7 13:40:33 server.company.com AppleFileServer[736] <Info>: IP 192.168.101.2 - - "Login -----" -5023 0 0

Aug  7 13:40:33 server.company.com AppleFileServer[736] <Info>: IP 192.168.101.2 - - "Logout -----" -5023 0 0

 

I did edit out the user and the server name.

 

Any help would be greatly appreciated.

 

Thank you.

Mac mini, OS X Mavericks (10.9.2)

Posted on Aug 7, 2014 11:43 AM

Close
david_austin

Q: OD users unable to connect to a server via afp

  • All replies
  • Helpful answers

  • by Linc Davis,

    Linc Davis Linc Davis Aug 7, 2014 11:20 PM in response to david_austin
    Level 10 (207,995 points)
    Applications
    Aug 7, 2014 11:20 PM in response to david_austin

    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.