[Samba] DRS replication fails with Windows 2003 R2

Dmitry Khromov icechrome at gmail.com
Thu Sep 27 05:11:05 MDT 2012

In continuation to https://lists.samba.org/archive/samba-technical/2012-September/087072.html


> [2012/09/27 14:48:08,  0] ../source4/librpc/rpc/dcerpc_util.c:660(dcerpc_pipe_auth_recv)
>  Failed to bind to uuid e3514235-4b06-11d1-ab04-00c04fc2dcd2 for e3514235-4b06-11d1 ab04-00c04fc2dcd2 at ncacn_ip_tcp:6c01aaa6-6374-409d-a7e9-4010964e2dca._msdcs.klin.kifato-mk.com[1026,seal,krb5] NT_STATUS_UNSUCCESSFUL
>[2012/09/27 14:48:08,  0] ../source4/dsdb/repl/drepl_ridalloc.c:43(drepl_new_rid_pool_callback)
>  ../source4/dsdb/repl/drepl_ridalloc.c:43: RID Manager failed RID allocation - WERR_GENERAL_FAILURE - extended_ret[0x0]

I had got same symptoms (on first replication after domain join) with 'master' branch too. 
I'm still unsure what causes this (Windows Event Log doesn't reveal any errors). But, since partitions had been copied during domain join, I would like to try take the Windows DC down, seize FSMO roles on Samba DC and join another Samba DC using the name Windows DC had. However, we have some GPOs in the Sysvol (and the Sysvol isn't going to replicate). So, my questions are: is it possible to manually replicate Sysvol, or should I just restore GPOs from backups after taking Windows DC down? Will such approach introduce any AD inconsistence/fuctionality problems?

Thanks in advance.
Best regards,
Dmitry Khromov

More information about the samba mailing list