similar to: samba 4.7.5 and db replication ( refering to closed bug : 13228 )

Hi Guys, I have now updated to 4.5.0 - thank you to all the team for your efforts on this :) I was excited to read in the release notes that there were many replication improvements, and I have run 'samba-tool dbcheck --cross-ncs --fix' on all my DCs; there were many, many replPropertyMetaData and other errors which have now been found and fixed - thanks! However, I think something

On Thu, 2019-03-14 at 07:38 +0000, Rowland Penny via samba wrote: > On Wed, 13 Mar 2019 23:59:29 +0000 > Sérgio Basto via samba <samba at lists.samba.org> wrote: > > > On Wed, 2019-03-13 at 11:22 +0100, L.P.H. van Belle via samba > > wrote: > > > Hi Stefan, > > > > > > Debian 8 ? 9? > > > DC's samba version ? > > >

On Wed, 2019-03-13 at 11:22 +0100, L.P.H. van Belle via samba wrote: > Hi Stefan, > > Debian 8 ? 9? > DC's samba version ? > > Can you post your smb.conf and resolv.conf > > If you check with (per server what is the outcome. ) > samba-tool dbcheck > samba-tool dbcheck --cross-nc > > You could do a forced sync of a good server to the bad one. >

Hi people I have a questions, i have 3 domain controllers, all with samba dc2 with dc1 drs is perfect dc3 with dc1 drs is perfect but dc2 with dc3 i have errors: WERR_DS_DRA_ACCESS_DENIED in CN=Configuration, DC =DomainDNsZonesm anda DC= ForestDnsZones have you any idea what can do? Sorry for my english, i am from Argentine.

Hi, First some background: ================== I had a test environment which had two samba DCs (running v 4.8.0rc2) and 1 Windows Server 2008R2 DC. The samba DCs had been upgraded from v 4.6x and the secrets database was not encrypted (as far as I know). I decided to downgrade one of the samba DCs to v 4.7.4. On re-starting samba after the downgrade the log shows: ldb: unable to dlopen

Samba 4.5.1 (started with this version as well) I started with 3 domain controllers, DC1 and DC2 at the hub, and another, DC3 as a spoke. Everything was running smoothly with this config. No problems with 'samba-tool drs showrepl'. As soon as I started adding more 'spoke' domain controllers I'm getting timeouts in the 'samba-tool drs showrepl' command. I believe

Le 19/11/2018 à 12:33, Julien TEHERY via samba a écrit : > Le 19/11/2018 à 11:14, Marco Gaiarin via samba a écrit : >> Mandi! Julien TEHERY via samba >>    In chel di` si favelave... >> >>> Is there a good pratice when adding new remote DCs in terms of >>> replication >>> topology? >> I think you have to define a topology of the domain, using

Hi all, We are running a three DC samba AD, using 4.12.8 sernet packages. Very stable for years. Today at 12:30 my colleague moved two users from * CN=Users,DC=samba,DC=company,DC=com to * OU=disabled,DC=samba,DC=company,DC=com This change was done on the DC4 at 12:30 using LAM (ldap-account-manager version 7.3) Ever since that, my automated samba-tool ldapcmp scripts started reporting

Hi all, I have an old dc (4.0.9). Let's call it dc1. I also have a new one (4.5.16) which I'm planning to switch to. Let's call it dc2. After initial set up of dc2 I initialised replication and things looked ok for a couple of weeks. Recently I've managed to mess it up. Possibly by editing users and DNS records. Or copying Kerberos cache and trying to use it elsewhere for

hmm, ? Well based on what i see, that error comes at the end of this process, so strange it errors out. Beside that your output looks good. ? You can try to install these, if its python problem Run samba-toold drs showrepl? after every install, that helps in detecting which package you might miss. ? apt install python-dnspython ? apt install python-iso8601 ? apt install python-crypto ? apt

Today I noticed something that has been going on for some weeks: I have 2 dc, (dc1 and dc2) both debian buster with the distro provided samba (4.9.5), recently upgraded from stretch. samba-tool drs showrepl on dc2 says DC=DomainDnsZones,DC=samba,DC=wetron,DC=es Default-First-Site-Name\DC1 via RPC DSA object GUID: 89812346-9037-43b0-86ab-c5052f55125d

Hi, I removed the last server (samba4-dc-old listed below) from the domain, but information related to that server remained. Is there any way to remove this registry from Samba 4? samba-tool drs showrepl Default-First-Site-Name\SAMBA4-DC DSA Options: 0x00000001 DSA object GUID: a1ab021c-0ef7-4fd3-a69d-28afc7c1260a DSA invocationId: a20c8ed0-c72a-4e57-9e59-2236f127d0b8 ==== INBOUND NEIGHBORS

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

Mandi! Julien TEHERY via samba In chel di` si favelave... > Is there a good pratice when adding new remote DCs in terms of replication > topology? I think you have to define a topology of the domain, using ADSS: https://blogs.technet.microsoft.com/canitpro/2015/03/03/step-by-step-setting-up-active-directory-sites-subnets-site-links/ defining links and weight. -- dott. Marco Gaiarin

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! I have 2 DC, now add one more DC, but all dcs dont view between they. New DC is "DC2" DC1 - vlan10 -> OK to DC3(Connectad by openvpn) DC1 -> vlan10 -> OK to DC2(vlan50) DC2-> vlan50 -> OK to DC1(vlan10) DC2-> Openvpn -> Dont "see" DC3 DC3 -> Openvpn -> OK to DC1(vlan10) DC3 -> Openvpn -> Dont "view" DC2(vlan50) All version

Hello List, Im running an network with five samba 4 addc, all on debian wheezy with the sernet packages. Recently an replication error showed up for an single Computer (WIN7-M-ADMIN) record. So I unjoined the pc from the domain deleted it's record from dc1 manually on the other dc's it had been removed automaticaly during unjoin. Now I get the following error [2015/07/21

Hai, ? You can safely ignore?that mesage. ? If both servers are done and running 4.8.? procede to 4.9 ? >> ERROR(<type 'exceptions.KeyError'>): uncaught exception - 'No such element' is fixed in later samba versions ? Greetz, ? Louis ? ? ? Van: Marcio Demetrio Bacci [mailto:marciobacci at gmail.com] Verzonden: vrijdag 30 augustus 2019 11:39 Aan: L.P.H. van Belle

2 debian-DCs ... I get Last attempt @ Wed Mar 13 10:57:11 2019 CET failed, result 121 (WERR_SEM_TIMEOUT) How to proceed here (yes, I google ...), please ...

Hi. Here is my problem. I have 2 DC (DC1, DC2) From DC1 I run samba-tool drs showrepl DC1 ------------------------------------------------------------------------------------- INBOUND NEIGHBORS : OK OUTBOUND NEIGHBORS : OK ==== KCC CONNECTION OBJECTS ==== Connection -- Connection name: 179ef6ba-a138-46d7-9a64-880ab4608b04 Enabled : TRUE Server DNS name :