OS X Server 10.9.x Client will not bind to LDAP/OD Server 10.9.x

Question

I've done multiple server updates, installs etc. with no luck.
I cannot get OS X Maverick 10.9.x clients to bind to a OS X Server Maverick 10.9.x Open Directory LDAP. I've tried clients & server installs of 10.9.1 , .2, & .3 with no luck. When I go to bind I get the mesage seen below. I know it's connecting because if I pruposly put in a wrong password for the "diradmin" user it tells me that credentials are wrong. If I put in the correct password I get this message.
The funny thing is that I still have setup two test servers with 10.7 & 10.8 server and clients of all version bind like they should. The issue is only with Mavericks Server 10.9.x
With searching around in Apple Disscussions I've seen articles that talk about changing DNS to the Mac Server which has not helped me plus we have DNS server in our network already so I do not wish to add more.
Anyone else having this issue?
Thank you!

Answer 1

Many Open Directory problems can be resolved by taking the following steps. Test after each one, and back up all data before making any changes.
1. The OD master must have a static IP address on the local network, not a dynamic address.
2. You must have a working DNS service, and the master's hostname must match its fully-qualified domain name. To confirm, select the server by name in the sidebar of the Server application window, then select the Overview tab. Click the Edit button on the Host Name line. On the Accessing your Server sheet, Domain Name should be selected. On the Accessing your Server sheet, change the Host Name, if necessary. The server must have at least a three-level name (e.g. "server.yourdomain.com"), and the name must not be in the ".local" top-level domain, which is reserved for Bonjour.
3. The primary DNS server used by the master must be 127.0.0.1 (that is, itself) unless you're using another server for internal DNS. The only DNS server set on the clients should be the internal one, which they should get from DHCP if applicable.
4. Follow these instructions to rebuild the Kerberos configuration on the master.
5. If you use authenticated binding, check the validity of the master's certificate. The common name must match the hostname and domain name. Deselecting and then reselecting the certificate in Server.app has been reported to have an effect in some cases.
6. Unbind and then rebind the clients in the Users & Groups preference pane. Use the fully-qualified domain name of the master.
7. Reboot the master and the clients.
8. Don't log in to the server with a network user's account.
9. Export all OD users, delete them, turn off OD, turn it back on, and import. Ensure that the UID's are in the 1001+ range.