similar to: samba-tool domain schemaupgrade fails on DC member

Thanks Rowland and Garming for your help!! How about "another DC", or 'a second DC' ? Ok. Got it! :D Alternatively, re-joining the domain controller (or joining a new DC and > demoting the old one) probably works because I believe there is code to > handle this case. I re-joined (remove secrets.tdb and .lbd, copy idmap from existing DC...) and now works properly!

Hello, Thanks for the feedback Garming!!! 👍 On Wed, Apr 17, 2019 at 12:35 AM Garming Sam <garming at catalyst.net.nz> wrote: > Hi, > > While I think we have most of the 2012 schema problems under control > now, there's still quite a bit of work to get the functional level > things working. In order to actually raise the level, we still need to > implement a number of

Hi, This is a known issue: https://bugzilla.samba.org/show_bug.cgi?id=12204 https://bugzilla.samba.org/show_bug.cgi?id=13713 There are currently patches in master to fix this issue. We could probably backport a patch to 4.10, but you'd have to rebuild Samba. Alternatively, re-joining the domain controller (or joining a new DC and demoting the old one) probably works because I believe there

Hi, While I think we have most of the 2012 schema problems under control now, there's still quite a bit of work to get the functional level things working. In order to actually raise the level, we still need to implement a number of features (mostly security). We're able to do some prep steps (so that things like Windows server 2012 R2 appear to join us but still use 2008 R2 FL) but

Hi, Everything seems to be ok, but the following is happening now. When I put a new computer in the domain, it only appears in the "second DC" and does not replicate to the first DC. root at dc3:~# samba-tool computer list |grep MINT-TESTE root at dc3:~# root at dc4:~# samba-tool computer list |grep MINT-TESTE MINT-TESTE$ root at dc4:~# Any idea? On Wed, Apr 17, 2019 at 8:12 AM

Hello, If when joining the computer in the domain and at the moment who received the request was the "second DC", it should automatically synchronize with the "first DC", correct? On Wed, Apr 17, 2019 at 5:00 PM Elias Pereira <empbilly at gmail.com> wrote: > Hi, > > Everything seems to be ok, but the following is happening now. > > When I put a new

I joined the windows 2019 domain, where among the controllers there is a Samba DC version 4.8.5, and after that the replica stopped working windows servers <--> samba DC. Upgrading to version 4.9.4 did not help Errors: ``` фев 12 14:15:28 srv-dc01 samba[24637]: [2019/02/12 14:15:28.679872,  0] ../source4/dsdb/repl/replicated_objects.c:248(dsdb_repl_resolve_working_schema) фев 12

I have a very old domain i inherited that is running samba 4.5.6 but is on schema version 30. I added a windows 2003 DC and used the 2008r2 adprep.exe utility to upgrade the schema to version 47. To do so the 2003 server had to take the schema and infrastructure roles. I am now trying to use the repadmin utility to sync the schema back to samba to it is failing with the following: [2017/06/09

On 12.02.2019 11:16, Rowland Penny via samba wrote: > On Tue, 12 Feb 2019 14:28:44 +0500 > Шигапов Денис Вильданович via samba <samba at lists.samba.org> wrote: > >> I joined the windows 2019 domain, where among the controllers there >> is a Samba DC version 4.8.5, and after that the replica stopped >> working windows servers <--> samba DC. Upgrading to

Hai,   Now, differences is fine, but can you see if one of the 2 servers is correct, and for that it might be handy to share the output.   You can push the good DB to the other DC. ( a forced replication )   And i can understand why you upgrade ...  Did you see :    samba-tool domain schemaupgrade --help Usage: samba-tool domain schemaupgrade [options] Domain schema upgrading Options:   -h,

im on phone, had a quick small look at the dc3 output. is your time in sync, it looks like a 3 - 10 min different. gr. Louis Op 7 mei 2019, om 18:34, Elias Pereira <empbilly at gmail.com> schreef: Hello, dc3: http://pasted.co/6b703479 dc4: http://pasted.co/5068fc6e diff: http://pasted.co/025c3242 On Tue, May 7, 2019 at 12:08 PM L.P.H. van Belle via samba <samba at

Hello, dc3 = principal DC dc4 = secondary DC I had this problem last month after updating samba to version 4.10.x. and also the schema from 45 to 69. But it looked like it had been corrected. Today I noticed that on dc4 there are computers that are not on dc3. I updated: 4.7.x to 4.8.x 4.8.x to 4.9.x and only after that I upgrade to 4.10.x version. When I run these commands: samba-tool

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

I believe a schema change on a Windows DC (2008rc) has broken replication with our S4 DCs. Anyone have any tips or pointers to resolve this? I have three S4 DCs [CentOS6] and one Windows 2008R2 DC. 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

hi, I have this DC in aws to fulfill the authentication need of our moodle. # samba -V Version 4.17.7-Debian DNS with SAMBA_INTERNAL The replication of the users and groups happens correctly. Some errors in running samba_dnsupdate, but it is ok anyway. When I ran the command samba-tool dbcheck, I got the return below. # samba-tool dbcheck --cross-ncs --reset-well-known-acls --fix --yes

The principle was not made any changes to occur this problem. We infra have dc3 and dc4 ADDC. root at dc3:/etc/samba# samba -V Version 4.7.7-Debian (van-blle apt) Result of gpupdate /force in a joined computer client: C:\>gpupdate /force > Updating Policy... > User policy could not be updated successfully. The following errors were > encountered: > The processing of Group Policy

While this should work, neither is this particularly harmful. ?Links to objects that don't exist are ignored at runtime. Andrew Bartlett On Tue, 2023-04-04 at 14:39 -0300, Elias Pereira via samba wrote: > hi, > > Any clue? > > On Mon, Apr 3, 2023 at 10:17?AM Elias Pereira <empbilly at gmail.com> wrote: > > > hi, > > > > I have this DC in aws to

Hi all, James, After following James' suggestions fixing the several dbcheck errors, and having observed things for a few days, I'd like to update this issue, and hope for some new input again. :-) Summary: three DCs, all three running Version 4.5.10-SerNet-Debian-16.wheezy, samba-tool dbcheck --cross-ncs reports no errors, except for two (supposedly innocent) dangling forward links

Hi, I have a new Centos 7.6 VM that I self compiled 4.10.3 and joined it to an existing samba AD domain that has 2 existing DCs. One of the existing DCs is running 4.8.7 and the other is running 4.7.7. Everything looks OK except that when I run samba-tool drs showrepl on the new DC (VDC4) I get the following output: (vdc4 pts4) # samba-tool drs showrepl Default-First-Site-Name\VDC4 DSA Options:

Hai Elias, 聽 Sorry for the late reply. I do preffer the list, and i understand why you mailt my directly, but best is to keep this on the list. The more eye that see this, the more chance you have on a reply. I must say, i personaly dont use any trust relations ships. that was long ago when i used that, so im bit rusty here. 聽 Now, i see you are using my 4.8.2 packages. so you on debian. *( or