search for: micor

Attempting to debug issues with replication I ldapcmd finds differences with the case of the "DC" attribute? Is this normal? LARKIN28 is Samba4 4.5.4, while WINDC1 is Windows 2008R2. [root at larkin28 samba]# samba-tool ldapcmp ldap://larkin28.micore.us ldap://windc1.micore.us -Uadministrator dnsdomain Password for [BACKBONE\administrator]: * Comparing [DNSDOMAIN] context... * Objects to be compared: 859 Comparing: 'DC=Chris_WIN7_VM,DC=micore.us,CN=MicrosoftDNS,DC=DomainDnsZones,DC=micore,DC=us' [ldap://larkin28.micore.us] '...

...9;RidAllocationmasterRole' > > It should show 'CN=NTDS Settings,CN=LARKIN27' > > [root at larkin28 ~]# samba-tool fsmo show > .. > RidAllocationMasterRole owner: CN=NTDS > Settings,CN=LARKIN27,CN=Servers,CN=Default-First-Site > -Name,CN=Sites,CN=Configuration,DC=micore,DC=us > ... > > > > Try running this on the DC: ldbsearch > > > -H/usr/local/samba/private/sa m.ldb '(objectClass=rIDSet)' dn > > > rIDNextRID > > It should should show the DN's of your DCs followed by the contents > > of the 'rIDNextRI...

On Mon, 19 Sep 2016 10:42:34 -0400 Adam Tauno Williams via samba <samba at lists.samba.org> wrote: > On Mon, 2016-09-19 at 15:15 +0100, Rowland Penny via samba wrote: > > No it shouldn't be replicated, the big hint is > > 'FLAG_ATTR_NOT_REPLICATED', it should only be on the DC that holds > > the > > RID master FSMO role, so I supposed the question is,

...t;> It should show 'CN=NTDS Settings,CN=LARKIN27' >>> [root at larkin28 ~]# samba-tool fsmo show >>> .. >>> RidAllocationMasterRole owner: CN=NTDS >>> Settings,CN=LARKIN27,CN=Servers,CN=Default-First-Site >>> -Name,CN=Sites,CN=Configuration,DC=micore,DC=us >>> ... >>> >>>>> Try running this on the DC: ldbsearch >>>>> -H/usr/local/samba/private/sa m.ldb '(objectClass=rIDSet)' dn >>>>> rIDNextRID >>>> It should should show the DN's of your DCs followed by the...

...ok at the line that > starts 'RidAllocationmasterRole' > It should show 'CN=NTDS Settings,CN=LARKIN27' [root at larkin28 ~]# samba-tool fsmo show .. RidAllocationMasterRole owner: CN=NTDS Settings,CN=LARKIN27,CN=Servers,CN=Default-First-Site -Name,CN=Sites,CN=Configuration,DC=micore,DC=us ... > > Try running this on the DC: ldbsearch -H/usr/local/samba/private/sa > > m.ldb '(objectClass=rIDSet)' dn rIDNextRID > It should should show the DN's of your DCs followed by the contents > of the 'rIDNextRID' attributes. these should be '0'...

...sterRole' >>> It should show 'CN=NTDS Settings,CN=LARKIN27' >> [root at larkin28 ~]# samba-tool fsmo show >> .. >> RidAllocationMasterRole owner: CN=NTDS >> Settings,CN=LARKIN27,CN=Servers,CN=Default-First-Site >> -Name,CN=Sites,CN=Configuration,DC=micore,DC=us >> ... >> >>>> Try running this on the DC: ldbsearch >>>> -H/usr/local/samba/private/sa m.ldb '(objectClass=rIDSet)' dn >>>> rIDNextRID >>> It should should show the DN's of your DCs followed by the contents >>> of...

...9;CN=NTDS Settings,CN=LARKIN27' > >>> [root at larkin28 ~]# samba-tool fsmo show > >>> .. > >>> RidAllocationMasterRole owner: CN=NTDS > >>> Settings,CN=LARKIN27,CN=Servers,CN=Default-First-Site > >>> -Name,CN=Sites,CN=Configuration,DC=micore,DC=us > >>> ... > >>> > >>>>> Try running this on the DC: ldbsearch > >>>>> -H/usr/local/samba/private/sa m.ldb '(objectClass=rIDSet)' dn > >>>>> rIDNextRID > >>>> It should should show the DN'...

