similar to: Question about syncing idmap.ldb between Domain Controllers

Hi Adnan, Your steps look correct. There are no ?secondary? or ?primary? DCs. All equal except for FSMO roles. http://samba.bigbird.es/doku.php?id=samba:fsmo-roles You do not need to back up sysvol or idmap as they should be already synced with other DCs. http://samba.bigbird.es/doku.php?id=samba:sync-sysvol http://samba.bigbird.es/doku.php?id=samba:sync-idmap.ldb Regards, LP On 28 Apr 2025

Agree. But I don?t think it is. See: root at member:/# cat /etc/hostname member root at member:/# cat /etc/hosts 127.0.0.1 localhost 192.168.3.1 member.mad.mater.int member root at member:/# cat /etc/resolv.conf search mad.mater.int nameserver 192.168.0.12 -> DC1 nameserver 192.168.0.13 -> DC2 nameserver 192.168.0.14 -> DC3 nameserver 192.168.0.62 -> DC4 root at member:/# cat

On Sun, 9 Jun 2024 10:20:46 +0100 Luis Peromarta <lperoma at icloud.com> wrote: > Agree. > > But I don?t think it is. See: > > root at member:/# cat /etc/hostname > member > > root at member:/# cat /etc/hosts > 127.0.0.1 localhost > 192.168.3.1 member.mad.mater.int member > > root at member:/# cat /etc/resolv.conf > search mad.mater.int >

On 5/5/2017 11:08 AM, Anantha Raghava wrote: > > Hello James, > > Even after setting the rfc2307 in smb.conf replication error continues > and password change error continues. Error thrown while forcing > replication is shown below. > > ------------------------------------------------------------------- > Even after setting RFC, DC2 is not getting synced from DC1.

On 05/06/16 10:05, Jo wrote: > I joined a Windows 10 Pro system to my (still experimental) domain. The > windows system actually hosts DC2 as a VM, and another Windows (Server 2008 > R2) at another location hosts DC1 also as a VM. The two locations are > connected via a VPN, both systems run only when needed. The windows system > does not directly use DC2 for DNS but instead talks

On 5/5/2017 10:56 PM, Anantha Raghava wrote: > > Hello James, > > To your questions: > > *"Are DC1 and DC2 in the same geographical location?"* > > Yes, they are in same location, & they are in the same subnet as well. > > *"I'm also unclear from your message if you are still having password > issues or not."* > > **It appears

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 :

On 26/05/15 12:51, Stephan Mattecka wrote: >> Gesendet: Dienstag, 26. Mai 2015 um 13:31 Uhr >> Von: "Rowland Penny" <rowlandpenny at googlemail.com> >> An: "Stephan Mattecka" <ste-fun_s at gmx.de> >> Cc: samba at lists.samba.org >> Betreff: Re: Aw: Re: [Samba] [SAMBA] Problems with joining a second DC to AD >> >> On 26/05/15

Being a newbie to Samba 4 and OpenLDAP I am setting up a DC going exactly by the rules, testing and taking my time. I got to the point where I would switch, just testing, roles from DC1 to DC2 and vice versa. Switching all roles from DC1 to DC2 was a piece of cake, reswitching "domaindns" and "forestdns" to DC1 wasn't, though: samba-tool fsmo transfer --role=domaindns -k

Hi Guys, I have run into a very interesting problem using GPO's on our DC's. As you may (or may not) know, we have migrated to a pure Samba4 (Git stable branch checkout) AD network. I can't be happier. *Kudos to the Samba team* We are running to DC's, DC1 and DC2, both full fledged DC's, both running CentOS 6.9, fully up to date. For the sysvol partition I decided to run a

On 26/05/15 10:42, Stephan Mattecka wrote: > Gesendet: Donnerstag, 21. Mai 2015 um 19:06 Uhr > Von: "Rowland Penny" <rowlandpenny at googlemail.com> > An: samba at lists.samba.org > Betreff: Re: [Samba] [SAMBA] Problems with joining a second DC to AD > On 21/05/15 17:41, Stephan Mattecka wrote: >> Hi Rowland and Louis, >> >> I did try both of your

Looking at you config setup, i noticed a few things.   DC1. /etc/resolv.conf domain empresa.com.br search empresa.com.br nameserver 192.168.200.25   (=dc1) nameserver 192.168.200.10   /etc/resolv.conf domain empresa.com.br search empresa.com.br nameserver 192.168.200.4   (dc=2) nameserver 192.168.200.10     /etc/resolv.conf domain empresa.com.br search empresa.com.br nameserver

On Fri, 15 Dec 2017 13:16:51 -0600 Taylor Hammerling <thammerling at tcsbasys.com> wrote: > ok, I followed the directions on that wikipage, made a hot backup, > copied the hot backup over to the new DC, renamed the hot backup > (thus replacing the existing idmap.ldb) and ran "samba-tool ntacl > sysvolreset" and it spat out the following after a minute or 2 of >

Hello James, To your questions: *"Are DC1 and DC2 in the same geographical location?"* Yes, they are in same location, & they are in the same subnet as well. *"I'm also unclear from your message if you are still having password issues or not."* **It appears to have been resolved. When we randomly checked, users were able to change their passwords. However

Thanks. I sync sysvol every hour 9-5 and idmap daily. I do not edit or create GPOs often so I guess that?s enough. I wanted to make sure I had this article right : http://samba.bigbird.es/doku.php?id=samba:sync-idmap.ldb All the best. On 19 Oct 2023 at 15:31 +0200, bd730c5053df9efb <bd730c5053df9efb at proton.me>, wrote: > > I forgot to add in my original response that this

Hi all, We seem to have some issues with our samba4 ad setup. I posted about this last week already but had received no replies at all so far. :-( What is our situation: two domain controllers (dc1 and dc2), one (separate) fileserver, all running sernet-4.1.7. From the workstations perspective, everything is running as it should, there appear to be no issues. However: something in my

On 23 November 2017 at 14:16, Rowland Penny <rpenny at samba.org> wrote: > On Thu, 23 Nov 2017 14:01:03 +0200 > Ian Coetzee via samba <samba at lists.samba.org> wrote: > > > On 22 November 2017 at 17:45, Rowland Penny <rpenny at samba.org> wrote: > > > > > On Wed, 22 Nov 2017 16:01:17 +0200 > > > Ian Coetzee via samba <samba at

Hello James, Even after setting the rfc2307 in smb.conf replication error continues and password change error continues. Error thrown while forcing replication is shown below. ------------------------------------------------------------------- Even after setting RFC, DC2 is not getting synced from DC1. Connection time out error comes. #samba-tool drs replicate DC2.KTKBANKLTD.COM

LP On Nov 7, 2023 at 18:06 +0100, Andrey Repin via samba <samba at lists.samba.org>, wrote: > > > AD DC configuration: > > # Global parameters > [global] > auto services = homes > client ldap sasl wrapping = sign > dns forwarder = 192.168.1.12 > dos charset = CP866 > logging = systemd > log level = 1 > netbios name = DC2 > panic action =

Hi, I tried to replicate two DC's (on test setup) with "--full-sync" option but fails with error message below. I tried "--full-sync" because I wonder if it has any effect on some diverged entries reported by "samba-tool ldapcmp". # samba-tool drs replicate dc1 dc2 --full-sync DC=samdom,DC=com ERROR(<class 'samba.drs_utils.drsException'>): DRS