Hi all, I have just found this thread. I am having serious problems and am at the end of my tether! I cannot believe Apple can get away with releasing such poor, bug filled software and passing it off as a network operating system, but that is a rant for another day.
My Issue is, I have two servers, both 10.7.5. One Master and one replica. I had multiple issues with getting the replication to work (_LDAP_REPLICATOR binding errors) but for some reason, after leaving it overnight, this has started working now.
The failover to the replica is not working correctly. I have some 10.8.x clients, bound to the master. When the master goes down, these clients find the replica with no issues. If the master is down for an extended amount of time however, these start failing logon too, however there is no red dot, they just hang. I have a couple hundred 10.7.5 clients. These will NOT find the replica if the master goes down. DNS is working with no issues. I then tried binding a 10.7.5 client to the replica instead. I then killed the masters connection, after a short delay, this seemed to work! great I thought. I logged in and out a few times, everything was fine. Rebooted the mac.... "network accounts are not available..". From this moment on, the client would no longer find the master. If i manually bind to the master, no problems. What is going on??
Also, every bit of documentation I can find (what little there is) states that a replica is a read only copy of the master. In the latest iteration, you are also supposed to be able to change limited things on the replica, such as passwords. Why is it then , that I can modify passwords, modify MCX, create users etc and these changes are immediately passed to the master ? how can this be read only!!? it is definitely a replica, as viewed in server admin.
Can anyone shed some light?