...--help' for more info. > You could also try forcing replication to the third DC, 'samba-tool > drs replicate --help' for more info. The full-sync reports success, but the issue is not resolved on the third DC. [root at larkin28 ~]# samba-tool drs replicate  --full-sync larkin28.micore.us larkin27.micore.us DC=micore,DC=us Replicate from larkin27.micore.us to larkin28.micore.us was successful. [root at larkin28 ~]# samba-tool fsmo show SchemaMasterRole owner: CN=NTDS Settings,CN=TEMP2008R2DC,... InfrastructureMasterRole owner: CN=NTDS Settings,CN=LARKIN27,... RidAllocationMaster...

...ngs,CN=LARKIN27' >>>>> [root at larkin28 ~]# samba-tool fsmo show >>>>> .. >>>>> RidAllocationMasterRole owner: CN=NTDS >>>>> Settings,CN=LARKIN27,CN=Servers,CN=Default-First-Site >>>>> -Name,CN=Sites,CN=Configuration,DC=micore,DC=us >>>>> ... >>>>> >>>>>>> Try running this on the DC: ldbsearch >>>>>>> -H/usr/local/samba/private/sa m.ldb '(objectClass=rIDSet)' dn >>>>>>> rIDNextRID >>>>>> It should shoul...

...Samba 4.5.4 DC to another, all roles transfered except the DNS related ones - those fail with an LDAP_INSUFFICIENT_ACCESS_RIGHTS [root at larkin28 ~]# samba-tool fsmo show SchemaMasterRole owner: CN=NTDS Settings,CN=LARKIN28,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=micore,DC=us InfrastructureMasterRole owner: CN=NTDS Settings,CN=LARKIN28,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=micore,DC=us RidAllocationMasterRole owner: CN=NTDS Settings,CN=LARKIN28,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=micore,DC=us PdcEmul...

...essage I can find in the event log on the 2008R2 server is -  > > Internal event: The local directory service received an exception > > from a remote procedure call (RPC) connection. Extended error > > information is not available.  > > directory service:  > > LARKIN27.micore.us  > > Additional Data  > > Error value:  > > The handle is invalid. (6) > > How can one debug where, or on what object, it is hung up or stops? > > samba-tool's dbcheck finds only two errors in cn=Configuration, but it > does not repair them.  These appear t...

...1630 out of approximately 1663 objects.   Only message I can find in the event log on the 2008R2 server is -  Internal event: The local directory service received an exception from a remote procedure call (RPC) connection. Extended error information is not available.  directory service:  LARKIN27.micore.us  Additional Data  Error value:  The handle is invalid. (6) How can one debug where, or on what object, it is hung up or stops?

...eplace DCNAME with the dns name of your Domain Controller. I wonder > if OP has exhausted his RID pool. Unlikely but possible. I also see a > similar post on this same issue. > https://lists.samba.org/archive/samba/2016-April/198879.html #### LARKIN26 C:\Users\adam>dcdiag /s:larkin26.micore.us /test:ridmanager /v Directory Server Diagnosis Performing initial setup: * Connecting to directory service on server larkin26.micore.us. * Identified AD Forest. Collecting AD specific global data * Collecting site info. Calling ldap_search_init_page(hld,CN=Sites,CN=Configuratio...

...of Y. So I have been digging, digging, digging, and I found this in the log file of the DC the 2008R2 box is attempting to replicate from - Feb 1 16:52:42 larkin28 samba[18650]: ../source4/rpc_server/drsuapi/getncchanges.c:1961: DsGetNCChanges 2nd replication on DN CN=Configuration,DC=micore,DC=us older highwatermark (last_dn CN=414,CN=DisplaySpecifiers,CN=Configuration,DC=micore,DC=us) Feb 1 16:52:44 larkin28 samba[18650]: [2017/02/01 16:52:44.553389, 0] ../source4/rpc_server/drsuapi/getncchanges.c:1961(dcesrv_drsuapi_DsGetNCChanges) Feb 1 16:52:44 larkin28 samba[18650]:...

