Mike Matthews

Q: File sharing and time machine backups fail after upgrade to Mavericks Server

Hi:

 

I've tried several times to upgrade from 10.8.5 server to 10.9.5 and everything seems fine except users can no longer connect via file sharing and time machine backups fail due to a password problem. (And this is the same password.)

 

Adding events to the Calendar server works just fine with the same password.

 

The problem may be in the data conversion after downloading and running Server 3.2.1. Steps I followed:

 

1. Download and install Mavericks (10.9.5)

2. Download and install Server 3.2.1

3. Run Server 3.2.1.

4. Can connect as a guest. Registered user cannot connect to file server. Time Machine backups also fail. Dialog box shakes as if to indicate a password problem. Creating calendar events for the same account using the same password work correctly. From Console:

 

10/13/14 12:31:14.986 PM com.apple.backupd[67724]: Authentication error (80) - the correct user or password info may not exist in the System.keychain or the server may no longer allow access for this user.

 

I also tried this:

 

1. Download and install Mavericks (10.9.5)

2. Download and install Server 3.2.1

3. Connect to server using sidebar in a Finder window. Some share points appear, but not all of them.

4. Run Server 3.2.1.

5. Registered cannot connect to file server. Time Machine backups also fail. Dialog box shakes as if to indicate a password problem.

 

I've seen and done these:

 

http://support.apple.com/kb/HT5300

OS X Server: Upgrade and migration from Mountain Lion

 

There are no open directory replicas. Open Directoy is running on this server only.

 

I'm also getting error messages on the server that say: server not found in database: Krbtgt no such entry found in hdb mavericks

 

Some sort of Open Directory problem? Shut off file sharing before upgrading? Any suggestions?

 

mm

OS X Mavericks (10.9)

Posted on Oct 13, 2014 6:09 PM

Close

Q: File sharing and time machine backups fail after upgrade to Mavericks Server

  • All replies
  • Helpful answers

  • by Linc Davis,

    Linc Davis Linc Davis Oct 14, 2014 4:03 PM in response to Mike Matthews
    Level 10 (207,963 points)
    Applications
    Oct 14, 2014 4:03 PM in response to Mike Matthews

    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, including third-party "security" software.

    10. If you've created any replica servers, delete them.

    11. 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 Mike Matthews,

    Mike Matthews Mike Matthews Apr 3, 2016 11:43 PM in response to Linc Davis
    Level 1 (21 points)
    Apr 3, 2016 11:43 PM in response to Linc Davis

    I have no idea why, but upgrading to El Capitan server ra couple of weeks ago to not result in either of these problems occurring. Go figure.

     

    mm