similar to: WERR_SEM_TIMEOUT

Am 23.01.2017 um 12:59 schrieb Carlos A. P. Cunha via samba: > Em 20-01-2017 18:19, Carlos A. P. Cunha escreveu: >> >> Hello >> I have about 10 Dcs Samba 4.4.4 running on Debian 8, in distinct >> networks, one of them presents the error: >> >> Result 121 (WERR_SEM_TIMEOUT) >> >> When I execute the command to check the DRS. >> >> Any

Hello! Comando is: samba-tool drs showrepl Debug 5 out of one of DC with problems ... array: struct drsuapi_DsReplicaNeighbour naming_context_dn : * naming_context_dn : 'DC=DomainDnsZones,DC=grupo,DC=XXX,DC=com,DC=br' source_dsa_obj_dn : *

Hehe Sorry for the lack of information .... Follow: ------------------------------------------- Dc133 [global] workgroup = <NAME> realm = grupo.<DOMAIN> netbios name = dc133 server role = active directory domain controller passdb backend = samba_dsdb server services = s3fs, rpc, nbt, wrepl, ldap, cldap, kdc, drepl, winbindd,

I tried to synchronize the sysvol folders, on two dcs. Something went wrong since yesterday we have replication problems: One machine shows this, while the other one is happy. samba-tool drs showrepl ==== INBOUND NEIGHBORS ==== DC=DomainDnsZones,DC=ourdomain,DC=com Default-First-Site-Name\DC03 via RPC DSA object GUID: af610e1a-9e3b-4cdd-a36b-c296d77a9479 Last attempt @

Hello !! Yes, I noticed this (and it called me too), but as it has about 10 Dc and with some it is talking the data in it are integral, but for some DCs is generating me this error ..... UPDATE: I updated the DC that has this error for several to version 4.5.4, but problem still persists .... Em 23-01-2017 19:30, Rowland Penny escreveu: > On Mon, 23 Jan 2017 18:59:47 -0200 >

Hi Carlos, If you were running "samba-tool drs showrepl", It seems like this bug could be the issue: https://bugzilla.samba.org/show_bug.cgi?id=11929 Which was encountered here: https://lists.samba.org/archive/samba/2015-March/190423.html Thanks, Bob On 24/01/17 08:59, Carlos A. P. Cunha via samba wrote: > Hello! > I removed these lines, restart samba / bind and still get

On Mon, 23 Jan 2017 16:38:00 -0200 "Carlos A. P. Cunha via samba" <samba at lists.samba.org> wrote: > Hehe Sorry for the lack of information .... > > Follow: > > ------------------------------------------- > > Dc133 > > [global] > workgroup = <NAME> > realm = grupo.<DOMAIN> > netbios name = dc133 >

Hi, I performed the procedures below on Samba4-DC1 (Master) and apparently everything went fine. /etc/init.d/samba-ad-dc stop sed -i -e 's/${DOMAINDN}/DC=empresa,DC=com,DC=br/g' \ -e 's/${NETBIOSNAME}/SAMBA4-DC1/g' \ -e 's/${NISDOMAIN}/empresa/g' \ /tmp/ypServ30.ldif root at samba4-dc1:/tmp# ldbmodify -H /var/lib/samba/private/sam.ldb

Hi all, I've been having DNS issues for about 3 months which is causing all sorts of weird problems (most things work fine but then we have days where random machines lose trust/can't login without un-joining and rejoining the domain). The domain was working with no problems for nearly 5 months before this started happening. I have Ubuntu 14.04 running Samba 4.1.6 using the internal

On Mon, 23 Jan 2017 18:59:47 -0200 "Carlos A. P. Cunha via samba" <samba at lists.samba.org> wrote: > Hello! > > Comando is: > > samba-tool drs showrepl > > Debug 5 out of one of DC with problems ... > > array: struct drsuapi_DsReplicaNeighbour > naming_context_dn : * >

HI, after update my DC(with fsmo) the replication is not work. 1° - Update DC2, replication OK 2° - Update DC(FSMo), replication error DC(FSMO) -> DC2 -> OK DC2 -> DC(FSMo) -> ERRO Erro information in "samba-tool  drs showrepl" result 121 (WERR_SEM_TIMEOUT) Any Ideia ? Samba 4.7.6 . Regards; On 20-03-2018 09:51, Carlos wrote: > > Hi, > > Thank you all

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, I have replications problems on one of my server. Replication was working since month and yet stopped working. on the remote server: islad01:~ # samba-tool drs showrepl | more Default-First-Site-Name\ISLAD01 DSA Options: 0x00000001 DSA object GUID: 3fe6bc7c-1116-4344-96a6-c58c43bc217f DSA invocationId: 89351eec-7207-45f5-b6b9-cebfcacfd0e3 ==== INBOUND NEIGHBORS ====

2015-03-27 14:00 GMT-04:00 <samba-request at lists.samba.org>: > Send samba mailing list submissions to > samba at lists.samba.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.samba.org/mailman/listinfo/samba > or, via email, send a message with subject or body 'help' to > samba-request at lists.samba.org

Found the problem. There is a DNS Problem on one machine. This happend because I was testing some samba AD settings in a virtual machine, without knowing that NAT isn't shielding this properly - this vm propagated the "new" IP to one of the dcs. DC04> ping DC03 gives wrong IP! This should be fixable with the samba-tool dns update? On 03/27/2015 01:14 PM, Johannes Amorosa |

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 at gmail.com> wrote: > > Hi, > I have same problem after update for samba. > I allow new ports in firewall. > >

On 24/03/18 01:35, lingpanda101 wrote: > On 3/22/2018 8:06 PM, David Minard wrote: >> G'day All, >> >>     Will replay to all messages so far in this one to keep it all >> together. >> >> On 21/03/18 22:52, lingpanda101 wrote: >>> On 3/21/2018 7:32 AM, David Minard via samba wrote: >>>> Thanks Carlos, >>>>

G'day All, Will replay to all messages so far in this one to keep it all together. On 21/03/18 22:52, lingpanda101 wrote: > 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.

Hello, Joined a new samba 4 dc to an existing pair of samba 4 domain controllers, but i have a problem with replication. 5-10 minutes after starting samba services on the new samba 4 server, both dns servers on the old Domain controllers freeze. Nothing works. all i can do is to kill all the services (ntp,named,samba) and start over again. i get this message on new dc in this file:

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. >