similar to: replPropertyMetaData & KCC issues after updating to Samba 4.5.0

Hi, For the unsorted attributeID values errors, can you first try: samba-tool dbcheck --cross-ncs --fix --yes 'fix_replmetadata_unsorted_attid' There's too much going on, and it does look like it might be bailing out. Running it with 'fix_replmetadata_unsorted_attid' should fix those first errors, then it will probably be easier to figure out what is happening. The

On 9/22/2016 6:31 PM, Garming Sam wrote: > On 23/09/16 00:59, lingpanda101 at gmail.com wrote: >> For clarification I'll add a few things. >> >> I initially deleted all the NTDS site links for each site and allowed >> the new KCC to create them. However it did not create them I believe >> correctly. By that I mean it defined what appeared to be a bridgehead

On 9/18/2016 6:23 PM, Garming Sam wrote: > Hi, > > For the unsorted attributeID values errors, can you first try: > > samba-tool dbcheck --cross-ncs --fix --yes 'fix_replmetadata_unsorted_attid' > > There's too much going on, and it does look like it might be bailing > out. Running it with 'fix_replmetadata_unsorted_attid' should fix those > first

On 9/21/2016 11:32 PM, Garming Sam wrote: > I would have assumed that deleting all the NTDS connections for all the > DCs would have remedied this issue. I'll write a patch to try to avoid > this error in any case. > > Ignoring this error and answering your earlier question, it's often hard > to tell if the KCC is doing what is expected or not. To figure that out, >

On Wed, 24 Aug 2016 11:56:06 -0400 lingpanda101--- via samba <samba at lists.samba.org> wrote: > > I know you asked recently but I do have them from a long ago > provisioned DC as reference. > > If you have them, I think you may be the only one who does ;-) A bit of searching doesn't turn up anything about _ldaps records, just _ldap. Rowland

On 2016-09-24 06:53, lingpanda101 at gmail.com wrote: > On 9/22/2016 6:31 PM, Garming Sam wrote: >> On 23/09/16 00:59, lingpanda101 at gmail.com wrote: >>> For clarification I'll add a few things. >>> >>> I initially deleted all the NTDS site links for each site and allowed >>> the new KCC to create them. However it did not create them I believe

Hi LingPanda101, .... > > DC=domain,DC=local > site-c\DUNDC1 via RPC > DSA object GUID: a216e718-488f-4821-8d9c-a399e6789222 > Last attempt @ NTTIME(0) was successful > 0 consecutive failure(s). > Last success @ NTTIME(0) > > DC=ForestDnsZones,DC=domain,DC=local > site-c\DUNDC2 via RPC

On 8/24/2016 12:10 PM, Rowland Penny via samba wrote: > On Wed, 24 Aug 2016 11:56:06 -0400 > lingpanda101--- via samba <samba at lists.samba.org> wrote: > >> I know you asked recently but I do have them from a long ago >> provisioned DC as reference. >> >> > If you have them, I think you may be the only one who does ;-) > > A bit of searching

I forgot to associate inter-site links (all using default), which fixed a lot though I'm still having an issue. * vsc site o vsc-dc01 o vsc-dc02 * aws site o aws-dc01 * epo site o epo-dc01 * vsc-dc01 => anywhere: OK * vsc-dc02 => anywhere: not replicating * aws-dc01 => anywhere: OK * epo-dc01 => anywhere: OK I've tried with samba_kcc =

On Thu, 2016-04-14 at 18:07 +0100, Jonathan Hunter wrote: > On 14 April 2016 at 13:37, Jonathan Hunter <jmhunter1 at gmail.com> > wrote: > > > # samba-tool dbcheck --cross-ncs > > Checking 4079 objects > > MYOBJ=value,OU=myou,DC=mydomain,DC=org,DC=uk: 0x00290001 > > MYOBJ=value,OU=myou,DC=mydomain,DC=org,DC=uk: 0x0029000a > >

