This may occur if the "/Library/Preferences/edu.mit.Kerberos" plist file contains IP addresses in addition to, or in place of, host names of Kerberos realms that the Mac is bound to.
Open the edu.mit.Kerberos file (located in /Library/Preferences) in a text editor. Check the [realms] section for either admin_server or kdc entries that are IP addresses.
Move the edu.mit.Kerberos file to the desktop and restart the client computer. If login is quicker, then follow the steps below.
To resolve the issue
To resolve this for all of the client computers bound to your Open Directory, you'll need to edit the master template that creates the edu.mit.Kerberos file:
- Open Workgroup Manager.
- Connect to the Open Directory Master.
- View the /LDAPv3/127.0.0.1 directory, authenticating as the directory admin if needed.
- In Workgroup Manager, open Preferences, make sure the Show "All Records" tab and inspector checkbox is checked, then close the preferences.
- In the left hand pane, in addition to the Users, Groups, Computers, and Computer Groups icons, you'll see an icon resembling a target. Click the icon to access to All Record Types.
- You'll now see a pull-down menu below the row of icons. Change it to display Config.
- In the list below the pull-down menu, click KerberosClient.
- In the right-hand pane, select XMLPlist and then click the Edit button below the list.
- A two-paned window will drop down. In the top half, you'll see the contents of the edu.mit.Kerberos master. As a safety precaution, you can copy all of the text and past it into a text file that you can save as a backup.
- Find the KADM_List and KDC_List arrays and remove any references to IP addresses. If needed, replace an IP address with a valid host name.
- Increment the generationID number by 1.
- Once all edits are complete, click OK.
- After the pull-down window disappears, click Save.
The next time a client computer connects to the Open Directory, the new version of the edu.mit.Kerberos file will be pushed to /Library/Preferences. At the client computer's next restart, logins should take the expected time.