covering all basics..
DNS etc etc is all kosher..
1 ODMaster + 4 Replicas
over 1000 clients in Directory
setup has been working fine for over a year now serving up user
info for 10.2.x-10.4.x clients.
all of the sudden a few clients stopped being able to log in.
Nothing about not finding the AFP share or homedirectory or
anything.. login window just shakes.. (usually an authentication
problem eh?)
logged in via local user and can connect to AFP share of network
user OK.
Can ssh to server and even get a Krb ticket via kinit from terminal
for Network user.
90% of the clients can login just fine. Most of the ones having the
problem seem to be 10.3.9 machines.
on the server that these clients would be authenticating against
(happens to be the OD master)
only thing I happen to see in the logfiles that might indicate a
relevant problem...
a bunch of (in PasswordService logs)
LaunchTaskWithIO path =/usr/sbin/kdb5_util, arg1 = dump, arg2 = -,
status = 1
also it seems that replicas seem to be constantly wanting to update
the records..
a bunch of Sync processes keep repeating over and over..
nothing really in the krb or opendirectory logs...
System works fine for most users still...
quadruple checked config in Directory Access on affected machines,
and have starting banging head on the wall..
On the client machines, only log that really seems to give up any
info related to login attempts are in secure.log, but only message
seems act like it's a bad password.
any ideas? something else I could check? more info I could provide
for assistance?
thanks for any help.
Chris H
Hello Chris,
Some things you may want to try for 10.3.9 are:
On the client change /System/Library/StartupItems/LoginWindow/
StartupParameters.plist
This resolves an issue where the login window starts up before the
system has a stable network connection.
On the client make sure that /private/Network/Servers is filled with
aliases not actual files. If there are files in this directory you
can rename/delete the Servers directory and reboot. A corrupt cache
file can also cause an issue. Try renaming /Library/Caches and
rebooting.
Check to see if there is anything in the system and secure logs on
the client. You could also bump up the log level in /etc/syslog.conf
on your clients and server.
Hope this helps!
- Barrett
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Macos-x-server mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
