Samba 4.3.0 sync issues between DCs

bogdan_bartos admin at
Sun Sep 27 16:54:43 UTC 2015


I have 2 DCs running on samba 4.3.0 on Fedora 22 x64. Whenever I add a new
machine, or user, or make a change (password change in this case). the DC
that senses first the change is the one that does not have the FSMO roles
on. The issue is that the change does not propagate onto the FSMO DC.
However, if that DC is down or stopped, the FSMO DC makes the changes and
the changes propagate in this case, but not the other way around.

The issue has been ongoing with previuos versions of Samba4, os it must be
something in the config or provisioning that is causing this. I also tried
to demote the server that does not hold the FSMO roles and I get lots of
errors.I have the same ports open on both servers. What is causing this

The ports open are the following:
  <port protocol="tcp" port="53"/>
  <port protocol="udp" port="53"/>
  <port protocol="tcp" port="88"/>
  <port protocol="udp" port="88"/>
  <port protocol="tcp" port="135"/>
  <port protocol="udp" port="137"/>
  <port protocol="udp" port="138"/>
  <port protocol="tcp" port="139"/>
  <port protocol="tcp" port="389"/>
  <port protocol="udp" port="389"/>
  <port protocol="tcp" port="445"/>
  <port protocol="tcp" port="464"/>
  <port protocol="udp" port="464"/>
  <port protocol="tcp" port="636"/>
  <port protocol="tcp" port="1024"/>
  <port protocol="tcp" port="3268"/>
  <port protocol="tcp" port="3269"/>
  <port protocol="tcp" port="5353"/>
  <port protocol="udp" port="5353"/>

View this message in context:
Sent from the Samba - samba-technical mailing list archive at

More information about the samba-technical mailing list