[jbt]

Yes, just changing hostname back seemed to fix it temporarily..

running changip seemed to break kerberos..

so first I exported my users and groups and DNS records ..
and set back to standalone server

then removed the /var/db/.AppleSetupDone, restarted and re-ran the serversetup without activating anything..

then restarting in single user and set hostname in hostconfig, adding an entry into hosts. then restarting again.

then I run the following as root :

slapconfig -kerberize diradmin REALM_NAME
sso_util configure -r REALM_NAME -f /LDAPv3/127.0.0.1 -a diradmin -p diradmin_password -v 1 all
sso_util configure -r REALM_NAME -f /LDAPv3/127.0.0.1 -a diradmin -p diradmin_password -v 1 ldap

restart again and promote the standalone server to OD master.

whew.

after importing my users and groups ..
all seemed fine.

but all seemed fine the first time I set it up, too

my concern is what caused it go whackey the first time
(although std setup leaved hostconfig host : -AUTOMATIC-)

could that be it ??

[jbt]

I have a very similar problem.. have tried using changip and resetting hostname, but it eventually seems to revert.

besides reverting the LDAP directory to the .local domain, the hostname reverts to a public FQDN that the second interface (on an Xserve) was attached to rather than my internal serve.tld. What’s really strange is that I’ve shut off the external interface and removed all reference to that IP address and STILL get that hostname. This seems to cause my LDAP directory to randomly X-out users, eventhough they still ‘appear” to be active in the WM.
AND, when this happens, kerberos authentication goes all nutty …
any idea what’s up with this ??

[Author]

Posts