similar to: Joined a second DC, some glitches...

On Thu, 26 Oct 2017 12:41:11 +0200 Marco Gaiarin via samba <samba at lists.samba.org> wrote: > > I've setup my second DC, following the samba wiki, without major > trouble. > > Only three notes: > > a) i've followed the suggestion to move idmap.ldb from the first DC to > the second (Rowland! Clap me! I've not sayed 'primary' and >

Hello, I have recently compiled, installed and configured samba4 to run on a FreeBSD server. samba -V reports the version to be Version 4.1.0pre1-GIT-57990cb. The server has working BIND 9.9 and ISC-DHCP services running on it. I have provisioned samba 4 to use the BIND_DLZ DNS backend. On the whole things seem to be working. local names are being resolved. phpLDAPAdmin shows the new

Hello all, I have installed Samba on a Cent OS 6.3. I followed the Samba4/HOW-TO. I'm using the samba internal dns. I can join the domain with a Win 7 Client but I have problems with the internal dns. I tried to test/debug the dynamic dns update by the help of the Samba4/HOW-TO. The summary of the error-message: ; TSIG error with server: tsig verify failure Failed nsupdate: 2 Failed

Hi all, I've set up a simple domain using Samba 4.4.2 from source under Ubuntu 16.04. I accepted the usual defaults and basically followed wiki.samba.org to the letter. The main thing is I'm using Samba's internal DNS and not Bind (Bind is not even installed on the system). In the log.samba file on the first DC I kept getting this: [2016/04/28 17:01:02.716292, 0]

I'm sorry, after double-checking the Louis's link I've found that the domain zone should be domain-wide, while the _msdcs stuff should be forest wide. I'll change it and try again. Apologies. >>>>> # samba-tool dns zonelist 172.26.1.81 >>>>> Password for [administrator at domain.com]: >>>>> 2 zone(s) found >>>>>

Hi I believe I am having DNS upgrade issues, as noticed below: /etc/init.d/samba-ad-dc status ? samba-ad-dc.service - Samba AD Daemon Loaded: loaded (/lib/systemd/system/samba-ad-dc.service; enabled; vendor preset: enabled) Active: active (running) since Fri 2019-08-02 10:04:24 -03; 5h 20min ago Docs: man:samba(8) man:samba(7) man:smb.conf(5) Main PID: 9284

On 4/28/2016 1:05 PM, Rowland penny wrote: > On 28/04/16 17:21, Wayne Merricks wrote: >> Hi all, >> >> I've set up a simple domain using Samba 4.4.2 from source under >> Ubuntu 16.04. >> >> I accepted the usual defaults and basically followed wiki.samba.org >> to the letter. The main thing is I'm using Samba's internal DNS and >>

I've set up a lab for testing Samba 4.1 as an RODC emulating a satellite office setup, using the sernet packages on SLES11SP2. ## Problem 1 samba_dnsupdate is failing: ==> /var/log/samba/log.samba <== [2013/11/18 13:22:37.416193, 0] ../lib/util/util_runcmd.c:317(samba_runcmd_io_handler) /usr/sbin/samba_dnsupdate: ; TSIG error with server: tsig verify failure [2013/11/18

Hello. We're running Samba 4.3.9 AD on two Ubuntu 16.04 LTS machines. I'm managing AD users and DNS from Windows 10 joined to the domain, by using ADUC. Last week I noticed the following error when starting ADUC as Administrator of the AD domain: ---- Naming information cannot be located because: The RPC server is unavailable. Contact your system administrator to verify that your domain

I am installing a new Samba 4.2 Active Directory server on CentOS 7. I followed the Wiki instructions on how to create the server. I am using sernet-samba 4.2 binaries. Everything seems to be OK on the Linux side but I cannot get any windows client to successfully join the domain. Each attempt returns the following error message "RPC Server in not available". Below are the config file

I joined an existing domain according to: https://wiki.samba.org/index.php/Samba4/HOWTO/Join_a_domain_as_a_DC My var/log.samba shows the following error message ... and unfortunately ... I have no idea what that means. [2013/05/29 20:48:00, 0] ../lib/util/util_runcmd.c:334(samba_runcmd_io_handler) /usr/local/samba/sbin/samba_dnsupdate: tkey query failed: GSSAPI error: Major = Unspecified

In addition with Rowlands comment. I suggest you try /etc/hosts add only 127.0.0.1 localhost Now type Hostname -f Hostname -s Hostname -d Hostname -I Are these all correct? > No, Edit resolv.conf domain samba.ifa.net search samba.ifa.net ifa.net nameserver 127.0.0.1 What happens now if you try the above command. Correct? Yes => correct your hosts and resolv.conf No || \/

Hi, It's my first try to setup RODC using Samba 4.8. We have latest Samba 4.7 environnement with 2 DC and some file servers. Joining the DC to the domain is OK using samba-tool domain join command. The domain controller appears in the DC list (MMC) However, users cannot be authenticated. Samba is running but these ports are closed : netbios-ssn 139/tcp # NETBIOS session service

Can you try to upgrade to any 4.8 version then to 4.9.4? might work, atleast my guess this will have a better chance get passed this bug. Greetz, Louis > Op 31 dec. 2018 om 18:35 heeft Král Gergely via samba <samba at lists.samba.org> het volgende geschreven: > > 2018-12-31 17:29 id??pontban Rowland Penny via samba ezt írta: > >>> >> >> OK,

I just set a DC with samba 4.1 but the other machine that should syncronize the DNS (using bind) just connect and then hang. on /var/log/samba/log.samba I have: [2015/02/11 20:11:53.161439, 0] ../lib/util/util_runcmd.c:317(samba_runcmd_io_handler) /usr/sbin/samba_dnsupdate: ; TSIG error with server: tsig verify failure I looked around but the fix found did not worked or were not for this

On Wed, 02 Jan 2019 20:09:44 +0100 Král Gergely via samba <samba at lists.samba.org> wrote: > 2018-12-31 20:50 időpontban L.P.H. van Belle via samba ezt írta: > > Can you try to upgrade to any 4.8 version then to 4.9.4? > > might work, atleast my guess this will have a better chance get > > passed this bug. > > > > I can confirm that an upgrade to 4.7.3 to

Hi, I have two problems with my 2 Samba AD-DC. I don't know if the two problems are related. Both domain controllers show the same error pattern for problem 1.The second problem only occurs with the second domain controller. The domain itself seems to work and be in order. Does someone know where this comes from and how to solve it? ## Issue 1 ## By doing my random log checking, I saw the

Good afternoon, I have installed a fileserver with samba4 environment. This is configured to works as AD-DC even if I only use it as a fileserver (at the moment). All seems to works fine but, every 10 minutes, the log print these messages: Mar 22 11:53:17 fileserver samba[1946]: [2016/03/22 11:53:17.557554, 0] ../lib/util/util_runcmd.c:324(samba_runcmd_io_handler) Mar 22 11:53:17 fileserver

On Sat, 8 Jun 2024 17:05:25 +0200 Ronny Preiss via samba <samba at lists.samba.org> wrote: > Hi, > > I have two problems with my 2 Samba AD-DC. I don't know if the two > problems are related. > Both domain controllers show the same error pattern for problem 1.The > second problem only occurs with the second domain controller. > The domain itself seems to work and

Problem whith dnsupdate --> /etc/samba# samba_dnsupdate --all-names --fail-immediately Failed to get Kerberos credentials, falling back to samba-tool: kinit for DOMAIN-SERVER2$@POLICIA2.RIONEGRO.GOV.AR failed (Cannot contact any KDC for requested realm) ERROR(runtime): uncaught exception - (9711, 'WERR_DNS_ERROR_RECORD_ALREADY_EXISTS') File