On 3/13/2017 2:15 PM, Arthur Ramsey via samba wrote: > Upgraded to 4.6.0 on all nodes. Still seeing the same issue. > > If I create an object on vsc-dc02, epo-dc01 or aws-dc01 DCs it doesn't > replicate. If I create it on vsc-dc01 (PDC emulator) then it does > replicate. > > On 03/13/2017 12:13 PM, Arthur Ramsey wrote: >> >> I believe the problem is a lack

On Fri, 2017-05-26 at 13:32 +0200, Karan Blas via samba wrote: > I expected that someone had the same problem before. > > DBchecker module does not provide fix for this. The implication is > that the main Samba DC is working fine but does not allow replication > with other DCs. They report WERR_DS_DRA_INTERNAL_ERROR in samba-tool > dsr showrepl for two two sections:

On Sat, 2017-05-27 at 03:16 +0200, Karan Blas via samba wrote: > > > We found that replPropertyMetaData is uniquie for each user, setting > > > it empty "fix the error' but breaks the user object. > > > > Correct, if you delete replPropertyMetaData in any way, you totally > > break replication. > > > > dbcheck should wipe that part of

Hai,   Environment, Debian Jessie.     I got reports about pc's unable to login into the samba ad dc domain. The trust between this workstation and the primary domain failed. This happend on a win7 and win10 pc. Now, this is "normaly" easy fixed,by rejoining the pc to the domain with the domain wizzard in windows. I noticed this didnt work anymore.   I was running without

Hi We migrated Windows 2003 with Exchange to Samba 4.2.14, 4.3.11 (we have few Samba DCs). Exchange is not needed. Joining was OK but replication is not working. Forcing sync with all attributes from the original WIN DC does not work Seems like the most accurate Samba 4.2.14 (used for changing passwords, adding users etc) has DB error: samba-tool dbcheck : ERROR(<type

hi bringing this thread back to life i waited to ugprade to 4.5.0 and after installing it i get a lot the same errors for users and computers objects when runnung samba-tool dbcheck --cross-ncs Checked 4744 objects (4909 errors) ERROR: unsorted attributeID values in replPropertyMetaData on CN=50LPT01,OU=Computers,OU=50,OU=MAINOU,DC=DOMAIN,DC=MY Not fixing replPropertyMetaData on

Hi people: I can't join a second samba 4.1.16 domain controller to an existing domain. This domain just contain a DC based on Zentyal 3.4. When I try this from the samba server: samba-tool domain join dtcf.etecsa.cu DC -U administrator --realm=dtcf.etecsa.cu --dns-backend=BIND9_DLZ But it returns: No objectClass found in replPropertyMetaData for

I have 2 DCs running 4.1.12 that have stopped replicating and are producing these error messages: from dc1: Failed to commit objects: WERR_GENERAL_FAILURE/NT_STATUS_INVALID_NETWORK_RESPONSE [2014/09/23 10:43:35.530000, 0] ../source4/rpc_server/drsuapi/getncchanges.c:1646(dcesrv_drsuapi_DsGetNCChanges) ../source4/rpc_server/drsuapi/getncchanges.c:1646: DsGetNCChanges 2nd replication on

Hi, About a year ago (I think I was using v4.2.x at the time), I extended the schema of my Samba AD. This worked just fine and since then I have been able to create and edit objects from my custom schema via ADSIEdit. This worked fine under 4.3.x as well - the last such object I successfully created was just over two months ago, at which point I was running some variant of 4.3.x (probably 4.3.5).

I had a AD with 4 Win2003 DC. Now I use a samba4 server as a additional DC. Samba4 server system version: ubuntu 15.04 Samba version: samba 4.3.0 The replication from win2003 DC to samba4 DC was success. But have some problem from samba4 DC to win2003 DC. I can run samba-tool drs showrepl without error. But in log.samba it can found many message like: [2015/10/09 12:53:11.562088, 0]