AFP548

Another client bind failure

(My binding problem seems different enough from the one just posted, that I've posted as a new topic.) I have one 10.6.2 client that was once bound to our 10.6.2 OD master. After unbinding it following a re-build from scratch of the OD master (one of many in a very frustrating series of learning experiments!), I can no longer bind it. Whether using Directory Utility or dsconfigldap, I get "Invalid credentials supplied for binding to the server", even though I am using the correct diradmin username/password, which works on other clients. I have rebuilt my client's local Kerberos, using the following steps: Delete 3 Kerberos items in Keychain Access. [code]sudo rm -rf /var/db/krb5kdc sudo /usr/libexec/configureLocalKDC[/code] No help. I have even done a clean install of 10.6 client on an external drive and booted from that drive. It gets the same invalid credentials error when attempting to bind to OD master during OS installation, and, after applying all patches to 10.6.2, when attempting the bind through Directory Utility or dsconfigldap. Server Admin on OD master shows no computers with my client's name, so there does not appear to be a name conflict. I am at my wit's end. Can anyone help? ---------- Here is the output from dsconfigldap: MyClient:~ user$ sudo dsconfigldap -f -a mymaster.fqdn.com -c MyClient -u myODadmin -p myODadminpassword -v dsconfigldap verbose mode Options selected by user: Force authenticated (un)binding option selected Add server option selected Server name provided as Computer ID provided as Network username provided as Network user password provided as Local username determined to be Step 1 - Server Information Discovery Status: Success - Server Responded. Step 2 - Validating Record/Attribute Mapping Status: Success - Valid Record/Attribute Mapping Step 3 - Detecting Required Security Levels and Binding requirements Status: Success WARNING: No Security Levels configured by Administrator! Your LDAP server supports Secure authentication. Directory Binding is ENABLED and REQUIRED. Step 4 - Attempting to bind computer as MyClient Status: Failed - Invalid credentials. Invalid credentials supplied for binding to the server
Exit mobile version