Re: [Samba] Replication Failure Issue

[lingpanda101 via samba <samba@xxxxxxxxxxxxxxx>]

On 3/21/2018 7:32 AM, David Minard via samba wrote:
> Thanks Carlos,
>
> The thing is, that I did not upgrade the version of Samba - that is the next step, so the ports used would not have changed. I only updated the OS.
>
>
> > On 21/03/2018, at 10:04 PM, Carlos Alberto Panozzo Cunha <carlos.hollow@xxxxxxxxx> wrote:
> >
> > Hi,
> > I have same problem after update for samba.
> > I allow new ports in firewall.
> >
> > https://wiki.samba.org/index.php/Samba_AD_DC_Port_Usage
> >
> > Regards
> >
> >
> > On Wed, Mar 21, 2018, 00:15 David Minard via samba <samba@xxxxxxxxxxxxxxx> wrote:
> > G'day All,
> >
> >          I have 4 DCs on Centos 7.1. Everything was working really well for
> > years, including replication.
> >
> >          Then I decided that the OS needed updating. Did the yum update on one
> > of the DCs, rebooted. That server is now running Centos 7.4. Samba
> > seemed to start okay.
> >
> >          However, samba-tool drs showrepl gives this error on all 3 of the other
> > DCs, and shows success on the updated DC.
> >
> > DC=DomainDnsZones,DC=samba4,DC=scem,DC=westernsydney,DC=edu,DC=au
> >          Default-First-Site-Name\SAMBA4-10 via RPC
> >                  DSA object GUID: 7fa7fc88-8d99-4217-b329-7e82324ec084
> >
> >                  Last attempt @ Wed Mar 21 12:58:13 2018 AEDT failed, result 58
> > (WERR_BAD_NET_RESP)
> >
> >                  10623 consecutive failure(s).
> >                  Last success @ Thu Mar  8 14:34:14 2018 AEDT
> >
> >
> >          Any thoughts on why this DC is now not replicating properly? Any
> > thoughts on how to remedy this?
> >
> >
> > --
> >
> > Cheers,
> > David Minard.
> > Ph:    0247 360 155
> > Fax:    0247 360 770
> >
> > ITDS - ACE - SSTaRS
> > Western Sydney University
> > Building Y - Penrith Campus (Kingswood)
> > Locked bag 1797
> > Penrith NSW 2751
> >
> > [Sometimes waking up just isn't worth the insult of the day to come.]
> >
> > --
> > This message has been scanned for viruses and
> > dangerous content by MailScanner, and is
> > believed to be clean.
> >
> >
> > --
> > To unsubscribe from this list go to the following URL and read the
> > instructions:  https://lists.samba.org/mailman/options/samba
> >
> > --
> > This message has been scanned for viruses and
> > dangerous content by MailScanner, and is
> > believed to be clean.
>
> Cheers,
> David Minard.
> Ph:    0247 360 155
> Fax:    0247 360 770
>
> School of Computing, Engineering, and Mathematics
> Building Y - Penrith Campus (Kingswood)
> Locked bag 1797
> Penrith South DC
> NSW 1797
>
> [Sometimes waking up just isn't worth the insult of the day to come.]
You most likely will need to turn up the samba log level to get 
additional information but you can start with running 'yum history list 
all' and post results. This might help identify the changes that were 
made to the OS. Are you using bind or the internal DNS?


--
--
James


--
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba