status of DRS efforts in Samba4 (and a developer tutorial)

[Rohit Rajan]

Dear All,

Any works on it will be helpfull

On 2/8/2010 5:59 PM, Rohit Rajan wrote:
> Hi,
>
> I tried the DRS on 2 seperate machines 1 the primary DC running Samba 
> 4.0.0alpha11-GIT-802e932 on CentOS release 5.4 (Final) and all is well 
> here, i made the changes to the smb.conf file and added the 
> replication commands
>
> dreplsrv:periodic-interval = 10
> dreplsrv:periodic-startup-interval = 5
>
> then started samba with the command "samba -i -M single -d4"
>
> then on the second machine i picked the latest git and done make 
> install, then copied the smb.conf from the first server and changed 
> the netbios name.
>
> also i copied the krb5.conf from the first DC and copy it onto second
>
> now when i'm trying to vampire it i'm getting this error
>
> Analyze and apply schema objects
> Failed to convert object 
> CN=account,CN=Schema,CN=Configuration,DC=catalyst-us,DC=com
> Failed to commit objects: WERR_GENERAL_FAILURE
> libnet_BecomeDC() failed - NT_STATUS_UNSUCCESSFUL
> Vampire of domain failed: NT_STATUS_UNSUCCESSFUL
> return code = -1
>
> any help would be wonderfull, thanks in advance
>


-- 
Please consider the environment before printing this e-mail
This message may contain confidential, proprietary or legally privileged information. In case you are not the original intended recipient of the message, you must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message and you are requested to delete it and inform the sender. 

Any views expressed in this message are those of the individual sender unless otherwise stated. Nothing contained in this message shall be construed as an offer or acceptance of any offer by "Catalyst Business Partners" or any of its subsidiaries unless sent with that express intent and with due authority of Catalyst Business Partners. 

Catalyst Business Partners has taken sufficient measures and precautions to prevent the spread of viruses. However the company accepts no liability for any damage caused by any virus transmitted by this email.