Hi, I?m looking to implement a 2-node Samba cluster using Samba version 3.0.9 running on Redhat Enterprise 3 Taroon update 3. Each node will be located in a separate location and connected via dual fibre to individual EMC storage (the data will be mirrored between each storage unit) and we are aiming to run Legato AAM to provide the clustering. At the moment each Samba node is a member of our Windows domain and can individually authenticate users against Active Directory and share files with ACL?s etc. My understanding is that both nodes within the cluster must have an understanding of the ID mappings allocated on each node otherwise when a failover is initiated the mappings will be inconsistent and the defined permissions will be incorrect. How do I go about ensuring the ID mappings are correct? Is it a case of adding the users to an LDAP backend and then pointing both smb.conf files to that? I did read a small section in the Samba How-To under Section 6: Domain Membership that covered ?Sharing User ID Mappings between Samba Domain members? but it didn?t go into to much detail. Is this the correct path to go down or am I barking up the wrong tree? If anyone has any advice/experience or ?best practice? ideas please let me know. Thanks in advance, Simon ******************************************************************************** The information contained in this email message may be confidential. If you are not the intended recipient, any use, interference with, disclosure or copying of this material is unauthorised and prohibited. Although this message and any attachments are believed to be free of viruses, no responsibility is accepted by T&F Informa for any loss or damage arising in any way from receipt or use thereof. Messages to and from the company are monitored for operational reasons and in accordance with lawful business practices. If you have received this message in error, please notify us by return and delete the message and any attachments. Further enquiries/returns can be sent to postmaster@tfinforma.com