similar to: Replication with Multiple Sites in a Hub and Spoke Topology

Hi, It seems unlikely that the KCC is the cause of these issues. The KCC is only responsible for telling who to connect (and when) and doesn't actually affect any underlying network connectivity. Connectivity between the spokes should not be required and the communication between them is usually just some stale data. But none of that should affect either of these commands. Unless the DRS

Hi list, I'm running into issues with Samba 4.5.16-Debian. I am trying to get 3 DCs to talk to each other and replicate. DC1 and DC3 are on the same subnet; DC2 is on another subnet, accessible by IP. Currently, no firewalls on any of the DCs. Issue 1 - When I run "samba-tool drs showrepl", I get various results: DC1 - Failed to bind to uuid e3514235-4b06-11d1-ab04-00c04fc2dcd2

On Sun, Dec 18, 2016 at 5:20 PM, Garming Sam <garming at catalyst.net.nz> wrote: > Hi, > > It seems unlikely that the KCC is the cause of these issues. The KCC is > only responsible for telling who to connect (and when) and doesn't > actually affect any underlying network connectivity. Connectivity > between the spokes should not be required and the communication

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 :

I have two DC with Samba 4.2.1 and now I have set up a third DC with Samba 4.6.3. I have executed the command: samba-tool domain join empresa.com.br DC -U "EMPRESA\administrator" --dns-backend = SAMBA_INTERNAL And everything went well, however with the command: samba-tool drs showrepl The following message appears: root at dc3:/home/marcio# /usr/local/samba/bin/samba-tool drs

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

Hello, I've having recurring issues with the second DC in my Samba AD domain. I've demoted/removed the second DC a number of times and re-provisioned it. It'll work for a bit and then replication breaks. Since replication is broken I've been doing the following to remove it: DC-02 systemctl stop samba systemctl disable samba DC-01 samba-tool domain demote

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

Hello, I set up a domain with two DCs (dns-backend is BIND9_DLZ) on a Debian 10 system. I used either the Debian-packages or the Packages from Louis (4.12.8). I created an Ansible-role to setup everything, starting from installing the packages over doing the provision/join up to change the settings for bind9. The first DC runs fine. After the reboot services are all present, allthe SRV Record for

I removed a DC using the DC removal tool mentioned in http://gallery.technet.microsoft.com/scriptcenter/d31f091f-2642-4ede-9f97-0e1cc4d577f3 as https://bugzilla.samba.org/show_bug.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

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

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

yes i realized that there is something wrong with BIND9_FLATFILE while encountering with samba_upgradedns -h which doesn't show BIND9_FLATFILE Any help on*drs repl* not working i think it is pointing to wrong FQDN how do i correct that ? > >/ Not able to to view replication.(samba-tool drs showrepl) > />/ > />/ > />/ [root at dc2

Dear All, Need some help as I was trying to follow the guide below. https://wiki.samba.org/index.php/Samba4/HOWTO/Join_a_domain_as_a_DC Until the steps of ldbsearch -H /usr/local/samba/private/sam.ldb '(invocationid=*)' --cross-ncs objectguid and my ldbsearch reply with such a result. ldb: unable to dlopen /usr/lib64/samba/ldb/acl.so : /usr/lib64/ldb/libreplace.so: version

Hi there. I'm trying to upgrad from 4.7.7 to 4.9.4. I built from source, running on centos 7.6 on a Raspberry Pi. When testing on a secondary DC, my "samba-tool drs showrepl" errors out with: ERROR(<class 'samba.drs_utils.drsException'>): DRS connection to dc02.rvx.is > failed - drsException: DRS connection to dc02.rvx.is failed: (8, >

So a little background, in my domain we have 2 domain controllers, the main (A Windows Server 2008 R2), and a secondary that is was recently migrated from Server 2003 R2 to Samba. Both domain controllers are offsite so we use OpenVpn to connect them, dns is set to the samba domain controller then the Windows server, this is due that the samba domain controller is up 24/7 while the Windows is only

Hi all, So we have a single AD-DC master, and I'm trying to join a fresh new DC (DOMAIN-ad.DOMAIN.intranet, 192.168.0.11) to the master (ad.DOMAIN.intranet, 192.168.0.17), and I'm using the HOWTO here: https://wiki.samba.org/index.php/Joining_a_Samba_DC_to_an_Existing_Active_Directory and I've hit a problem in the section "Built-in User & Group ID Mappings" - when

Hi, i upgrade to sles sp1 with sernet packages and get the following error after upgrade. Its looks like that port 135 will not reached. Anyone who have an information about that or a solution? Thanks Sven orion:~ # samba-tool drs showrepl Failed to connect host 192.168.24.2 on port 135 - NT_STATUS_CONNECTION_REFUSED Failed to connect host 192.168.24.2 (orion.domain.local) on port 135 -

Hello. We're trying to integrate Samba 4 as a DC in production. We aim to replace our only Windows 2003 Enterprise R2 Russian DC with 2 Samba DCs. However, we've got a replication problem, we aren't shure is it a bug or misconfiguration. Both Windows and Samba DCs are virtual amd64 machines, running under the control of Xen (so, at least the time is the same). Windows VM has GPLPV

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.