similar to: log level and samba-tool domain demote

On 23/07/15 16:23, mathias dufresne wrote: > Hi all, > > I tried "samba-tool ldapcmp" several times to solve this issue, without > success. > > On DC acting as full FSMO: > dc20:~# samba-tool ldapcmp ldap://dc00.ad.dgfip.lan > ldap://dc20.ad.dgfip.lan domain > ERROR(ldb): uncaught exception - ldb_wait: Time limit exceeded (3) > File

Am 16.07.2015 um 17:18 schrieb Rowland Penny: > On 16/07/15 13:27, Reindl Harald wrote: >> >> Am 16.07.2015 um 14:02 schrieb Rowland Penny: >>> /etc/hosts should be: >>> >>> 127.0.0.1 localhost.localdomain localhost >> >> uhm no - you want 127.0.0.1 normally resolved to localhost and hence >> 127.0.0.1 localhost

Hi all, I tried "samba-tool ldapcmp" several times to solve this issue, without success. On DC acting as full FSMO: dc20:~# samba-tool ldapcmp ldap://dc00.ad.dgfip.lan ldap://dc20.ad.dgfip.lan domain ERROR(ldb): uncaught exception - ldb_wait: Time limit exceeded (3) File "/usr/lib64/python2.6/site-packages/samba/netcmd/__init__.py", line 175, in _run return

The following commands work on both DC: host -t A <short_hostname_of_other_DC> host -t A <fqdn_hostname_of_other_DC> hostname and hostname --fqdn are working on both DC.The simplest way is to not declare external IP /etc/hosts SRV DNS entries which are working are: host -t SRV _kerberos._tcp.Default-First-Site-Name._sites.dc._msdcs.ad.domain.tld host -t SRV

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

Hi, I get the following error when I am trying to check the replication status of my samba4 dc: ERROR(<class 'samba.drs_utils.drsException'>): DRS connection to nidy. failed - drsException: DRS connection to nidy. failed: (-1073741772, 'The object name is not found.') File "/usr/lib64/python2.7/site-packages/samba/netcmd/drs.py", line 39, in drsuapi_connect

Am 12.10.2016 um 20:17 schrieb lingpanda101--- via samba: > On 10/12/2016 1:57 PM, Ronny Forberger via samba wrote: >> Hi, >> >> I get the following error when I am trying to check the replication >> status of my samba4 dc: >> >> ERROR(<class 'samba.drs_utils.drsException'>): DRS connection to nidy. >> failed - drsException: DRS connection

Hi all, I posted on both mailing as this seems to be (to me) an internal issue. As the 4.3.1 went out I decided to switch my DC from 4.3.0 to this new version. The process was to install Samba 4.3.1 on new systems, joining these Samba as DC, seizing FSMO roles, demote all 4.3.0. The few I tested until now is working except for DNS entries: samba_dnsupdate is not working as it tries to update

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 :

Am 13.10.2016 um 16:28 schrieb lingpanda101 at gmail.com: > On 10/13/2016 10:19 AM, Ronny Forberger wrote: >> >> Am 12.10.2016 um 20:17 schrieb lingpanda101--- via samba: >>> On 10/12/2016 1:57 PM, Ronny Forberger via samba wrote: >>>> Hi, >>>> >>>> I get the following error when I am trying to check the replication >>>>

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, I tried to replicate two DC's (on test setup) with "--full-sync" option but fails with error message below. I tried "--full-sync" because I wonder if it has any effect on some diverged entries reported by "samba-tool ldapcmp". # samba-tool drs replicate dc1 dc2 --full-sync DC=samdom,DC=com ERROR(<class 'samba.drs_utils.drsException'>): DRS

Am 13.10.2016 um 16:54 schrieb lingpanda101 at gmail.com: > On 10/13/2016 10:37 AM, Ronny Forberger wrote: >> >> Am 13.10.2016 um 16:28 schrieb lingpanda101 at gmail.com: >>> On 10/13/2016 10:19 AM, Ronny Forberger wrote: >>>> Am 12.10.2016 um 20:17 schrieb lingpanda101--- via samba: >>>>> On 10/12/2016 1:57 PM, Ronny Forberger via samba wrote:

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

Hey, Thank you Louis for this script, I didn't yet took time to dig in but I'll do. I didn't took time neither to perform another test. That should be done today. Anyway I waited for DC synchronisation before posting. I joined my DC and removed the old ones almost at same time then I gave more than 12 hours to my DC to synchronize. Then I tried to understand what happened, I wrote

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

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

After update I have got this: samba-tool drs kcc -Uadm2 -d 9 INFO: Current debug levels: all: 9 tdb: 9 printdrivers: 9 lanman: 9 smb: 9 rpc_parse: 9 rpc_srv: 9 rpc_cli: 9 passdb: 9 sam: 9 auth: 9 winbind: 9 vfs: 9 idmap: 9 quota: 9 acls: 9 locking: 9 msdfs: 9 dmapi: 9 registry: 9 scavenger: 9 dns: 9 ldb: 9 tevent: 9 auth_audit: 9