RE: 10.3.9 open directory issue.

I had this happen, and the issue I had was that the directory access preference files had become corrupted.  The way I fixed this was to boot up in single user mode, set the volume to read/write, delete the files in /Library/Preferences/DirectoryService.  Let the machine boot back up and it remade the files and everything logged in fine.

Rich

 I am stuck on an Open Directory issue,  and I hope someone can shed some light on it.   The scenario is

    •     10.3.3 client,  plugged into a 10.3.3 server.   Everything is happy.  LDAP info is given via DHCP,  so authentication is a no-brainer,  and everything looks good in Directory Access app.
    •     10.3.3 client taken and  plugged into a 10.3.9 server (test purposes).   Everything is happy.   Same LDAP info over DHCP,  Directory Access app looks like it should.
    •     10.3.3 client taken and plugged BACK into 10.3.3 server,  and the machine will not log in to any network accounts.  I then logged in as local admin,  checked Directory Access,  and everything still looks good.    When logged in as localadmin,  I can still *authenticate* to the server with a network username/pass when I mount a drive via AFP,  I can also get Kerberos tickets.  I simply cannot log in to a network account to save my life.

Could this be related to the issue I read about on afp548?

http://www.afp548.com/article.php?story=20050422122211759

t.i.a
Vic