similar to: Replication Error Between Differing Samba Versions During Upgrade

----- On Mar 1, 2019, at 3:35 AM, samba samba at lists.samba.org wrote: > > I wonder if this has anything to do with the 'you cannot upgrade > directly from 4.7.x to 4.9.x' bug ? I was not aware of this bug. Do you think I should scrap this upgrade and try again jumping like so? 4.0.6-12 -> 4.7 -> 4.8 -> 4.9 > I know this might seem strange, but try running

Dear all, Running samba-tool ldapcmp on my both DCs samba 4.1.7 leads to the output : Attributes found only in ldap://s4master: msDS-NcType serverState FAILED How to deal with this? I am missing something? [root at s4slave ~]# samba-tool ldapcmp ldap://s4master ldap://s4slave -Uadministrator domain Password for [TPLK\administrator]: * Comparing [DOMAIN]

Hello all- I am trying to upgrade a old domain to a newer version. The old DCs are a custom compiled version of Samba, so instead of upgrading the DCs in place, the plan is to upgrade by joining new DCs to the domain, replicating data and then shutting down the old ones after transferring the FSMO roles. I had the new DC (dc3, version 4.9.4-12) replicating to the other DCs (dc0, versions

Hello, I had posted this in another topic, but because the problem is different, I decided to create a new topic. Conf: - Primary DC/pdc Emulator as DC3 - Second DC as DC4 After an upgrade from schema 45 to 69 in DCs, when adding a computer in the domain and if the domain to respond is DC4 the synchronization for DC3 is not done. I already did several tests that I already knew and also new

On 16/07/15 07:19, Daniel Müller wrote: > On my site with samba 4.18 on centos 6: > > 'samba-tool ldapcmp ldap://DC1 ldap://DC2 -Uadministrator' failed with this result msDS-NC Type failed : > > [root at s4master ~]# samba-tool ldapcmp ldap://s4master ldap://s4slave -Uadministrator > Password for [TPLK\administrator]: > > * Comparing [DOMAIN] context... >

On 16/07/15 12:20, mathias dufresne wrote: > Here I obtained: > --------------------- > * Comparing [DOMAIN] context... > Failed search of base=DC=ad,DC=domain,DC=tld > ERROR(ldb): uncaught exception - LDAP client internal error: > NT_STATUS_UNEXPECTED_NETWORK_ERROR > File "/usr/lib/python2.7/dist-packages/samba/netcmd/__init__.py", line > 175, in _run >

Here I obtained: --------------------- * Comparing [DOMAIN] context... Failed search of base=DC=ad,DC=domain,DC=tld ERROR(ldb): uncaught exception - LDAP client internal error: NT_STATUS_UNEXPECTED_NETWORK_ERROR File "/usr/lib/python2.7/dist-packages/samba/netcmd/__init__.py", line 175, in _run return self.run(*args, **kwargs) File

On my site with samba 4.18 on centos 6: 'samba-tool ldapcmp ldap://DC1 ldap://DC2 -Uadministrator' failed with this result msDS-NC Type failed : [root at s4master ~]# samba-tool ldapcmp ldap://s4master ldap://s4slave -Uadministrator Password for [TPLK\administrator]: * Comparing [DOMAIN] context... * Objects to be compared: 606 Comparing: 'CN=Builtin,DC=tplk,DC=loc'

I'm understand, why I get error about unique index violation on objectSid: samba-tool fsmo show RidAllocationMasterRole owner: CN=NTDS Settings,CN=PDC,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=ad,... Last created object have objectSid S-1-5-21-763247336-2482037999-3416227170-2001 (it is record for computer) Last symbols is 2001, and last assigned RID is 2001: [root

21.11.2016 12:32, L.P.H. van Belle via samba пишет: > Hai, > > Since your getting. > finddcs: No matching server found >> ERROR: Invalid IP address '3(NXDOMAIN)'! > There is something wrong in the base of you setup. yes, and it is a server own local hostname see "DC server own hostname must be part of ad dc domain?" thread your script relies on

On 28/06/16 12:05, Zhuchenko Valery wrote: > I'm understand, why I get error about unique index violation on objectSid: > > samba-tool fsmo show > RidAllocationMasterRole owner: CN=NTDS > Settings,CN=PDC,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=ad,... > > Last created object have objectSid > S-1-5-21-763247336-2482037999-3416227170-2001 (it is

Hai, Since your getting. finddcs: No matching server found > ERROR: Invalid IP address '3(NXDOMAIN)'! There is something wrong in the base of you setup. Check all DC's for ipnumbers (A) and PTR records. Dont forget to create the reverse zone yourself. https://wiki.samba.org/index.php/Samba_AD_DC_Troubleshooting

Hi Valery, First thank you for this detailed information about your searches. I find them very interesting. Here I'm thinking of two workarounds. The first one would be to list deleted objects RIDs, to verify RID=2002 is really the last one used, being sure there is no deleted object with RID=2003 and so on. Then once you get the last RID used, you could change RidNextRid to match this

Hi, I am running a Windows Domain based on 2 Samba AD servers. The setup is running mostly fine but I have the impression that the 2 DC's are not syncing their information. For instance: - I added a Windows pc to the domain last week, when I started 'Active directory users and computers' today on a windows pc I could not see that pc, after rebooting one of the DC's the pc

On Thu, 28 Feb 2019 18:04:50 -0600 (CST) Mike Ray via samba <samba at lists.samba.org> wrote: > Hello all- > > I am trying to upgrade a old domain to a newer version. The old DCs > are a custom compiled version of Samba, so instead of upgrading the > DCs in place, the plan is to upgrade by joining new DCs to the > domain, replicating data and then shutting down the old

Hi there! Here it is a setup with an Windows 2003 SBS and two Samba 4.1.2. Everything is working fine, but I found differences in LDAP and need to know if this is relevant for replication samba-tool ldapcmp ldap://sbssrv2003 ldap://samba4.1.2 [...] Comparing: 'CN=Builtin,DC=SAMBADOMAIN,DC=local' [ldap://gaia] 'CN=Builtin,DC=SAMBADOMAIN,DC=local' [ldap://samba1] Attributes

27.06.2016 18:45, mathias dufresne: > Perhaps you don't have yet duplicate objectSid as that's not supposed to be > possible. > Rather than scripting something to look for objectSid used twice I would > start with dbcheck and other tools to verify that your database is > consistent and identical on all servers. [root at pdc ~]# samba-tool dbcheck Checking 3346 objects

Hello, I'm testing a Samba 4.1.10 ADC in a 2008 R2 level environment. I successfully setup a Win 2008R2 & Samba 4.1.10-sernet controller. But after adding Exchange 2013 things stopped working. I removed the Samba DC from AD, removed all leftovers in AD and re-added it as DC. Adding Samba as DC goes ok, no errors. But running repadmin /showreps gives me a 8418 error complaining about

Hai, Reboot both servers first, DC1 and wait until its fully up, then reboot DC2, and run the replicate again but now like this : samba-tool drs replicate dc_WITH_FSMO_ROLES dc_TO_SYNC_TO DC=win,DC=office report if this worked. And check with this one, you can run it on any samba DC. https://secure.bazuin.nl/scripts/samba-check-db-repl.sh configure it, and run it, and report back. For the

On 22/01/15 00:11, Gilbert Gutierrez wrote: > I have moved to 4.1.16 on both controllers. It did not solve my issue > (though it reduced the errors as seen in the new attached ldap > comparison). I am still getting the error telling me to see the > administrator when trying to add a user via the Windows Active > Directory Users and Computers utility. > > Gilbert > >