...no existing schema, seq_num: 64 schema_fsmo_init: we are master[no] updates allowed[no] Initial schema load needed, as we have no existing schema, seq_num: 64 schema_fsmo_init: we are master[no] updates allowed[no] gendb_search_v: CN=Directory Service,CN=Windows NT,CN=Services,CN=Configuration,DC=micore,DC=us objectClass=nTDSService -> 1 Doing a full scan on CN=Configuration,DC=micore,DC=us and looking for deleted objects Doing a full scan on DC=micore,DC=us and looking for deleted objects Doing a full scan on DC=DomainDnsZones,DC=micore,DC=us and looking for deleted objects Doing a full...

...The Windows 2008R2 DC has the schema master FSMO, and I believe the Exchange schema was added. I am willing to pay US dollars to get this issue resolved. I need the replication restored, the Windows 2008DC, and the Samba4 DCs demoted. [root at larkin27 ~]# samba-tool ldapcmp ldap://temp2008r2dc.micore.us lda p://larkin27.micore.us schema * Comparing [SCHEMA] context... * DN lists have different size: 4267 != 4014 ... -- Adam Tauno Williams <mailto:awilliam at whitemice.org> GPG D95ED383 Systems Administrator, Python Developer, LPI / NCLA

...23 ~]# wbinfo -u | grep steve > steve Here is a debug level 10 from winbind when making the wbinfo -i request 2015/04/15 16:22:19.609439, 5, pid=9576, effective(0, 0), real(0, 0)] ../source3/libads/ldap.c:270(ads_try_connect) ads_try_connect: sending CLDAP request to 192.168.1.79 (realm: micore.us) [2015/04/15 16:22:19.613245, 1, pid=9576, effective(0, 0), real(0, 0)] ../librpc/ndr/ndr.c:296(ndr_print_debug) &response->data.nt5_ex: struct NETLOGON_SAM_LOGON_RESPONSE_EX command : LOGON_SAM_LOGON_RESPONSE_EX (23) sbz...

...ug.cgi?id=10734 prevents normal DC demotion. The DC was still all over in DNS, so I had to pick it out. Now replication between the remaining three DCs is broken [root at larkin26 ~]# samba-tool drs showrepl ERROR(<class 'samba.drs_utils.drsException'>): DRS connection to larkin26.micore.us failed - drsException: DRS connection to larkin26.micore.us failed: (-1073741772, 'NT_STATUS_OBJECT_NAME_NOT_FOUND') File "/usr/lib64/python2.6/site-packages/samba/netcmd/drs.py", line 39, in drsuapi_connect (ctx.drsuapi, ctx.drsuapi_handle, ctx.bind_supported_extensions...

...1663 objects. > Only message I can find in the event log on the 2008R2 server is -  > Internal event: The local directory service received an exception > from a remote procedure call (RPC) connection. Extended error > information is not available.  > directory service:  > LARKIN27.micore.us  > Additional Data  > Error value:  > The handle is invalid. (6) > How can one debug where, or on what object, it is hung up or stops? samba-tool's dbcheck finds only two errors in cn=Configuration, but it does not repair them.  These appear to be references to an original, lon...

...ll gcc libacl-devel python-devel gnutls-devel openldap-devel ./configure make ls bin/samba-tool [**2] https://bugzilla.samba.org/show_bug.cgi?id=12297 >> [root at larkin27 ~]#  ldbsearch --cross-ncs -H >> /var/lib/samba/private/sam.ldb -b >> "CN=Configuration,DC=micore,DC=US"  - s sub >> CN=3ad6381a-9725-4e28-8157-a5a3fde68a43 msDS-NC-Replica-Locations >> # record 1 >> dn: CN=3ad6381a-9725-4e28-8157- >> a5a3fde68a43,CN=Partitions,CN=Configuration,DC=micore,DC=us >> msDS-NC- >> Replica-Locations: CN=NTDS Settings,CN=LARKIN...