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
/tmp/ypServ30.ldif --option="dsdb:schema update allowed"=true
Modified 55 records successfully
/etc/init.d/samba-ad-dc start
ldbsearch -H /var/lib/samba/private/sam.ldb -s base -b
CN=ypservers,CN=ypServ30,CN=RpcServices,CN=System,DC=empresa,DC=com,DC=br cn
# record 1
dn:
CN=ypservers,CN=ypServ30,CN=RpcServices,CN=System,DC=empresa,DC=com,DC=br
cn: ypservers
# returned 1 records
# 1 entries
# 0 referrals
However I noticed that an error arose in replication with Samba4-DC2, as
follows:
samba-tool drs showrepl
...
CN=Schema,CN=Configuration,DC=empresa,DC=com,DC=br
Default-First-Site-Name\SAMBA4-DC2 via RPC
DSA object GUID: 45b5b534-9bcc-483c-8f6d-5bbc37dc35e9
Last attempt @ Mon Aug 19 22:28:59 2019 -03 failed, result
64 (WERR_NETNAME_DELETED)
1 consecutive failure(s).
Last success @ Mon Aug 19 22:07:23 2019 -03
How can I solve this problem?
Regards,
M?rcio Bacci
Em seg, 19 de ago de 2019 ?s 18:05, Rowland penny via samba <
samba at lists.samba.org> escreveu:
> On 19/08/2019 21:45, Marcio Demetrio Bacci wrote:
> > Hi,
> >
> > >Ah, I think I see the problem, If I remember correctly, you joined
the
> > >the Samba DC to a Windows DC and if you didn't have IDMU
installed on
> > >the Windows DC, you wouldn't get the required objects in AD
created on
> > >the Samba DC either.
> >
> > Really, IDMU was not installed.
> >
> >
> > There is the file ypServ30.ldif
> > ls /usr/share/samba/setup/
> > ...
> > ypServ30.ldif
> >
> > But, I believe the extension is not enabled:
> >
> > ldbsearch -H /var/lib/samba/private/sam.ldb -s base -b
> >
> CN=ypservers,CN=ypServ30,CN=RpcServices,CN=System,DC=empresa,DC=com,DC=br
> > cn
> > search error - No such Base DN:
> >
CN=ypservers,CN=ypServ30,CN=RpcServices,CN=System,DC=empresa,DC=com,DC=br
> >
> >
> > This way, Do I need to install NIS (apt-get install nis) or only
> > Replace the variables in LDIF file with the domain distinguished name
> > (DN), NetBIOS name, and the NIS domain ?
>
> No, yes, yes and sort of ;-)
>
> No, you do not install NIS
>
> Yes, you replace '${DOMAINDN}' with
'DC=empresa,DC=com,DC=br'
>
> Yes, you replace '${NETBIOSNAME}' with the DCs short hostname in
uppercase
>
> You replace '${NISDOMAIN}' (that is a bad name) with the workgroup
name
> in lowercase.
>
> ypServ30.ldif is what installing IDMU on a Windows adds to AD and is
> normally only added to Samba if you provision a new domain with
> '--use-rfc2307'
>
> Rowland
>
>
> --
> To unsubscribe from this list go to the following URL and read the
> instructions: https://lists.samba.org/mailman/options/samba
>
On 20/08/2019 02:59, Marcio Demetrio Bacci wrote:> 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 > /tmp/ypServ30.ldif --option="dsdb:schema update allowed"=true > Modified 55 records successfully > > /etc/init.d/samba-ad-dc start > > ldbsearch -H /var/lib/samba/private/sam.ldb -s base -b > CN=ypservers,CN=ypServ30,CN=RpcServices,CN=System,DC=empresa,DC=com,DC=br > cn > # record 1 > dn: > CN=ypservers,CN=ypServ30,CN=RpcServices,CN=System,DC=empresa,DC=com,DC=br > cn: ypservers > > # returned 1 records > # 1 entries > # 0 referrals > > > However I noticed that an error arose in replication with Samba4-DC2, > as follows: > > samba-tool drs showrepl > ... > CN=Schema,CN=Configuration,DC=empresa,DC=com,DC=br > ? ? ? ? Default-First-Site-Name\SAMBA4-DC2 via RPC > ? ? ? ? ? ? ? ? DSA object GUID: 45b5b534-9bcc-483c-8f6d-5bbc37dc35e9 > ? ? ? ? ? ? ? ? Last attempt @ Mon Aug 19 22:28:59 2019 -03 failed, > result 64 (WERR_NETNAME_DELETED) > ? ? ? ? ? ? ? ? 1 consecutive failure(s). > ? ? ? ? ? ? ? ? Last success @ Mon Aug 19 22:07:23 2019 -03 > > > How can I solve this problem?You could try forcing replication with: samba-tool drs replicate <destinationDC> <sourceDC> <NC> Where <destinationDC> & <sourceDC> are in the format 'ldap://DC_HOSTNAME' and <NC> is the Naming Context, I woukd start with 'domain' See: samba-tool drs replicate --help For more info. Rowland
Hi,
I have noticed that at night the DC synced.
However sometimes the samba-tool drs showrepl command takes a long time to
display the results, I don't know if is because the DC Windows Server 2008
that has been down for 4 days. I plan to demote this Windows server today.
root at samba4-dc1:~# samba-tool drs showrepl
Default-First-Site-Name\SAMBA4-DC1
DSA Options: 0x00000001
DSA object GUID: a1ab021c-0ef7-4fd3-a69d-28afc7c1260a
DSA invocationId: a20c8ed0-c72a-4e57-9e59-2236f127d0b8
==== INBOUND NEIGHBORS ===
DC=ForestDnsZones,DC=empresa,DC=com,DC=br
Default-First-Site-Name\WIN-DC3 via RPC
DSA object GUID: d580939f-a8b9-43ea-84e9-be0f9bd29468
Last attempt @ Tue Aug 20 06:23:56 2019 -03 failed, result
121 (WERR_SEM_TIMEOUT)
993 consecutive failure(s).
Last success @ Fri Aug 16 13:38:20 2019 -03
DC=ForestDnsZones,DC=empresa,DC=com,DC=br
Default-First-Site-Name\SAMBA4-DC2 via RPC
DSA object GUID: 45b5b534-9bcc-483c-8f6d-5bbc37dc35e9
Last attempt @ Tue Aug 20 06:23:56 2019 -03 was successful
0 consecutive failure(s).
Last success @ Tue Aug 20 06:23:56 2019 -03
CN=Configuration,DC=empresa,DC=com,DC=br
Default-First-Site-Name\WIN-DC3 via RPC
DSA object GUID: d580939f-a8b9-43ea-84e9-be0f9bd29468
Last attempt @ Tue Aug 20 06:25:56 2019 -03 failed, result
121 (WERR_SEM_TIMEOUT)
989 consecutive failure(s).
Last success @ Fri Aug 16 13:38:20 2019 -03
CN=Configuration,DC=empresa,DC=com,DC=br
Default-First-Site-Name\SAMBA4-DC2 via RPC
DSA object GUID: 45b5b534-9bcc-483c-8f6d-5bbc37dc35e9
Last attempt @ Tue Aug 20 06:25:57 2019 -03 was successful
0 consecutive failure(s).
Last success @ Tue Aug 20 06:25:57 2019 -03
DC=DomainDnsZones,DC=empresa,DC=com,DC=br
Default-First-Site-Name\WIN-DC3 via RPC
DSA object GUID: d580939f-a8b9-43ea-84e9-be0f9bd29468
Last attempt @ Tue Aug 20 06:24:56 2019 -03 failed, result
121 (WERR_SEM_TIMEOUT)
990 consecutive failure(s).
Last success @ Fri Aug 16 13:38:20 2019 -03
DC=DomainDnsZones,DC=empresa,DC=com,DC=br
Default-First-Site-Name\SAMBA4-DC2 via RPC
DSA object GUID: 45b5b534-9bcc-483c-8f6d-5bbc37dc35e9
Last attempt @ Tue Aug 20 06:24:56 2019 -03 was successful
0 consecutive failure(s).
Last success @ Tue Aug 20 06:24:56 2019 -03
CN=Schema,CN=Configuration,DC=empresa,DC=com,DC=br
Default-First-Site-Name\WIN-DC3 via RPC
DSA object GUID: d580939f-a8b9-43ea-84e9-be0f9bd29468
Last attempt @ Tue Aug 20 06:21:56 2019 -03 failed, result
121 (WERR_SEM_TIMEOUT)
985 consecutive failure(s).
Last success @ Fri Aug 16 13:38:20 2019 -03
CN=Schema,CN=Configuration,DC=empresa,DC=com,DC=br
Default-First-Site-Name\SAMBA4-DC2 via RPC
DSA object GUID: 45b5b534-9bcc-483c-8f6d-5bbc37dc35e9
Last attempt @ Tue Aug 20 06:21:56 2019 -03 was successful
0 consecutive failure(s).
Last success @ Tue Aug 20 06:21:56 2019 -03
DC=empresa,DC=com,DC=br
Default-First-Site-Name\WIN-DC3 via RPC
DSA object GUID: d580939f-a8b9-43ea-84e9-be0f9bd29468
Last attempt @ Tue Aug 20 06:22:56 2019 -03 failed, result
121 (WERR_SEM_TIMEOUT)
983 consecutive failure(s).
Last success @ Fri Aug 16 13:39:32 2019 -03
DC=empresa,DC=com,DC=br
Default-First-Site-Name\SAMBA4-DC2 via RPC
DSA object GUID: 45b5b534-9bcc-483c-8f6d-5bbc37dc35e9
Last attempt @ Tue Aug 20 06:22:56 2019 -03 was successful
0 consecutive failure(s).
Last success @ Tue Aug 20 06:22:56 2019 -03
==== OUTBOUND NEIGHBORS ===
DC=ForestDnsZones,DC=empresa,DC=com,DC=br
Default-First-Site-Name\WIN-DC3 via RPC
DSA object GUID: d580939f-a8b9-43ea-84e9-be0f9bd29468
Last attempt @ Tue Aug 20 06:11:40 2019 -03 failed, result
121 (WERR_SEM_TIMEOUT)
177 consecutive failure(s).
Last success @ Fri Aug 16 01:08:09 2019 -03
DC=ForestDnsZones,DC=empresa,DC=com,DC=br
Default-First-Site-Name\SAMBA4-DC2 via RPC
DSA object GUID: 45b5b534-9bcc-483c-8f6d-5bbc37dc35e9
Last attempt @ NTTIME(0) was successful
0 consecutive failure(s).
Last success @ NTTIME(0)
CN=Configuration,DC=empresa,DC=com,DC=br
Default-First-Site-Name\WIN-DC3 via RPC
DSA object GUID: d580939f-a8b9-43ea-84e9-be0f9bd29468
Last attempt @ Tue Aug 20 05:56:29 2019 -03 failed, result
121 (WERR_SEM_TIMEOUT)
171 consecutive failure(s).
Last success @ Fri Aug 16 11:43:03 2019 -03
CN=Configuration,DC=empresa,DC=com,DC=br
Default-First-Site-Name\SAMBA4-DC2 via RPC
DSA object GUID: 45b5b534-9bcc-483c-8f6d-5bbc37dc35e9
Last attempt @ NTTIME(0) was successful
0 consecutive failure(s).
Last success @ NTTIME(0)
DC=DomainDnsZones,DC=empresa,DC=com,DC=br
Default-First-Site-Name\WIN-DC3 via RPC
DSA object GUID: d580939f-a8b9-43ea-84e9-be0f9bd29468
Last attempt @ Tue Aug 20 06:18:56 2019 -03 failed, result
121 (WERR_SEM_TIMEOUT)
217 consecutive failure(s).
Last success @ Fri Aug 16 13:37:53 2019 -03
DC=DomainDnsZones,DC=empresa,DC=com,DC=br
Default-First-Site-Name\SAMBA4-DC2 via RPC
DSA object GUID: 45b5b534-9bcc-483c-8f6d-5bbc37dc35e9
Last attempt @ NTTIME(0) was successful
0 consecutive failure(s).
Last success @ NTTIME(0)
CN=Schema,CN=Configuration,DC=empresa,DC=com,DC=br
Default-First-Site-Name\WIN-DC3 via RPC
DSA object GUID: d580939f-a8b9-43ea-84e9-be0f9bd29468
Last attempt @ Tue Aug 20 06:01:30 2019 -03 failed, result
121 (WERR_SEM_TIMEOUT)
166 consecutive failure(s).
Last success @ Fri Aug 16 01:08:09 2019 -03
CN=Schema,CN=Configuration,DC=empresa,DC=com,DC=br
Default-First-Site-Name\SAMBA4-DC2 via RPC
DSA object GUID: 45b5b534-9bcc-483c-8f6d-5bbc37dc35e9
Last attempt @ NTTIME(0) was successful
0 consecutive failure(s).
Last success @ NTTIME(0)
DC=empresa,DC=com,DC=br
Default-First-Site-Name\WIN-DC3 via RPC
DSA object GUID: d580939f-a8b9-43ea-84e9-be0f9bd29468
Last attempt @ Tue Aug 20 06:06:35 2019 -03 failed, result
121 (WERR_SEM_TIMEOUT)
198 consecutive failure(s).
Last success @ Fri Aug 16 13:09:55 2019 -03
DC=empresa,DC=com,DC=br
Default-First-Site-Name\SAMBA4-DC2 via RPC
DSA object GUID: 45b5b534-9bcc-483c-8f6d-5bbc37dc35e9
Last attempt @ NTTIME(0) was successful
0 consecutive failure(s).
Last success @ NTTIME(0)
==== KCC CONNECTION OBJECTS ===
Connection --
Connection name: c6393fbd-461c-4fd7-ac62-4801a3de43d2
Enabled : TRUE
Server DNS name : win-dc3.empresa.com.br
Server DN name : CN=NTDS
Settings,CN=WIN-DC3,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=empresa,DC=com,DC=br
TransportType: RPC
options: 0x00000001
Warning: No NC replicated for Connection!
Connection --
Connection name: 4d807638-61ef-4f9e-843b-d8928dd44263
Enabled : TRUE
Server DNS name : samba4-dc2.empresa.com.br
Server DN name : CN=NTDS
Settings,CN=SAMBA4-DC2,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=empresa,DC=com,DC=br
TransportType: RPC
options: 0x00000001
Warning: No NC replicated for Connection!
The commands below have showed error:
root at samba4-dc1:~# samba-tool drs replicate SAMBA4-DC2 SAMBA4-DC1
CN=Schema,CN=Configuration,DC=empresa,DC=com,DC=br
ERROR(<class 'samba.drs_utils.drsException'>): DsReplicaSync
failed -
drsException: DsReplicaSync failed (-1073741643, '{Device Timeout} The
specified I/O operation on %hs was not completed before the time-out period
expired.')
File "/usr/lib/python2.7/dist-packages/samba/netcmd/drs.py", line
368, in
run
drs_utils.sendDsReplicaSync(server_bind, server_bind_handle,
source_dsa_guid, NC, req_options)
File "/usr/lib/python2.7/dist-packages/samba/drs_utils.py", line 83,
in
sendDsReplicaSync
raise drsException("DsReplicaSync failed %s" % estr)
root at samba4-dc1:~# samba-tool drs replicate SAMBA4-DC2 SAMBA4-DC1
DC=empresa,DC=com,DC=br
ERROR(<class 'samba.drs_utils.drsException'>): DsReplicaSync
failed -
drsException: DsReplicaSync failed (-1073741643, '{Device Timeout} The
specified I/O operation on %hs was not completed before the time-out period
expired.')
File "/usr/lib/python2.7/dist-packages/samba/netcmd/drs.py", line
368, in
run
drs_utils.sendDsReplicaSync(server_bind, server_bind_handle,
source_dsa_guid, NC, req_options)
File "/usr/lib/python2.7/dist-packages/samba/drs_utils.py", line 83,
in
sendDsReplicaSync
raise drsException("DsReplicaSync failed %s" % estr)
How could I solve this problem?
Regards,
M?rcio Bacci
Em ter, 20 de ago de 2019 ?s 04:46, Rowland penny via samba <
samba at lists.samba.org> escreveu:
> On 20/08/2019 02:59, Marcio Demetrio Bacci wrote:
> > 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
> > /tmp/ypServ30.ldif --option="dsdb:schema update
allowed"=true
> > Modified 55 records successfully
> >
> > /etc/init.d/samba-ad-dc start
> >
> > ldbsearch -H /var/lib/samba/private/sam.ldb -s base -b
> >
> CN=ypservers,CN=ypServ30,CN=RpcServices,CN=System,DC=empresa,DC=com,DC=br
> > cn
> > # record 1
> > dn:
> >
CN=ypservers,CN=ypServ30,CN=RpcServices,CN=System,DC=empresa,DC=com,DC=br
> > cn: ypservers
> >
> > # returned 1 records
> > # 1 entries
> > # 0 referrals
> >
> >
> > However I noticed that an error arose in replication with Samba4-DC2,
> > as follows:
> >
> > samba-tool drs showrepl
> > ...
> > CN=Schema,CN=Configuration,DC=empresa,DC=com,DC=br
> > Default-First-Site-Name\SAMBA4-DC2 via RPC
> > DSA object GUID: 45b5b534-9bcc-483c-8f6d-5bbc37dc35e9
> > Last attempt @ Mon Aug 19 22:28:59 2019 -03 failed,
> > result 64 (WERR_NETNAME_DELETED)
> > 1 consecutive failure(s).
> > Last success @ Mon Aug 19 22:07:23 2019 -03
> >
> >
> > How can I solve this problem?
>
> You could try forcing replication with: samba-tool drs replicate
> <destinationDC> <sourceDC> <NC>
>
> Where <destinationDC> & <sourceDC> are in the format
> 'ldap://DC_HOSTNAME' and <NC> is the Naming Context, I woukd
start with
> 'domain'
>
> See: samba-tool drs replicate --help
>
> For more info.
>
> Rowland
>
>
>
> --
> To unsubscribe from this list go to the following URL and read the
> instructions: https://lists.samba.org/mailman/options/samba
>
Since it looks good now, i suggest, before you go hunting down this : samba-tool drs replicate SAMBA4-DC2 SAMBA4-DC1 \ DC=empresa,DC=com,DC=br \ ERROR(<class 'samba.drs_utils.drsException'>): Remove the windows DC from the AD first. Above happend because of the existing record of the windows DC. Greetz, Louis> -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens > Marcio Demetrio Bacci via samba > Verzonden: dinsdag 20 augustus 2019 11:44 > Aan: Rowland penny > CC: sambalist > Onderwerp: Re: [Samba] Problems with NIS Server on Samba 4 > > Hi, > > I have noticed that at night the DC synced. > > However sometimes the samba-tool drs showrepl command takes a > long time to > display the results, I don't know if is because the DC > Windows Server 2008 > that has been down for 4 days. I plan to demote this Windows > server today. > > > root at samba4-dc1:~# samba-tool drs showrepl > Default-First-Site-Name\SAMBA4-DC1 > DSA Options: 0x00000001 > DSA object GUID: a1ab021c-0ef7-4fd3-a69d-28afc7c1260a > DSA invocationId: a20c8ed0-c72a-4e57-9e59-2236f127d0b8 > > ==== INBOUND NEIGHBORS ===> > DC=ForestDnsZones,DC=empresa,DC=com,DC=br > Default-First-Site-Name\WIN-DC3 via RPC > DSA object GUID: d580939f-a8b9-43ea-84e9-be0f9bd29468 > Last attempt @ Tue Aug 20 06:23:56 2019 -03 > failed, result > 121 (WERR_SEM_TIMEOUT) > 993 consecutive failure(s). > Last success @ Fri Aug 16 13:38:20 2019 -03 > > DC=ForestDnsZones,DC=empresa,DC=com,DC=br > Default-First-Site-Name\SAMBA4-DC2 via RPC > DSA object GUID: 45b5b534-9bcc-483c-8f6d-5bbc37dc35e9 > Last attempt @ Tue Aug 20 06:23:56 2019 -03 > was successful > 0 consecutive failure(s). > Last success @ Tue Aug 20 06:23:56 2019 -03 > > CN=Configuration,DC=empresa,DC=com,DC=br > Default-First-Site-Name\WIN-DC3 via RPC > DSA object GUID: d580939f-a8b9-43ea-84e9-be0f9bd29468 > Last attempt @ Tue Aug 20 06:25:56 2019 -03 > failed, result > 121 (WERR_SEM_TIMEOUT) > 989 consecutive failure(s). > Last success @ Fri Aug 16 13:38:20 2019 -03 > > CN=Configuration,DC=empresa,DC=com,DC=br > Default-First-Site-Name\SAMBA4-DC2 via RPC > DSA object GUID: 45b5b534-9bcc-483c-8f6d-5bbc37dc35e9 > Last attempt @ Tue Aug 20 06:25:57 2019 -03 > was successful > 0 consecutive failure(s). > Last success @ Tue Aug 20 06:25:57 2019 -03 > > DC=DomainDnsZones,DC=empresa,DC=com,DC=br > Default-First-Site-Name\WIN-DC3 via RPC > DSA object GUID: d580939f-a8b9-43ea-84e9-be0f9bd29468 > Last attempt @ Tue Aug 20 06:24:56 2019 -03 > failed, result > 121 (WERR_SEM_TIMEOUT) > 990 consecutive failure(s). > Last success @ Fri Aug 16 13:38:20 2019 -03 > > DC=DomainDnsZones,DC=empresa,DC=com,DC=br > Default-First-Site-Name\SAMBA4-DC2 via RPC > DSA object GUID: 45b5b534-9bcc-483c-8f6d-5bbc37dc35e9 > Last attempt @ Tue Aug 20 06:24:56 2019 -03 > was successful > 0 consecutive failure(s). > Last success @ Tue Aug 20 06:24:56 2019 -03 > > CN=Schema,CN=Configuration,DC=empresa,DC=com,DC=br > Default-First-Site-Name\WIN-DC3 via RPC > DSA object GUID: d580939f-a8b9-43ea-84e9-be0f9bd29468 > Last attempt @ Tue Aug 20 06:21:56 2019 -03 > failed, result > 121 (WERR_SEM_TIMEOUT) > 985 consecutive failure(s). > Last success @ Fri Aug 16 13:38:20 2019 -03 > > CN=Schema,CN=Configuration,DC=empresa,DC=com,DC=br > Default-First-Site-Name\SAMBA4-DC2 via RPC > DSA object GUID: 45b5b534-9bcc-483c-8f6d-5bbc37dc35e9 > Last attempt @ Tue Aug 20 06:21:56 2019 -03 > was successful > 0 consecutive failure(s). > Last success @ Tue Aug 20 06:21:56 2019 -03 > > DC=empresa,DC=com,DC=br > Default-First-Site-Name\WIN-DC3 via RPC > DSA object GUID: d580939f-a8b9-43ea-84e9-be0f9bd29468 > Last attempt @ Tue Aug 20 06:22:56 2019 -03 > failed, result > 121 (WERR_SEM_TIMEOUT) > 983 consecutive failure(s). > Last success @ Fri Aug 16 13:39:32 2019 -03 > > DC=empresa,DC=com,DC=br > Default-First-Site-Name\SAMBA4-DC2 via RPC > DSA object GUID: 45b5b534-9bcc-483c-8f6d-5bbc37dc35e9 > Last attempt @ Tue Aug 20 06:22:56 2019 -03 > was successful > 0 consecutive failure(s). > Last success @ Tue Aug 20 06:22:56 2019 -03 > > ==== OUTBOUND NEIGHBORS ===> > DC=ForestDnsZones,DC=empresa,DC=com,DC=br > Default-First-Site-Name\WIN-DC3 via RPC > DSA object GUID: d580939f-a8b9-43ea-84e9-be0f9bd29468 > Last attempt @ Tue Aug 20 06:11:40 2019 -03 > failed, result > 121 (WERR_SEM_TIMEOUT) > 177 consecutive failure(s). > Last success @ Fri Aug 16 01:08:09 2019 -03 > > DC=ForestDnsZones,DC=empresa,DC=com,DC=br > Default-First-Site-Name\SAMBA4-DC2 via RPC > DSA object GUID: 45b5b534-9bcc-483c-8f6d-5bbc37dc35e9 > Last attempt @ NTTIME(0) was successful > 0 consecutive failure(s). > Last success @ NTTIME(0) > > CN=Configuration,DC=empresa,DC=com,DC=br > Default-First-Site-Name\WIN-DC3 via RPC > DSA object GUID: d580939f-a8b9-43ea-84e9-be0f9bd29468 > Last attempt @ Tue Aug 20 05:56:29 2019 -03 > failed, result > 121 (WERR_SEM_TIMEOUT) > 171 consecutive failure(s). > Last success @ Fri Aug 16 11:43:03 2019 -03 > > CN=Configuration,DC=empresa,DC=com,DC=br > Default-First-Site-Name\SAMBA4-DC2 via RPC > DSA object GUID: 45b5b534-9bcc-483c-8f6d-5bbc37dc35e9 > Last attempt @ NTTIME(0) was successful > 0 consecutive failure(s). > Last success @ NTTIME(0) > > DC=DomainDnsZones,DC=empresa,DC=com,DC=br > Default-First-Site-Name\WIN-DC3 via RPC > DSA object GUID: d580939f-a8b9-43ea-84e9-be0f9bd29468 > Last attempt @ Tue Aug 20 06:18:56 2019 -03 > failed, result > 121 (WERR_SEM_TIMEOUT) > 217 consecutive failure(s). > Last success @ Fri Aug 16 13:37:53 2019 -03 > > DC=DomainDnsZones,DC=empresa,DC=com,DC=br > Default-First-Site-Name\SAMBA4-DC2 via RPC > DSA object GUID: 45b5b534-9bcc-483c-8f6d-5bbc37dc35e9 > Last attempt @ NTTIME(0) was successful > 0 consecutive failure(s). > Last success @ NTTIME(0) > > CN=Schema,CN=Configuration,DC=empresa,DC=com,DC=br > Default-First-Site-Name\WIN-DC3 via RPC > DSA object GUID: d580939f-a8b9-43ea-84e9-be0f9bd29468 > Last attempt @ Tue Aug 20 06:01:30 2019 -03 > failed, result > 121 (WERR_SEM_TIMEOUT) > 166 consecutive failure(s). > Last success @ Fri Aug 16 01:08:09 2019 -03 > > CN=Schema,CN=Configuration,DC=empresa,DC=com,DC=br > Default-First-Site-Name\SAMBA4-DC2 via RPC > DSA object GUID: 45b5b534-9bcc-483c-8f6d-5bbc37dc35e9 > Last attempt @ NTTIME(0) was successful > 0 consecutive failure(s). > Last success @ NTTIME(0) > > DC=empresa,DC=com,DC=br > Default-First-Site-Name\WIN-DC3 via RPC > DSA object GUID: d580939f-a8b9-43ea-84e9-be0f9bd29468 > Last attempt @ Tue Aug 20 06:06:35 2019 -03 > failed, result > 121 (WERR_SEM_TIMEOUT) > 198 consecutive failure(s). > Last success @ Fri Aug 16 13:09:55 2019 -03 > > DC=empresa,DC=com,DC=br > Default-First-Site-Name\SAMBA4-DC2 via RPC > DSA object GUID: 45b5b534-9bcc-483c-8f6d-5bbc37dc35e9 > Last attempt @ NTTIME(0) was successful > 0 consecutive failure(s). > Last success @ NTTIME(0) > > ==== KCC CONNECTION OBJECTS ===> > Connection -- > Connection name: c6393fbd-461c-4fd7-ac62-4801a3de43d2 > Enabled : TRUE > Server DNS name : win-dc3.empresa.com.br > Server DN name : CN=NTDS > Settings,CN=WIN-DC3,CN=Servers,CN=Default-First-Site-Name,CN=S > ites,CN=Configuration,DC=empresa,DC=com,DC=br > TransportType: RPC > options: 0x00000001 > Warning: No NC replicated for Connection! > Connection -- > Connection name: 4d807638-61ef-4f9e-843b-d8928dd44263 > Enabled : TRUE > Server DNS name : samba4-dc2.empresa.com.br > Server DN name : CN=NTDS > Settings,CN=SAMBA4-DC2,CN=Servers,CN=Default-First-Site-Name,C > N=Sites,CN=Configuration,DC=empresa,DC=com,DC=br > TransportType: RPC > options: 0x00000001 > Warning: No NC replicated for Connection! > > > The commands below have showed error: > > > root at samba4-dc1:~# samba-tool drs replicate SAMBA4-DC2 SAMBA4-DC1 > CN=Schema,CN=Configuration,DC=empresa,DC=com,DC=br > ERROR(<class 'samba.drs_utils.drsException'>): DsReplicaSync failed - > drsException: DsReplicaSync failed (-1073741643, '{Device Timeout} The > specified I/O operation on %hs was not completed before the > time-out period > expired.') > File > "/usr/lib/python2.7/dist-packages/samba/netcmd/drs.py", line 368, in > run > drs_utils.sendDsReplicaSync(server_bind, server_bind_handle, > source_dsa_guid, NC, req_options) > File "/usr/lib/python2.7/dist-packages/samba/drs_utils.py", > line 83, in > sendDsReplicaSync > raise drsException("DsReplicaSync failed %s" % estr) > > > > root at samba4-dc1:~# samba-tool drs replicate SAMBA4-DC2 SAMBA4-DC1 > DC=empresa,DC=com,DC=br > ERROR(<class 'samba.drs_utils.drsException'>): DsReplicaSync failed - > drsException: DsReplicaSync failed (-1073741643, '{Device Timeout} The > specified I/O operation on %hs was not completed before the > time-out period > expired.') > File > "/usr/lib/python2.7/dist-packages/samba/netcmd/drs.py", line 368, in > run > drs_utils.sendDsReplicaSync(server_bind, server_bind_handle, > source_dsa_guid, NC, req_options) > File "/usr/lib/python2.7/dist-packages/samba/drs_utils.py", > line 83, in > sendDsReplicaSync > raise drsException("DsReplicaSync failed %s" % estr) > > > How could I solve this problem? > > Regards, > > M?rcio Bacci > > Em ter, 20 de ago de 2019 ?s 04:46, Rowland penny via samba < > samba at lists.samba.org> escreveu: > > > On 20/08/2019 02:59, Marcio Demetrio Bacci wrote: > > > 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 > > > /tmp/ypServ30.ldif --option="dsdb:schema update allowed"=true > > > Modified 55 records successfully > > > > > > /etc/init.d/samba-ad-dc start > > > > > > ldbsearch -H /var/lib/samba/private/sam.ldb -s base -b > > > > > > CN=ypservers,CN=ypServ30,CN=RpcServices,CN=System,DC=empresa,D > C=com,DC=br > > > cn > > > # record 1 > > > dn: > > > > CN=ypservers,CN=ypServ30,CN=RpcServices,CN=System,DC=empresa,D > C=com,DC=br > > > cn: ypservers > > > > > > # returned 1 records > > > # 1 entries > > > # 0 referrals > > > > > > > > > However I noticed that an error arose in replication with > Samba4-DC2, > > > as follows: > > > > > > samba-tool drs showrepl > > > ... > > > CN=Schema,CN=Configuration,DC=empresa,DC=com,DC=br > > > Default-First-Site-Name\SAMBA4-DC2 via RPC > > > DSA object GUID: > 45b5b534-9bcc-483c-8f6d-5bbc37dc35e9 > > > Last attempt @ Mon Aug 19 22:28:59 2019 > -03 failed, > > > result 64 (WERR_NETNAME_DELETED) > > > 1 consecutive failure(s). > > > Last success @ Mon Aug 19 22:07:23 2019 -03 > > > > > > > > > How can I solve this problem? > > > > You could try forcing replication with: samba-tool drs replicate > > <destinationDC> <sourceDC> <NC> > > > > Where <destinationDC> & <sourceDC> are in the format > > 'ldap://DC_HOSTNAME' and <NC> is the Naming Context, I > woukd start with > > 'domain' > > > > See: samba-tool drs replicate --help > > > > For more info. > > > > Rowland > > > > > > > > -- > > To unsubscribe from this list go to the following URL and read the > > instructions: https://lists.samba.org/mailman/options/samba > > > -- > To unsubscribe from this list go to the following URL and read the > instructions: https://lists.samba.org/mailman/options/samba > >