Tiger client cannot bind to 10.6.8 server

Question

When attempting to bind a 10.4.11 client to our 10.6.8 Open Directory server, the DirectoryService process on the client crashes and the bind fails. 10.5.x and 10.6.x clients have no trouble binding and every other element of ldap, kerberos, and password server appear to be working normally.
We're also noticing errors in slapd.log on the server for 10.4 clients that were previously bound, eg...
"SASL [conn=1637825] Failure: no user in database ed-12377" In these cases, the existing bind appears normal in WGM and the client machine is working as expected.
I'm not looking for suggestions as much as I'd like to see if anyone else is able to bind an ancient 10.4.11 (PPC) client to a 10.6.8 server. The answer to this question would simplify our troubleshooting path significantly. Of course, if you know exactly what's going on here, I'm all ears!
Thanks!
-Lyle
From system.log on the Tiger/10.4.11 client:
Jul 12 11:50:44 Ed-13229 launchd: Server 0 in bootstrap 1103 uid 0: "/usr/sbin/DirectoryService"[255]: exited abnormally: Bus error
Jul 12 11:50:44 Ed-13229 DirectoryService[262]: Launched version 2.1 (v353.6)
Jul 12 11:50:44 Ed-13229 crashdump[261]: DirectoryService crashed
Jul 12 11:50:44 Ed-13229 crashdump[261]: crash report written to: /Library/Logs/CrashReporter/DirectoryService.crash.log
The crash.log from the Tiger/10.4.11 client, edited and limited to just the crashed thread:
OS Version:     10.4.11 (Build 8S165)
Report Version: 4
Command: DirectoryService
Path:    /usr/sbin/DirectoryService
Parent:  launchd [1]
Thread: 1
Exception:  EXC_BAD_ACCESS (0x0001)
Codes:      KERN_PROTECTION_FAILURE (0x0002) at 0x00000000
Thread 1 Crashed:
0   libSystem.B.dylib                        0x9002e4cc strcasecmp + 84
1   DirectoryService                         0x00078d70 CLDAPv3Plugin::TryPWSPasswordSet(unsigned long, unsigned long, sLDAPContextData*, tDataBuffer*, char const*) + 372
2   DirectoryService                         0x0003a778 CLDAPv3Plugin::DoAuthenticationOnRecordType(sDoDirNodeAuthOnRecordType*, char const*) + 3440
3   DirectoryService                         0x0001563c CLDAPv3Plugin::HandleRequest(void*) + 848
4   DirectoryService                         0x0001818c CLDAPv3Plugin::ProcessRequest(void*) + 328
5   DirectoryService                         0x000032d8 CRequestHandler::HandlePluginCall(sComData**) + 880
6   DirectoryService                         0x00004274 CRequestHandler::HandleRequest(sComData**) + 92
7   DirectoryService                         0x0000d794 CMessaging::SendInlineMessage(unsigned long) + 196
8   DirectoryService                         0x0001fed8 dsDoDirNodeAuthOnRecordType + 716
9   DirectoryService                         0x0007eba0 CLDAPv3Plugin::DoNewServerBind2(sDoPlugInCustomCall*) + 2364
10  DirectoryService                         0x0007e198 CLDAPv3Plugin::DoNewServerBind(sDoPlugInCustomCall*) + 476
11  DirectoryService                         0x0007bad0 CLDAPv3Plugin::DoPlugInCustomCall(sDoPlugInCustomCall*) + 1920
12  DirectoryService                         0x0001566c CLDAPv3Plugin::HandleRequest(void*) + 896
13  DirectoryService                         0x0001818c CLDAPv3Plugin::ProcessRequest(void*) + 328
14  DirectoryService                         0x000032d8 CRequestHandler::HandlePluginCall(sComData**) + 880
15  DirectoryService                         0x00004274 CRequestHandler::HandleRequest(sComData**) + 92
16  DirectoryService                         0x000428e0 dsmig_do_api_call + 312
17  DirectoryService                         0x000889d8 _Xapi_call + 276
18  DirectoryService                         0x00088684 DirectoryServiceMIG_server + 160
19  DirectoryService                         0x0003cab0 dsmig_demux_notify(mach_msg_header_t*, mach_msg_header_t*) + 480
20  libSystem.B.dylib                        0x90108aec mach_msg_server + 520
21  DirectoryService                         0x0003cdb4 CMigHandlerThread::ThreadMain() + 348
22  ...ectoryServiceCore.Framework           0x971ff5f4 DSCThread::Run() + 52
23  ...ectoryServiceCore.Framework           0x971ff348 DSLThread::_RunWrapper(void*) + 96
24  libSystem.B.dylib                        0x9002b908 _pthread_body + 96

Answer 1

Hi mcraig55,
Thanks for the response and suggestion!
I did review the security settings back when this started. After an OD rebuild (export, demote, promote, import) a few months ago, our standard security settings had not been restored. I tried to bind the 10.4 client with clear text allowed on both sides (server and client). Then, re-enabled the disabling of clear text passwords (what it should have been) and tried again with both sides set the same. In all cases I still get an error:
Unexpected error while binding - operation cancelled.
I also used this kb article (http://support.apple.com/kb/TA25124) to try SSL to see if the behavior would be different - no change.
Interestingly, the directory does show the client in the computer list. However, the Directory Access application doesn't "know" it's bound. Even more bizarre, the client is taking the preferences that were set for the workstation by Open Directory (eg. the message we display at the login window).
So, at this point, it seems to be 'working.' My speculation is that Directory Service crashes on the client before it can tell the Directory Access application that the client is bound.
Funky stuff.
Thanks!