similar to: Samba4 - Cannot contact any KDC for requested realm

On 22/03/16 14:38, Daniele Manfredi wrote: > Il 22/03/2016 14.45, Rowland penny ha scritto: >> On 22/03/16 13:35, Daniele Manfredi wrote: >>> 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

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

Hello, please excuse my bad englisch. I am not a native speaker. I try to install Samba 4 as a active directory domain controller but I get always this message in the /var/log/syslog: Jul 18 11:42:41 file winbindd[1100]: [2018/07/18 11:42:41.609594,  0] ../source3/winbindd/winbindd_cache.c:3235(initialize_winbindd_cache) Jul 18 11:42:41 file winbindd[1100]:   initialize_winbindd_cache:

Am 19.07.2018 um 17:50 schrieb Rowland Penny via samba: > On Thu, 19 Jul 2018 17:33:46 +0200 > Anton Blau via samba <samba at lists.samba.org> wrote: > >> Am 19.07.2018 um 10:03 schrieb Rowland Penny via samba: >>> On Wed, 18 Jul 2018 23:21:41 +0200 >>> Anton Blau via samba <samba at lists.samba.org> wrote: >>> >>>> Am 18.07.2018 um

Am 19.07.2018 um 10:03 schrieb Rowland Penny via samba: > On Wed, 18 Jul 2018 23:21:41 +0200 > Anton Blau via samba <samba at lists.samba.org> wrote: > >> Am 18.07.2018 um 14:17 schrieb Rowland Penny via samba: >> > It is touched on here: > > https://wiki.samba.org/index.php/Setting_up_Samba_as_an_Active_Directory_Domain_Controller#Parameter_Explanation >

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

> On 2 Jan 2019, at 22:43, Rowland Penny via samba <samba at lists.samba.org> wrote: > > On Wed, 2 Jan 2019 19:35:04 +0000 > Rowland Penny via samba <samba at lists.samba.org> wrote: > >> 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

Hi, i have the same problem. Inplace upgrade and i get the following error. Mar 23 13:46:50 orion2 systemd[1]: Started Session 30346 of user root. Mar 23 13:46:50 orion2 systemd-logind[1316]: Removed session 30346. Mar 23 13:46:50 orion2 sernet-samba-ad[7358]: Shutting down SAMBA AD services : ..done Mar 23 13:46:50 orion2 systemd[1]: Stopped LSB: initscript for the SAMBA AD services. Mar 23

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

Am 23.07.2018 um 23:27 schrieb Rowland Penny via samba: > On Mon, 23 Jul 2018 23:09:58 +0200 > Anton Blau via samba <samba at lists.samba.org> wrote: > >> Am 19.07.2018 um 17:50 schrieb Rowland Penny via samba: >>> On Thu, 19 Jul 2018 17:33:46 +0200 >>> Anton Blau via samba <samba at lists.samba.org> wrote: >>> >>>> Am 19.07.2018 um

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

Hi, I have restarted, but it didn't solve the problem. /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 Mon 2019-08-12 15:32:18 -03; 9s ago Docs: man:samba(8) man:samba(7) man:smb.conf(5) Main PID: 575 (samba)

On 12/31/2015 11:01 AM, Reindl Harald wrote: > > > Am 31.12.2015 um 16:51 schrieb James: >> I forgot, I do not want to update the distro at the moment. My >> production is currently on 12.04. Want to keep things symmetrical. I'm >> going to compile and build bind again. >> >> mount | grep /run >> tmpfs on /run type tmpfs

Hai, ? I just installed a clean sernet samba 4.2.1 with just 2 dc's, used my scripts, all went ok, but when i check the logs. Im see-ing the following..?? ( with every start of restart ) ? [2015/04/22 13:50:40.622537,? 0] ../source4/smbd/server.c:370(binary_smbd_main) ? samba version 4.2.1-SerNet-Debian-7.wheezy started. ? Copyright Andrew Tridgell and the Samba Team 1992-2014 [2015/04/22

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]

Since a bit more than a year I run a Samba4 AD server on a Debian testing box. During that period I did update and dist-update the box about twice a week, and also did update and recompile Sambe, i.e. Samba and Debian Jessie are on their latest stage. I use Bind 9.9.3 as name server, which works absolutely smooth. But two days ago something got broken, and I am totally clueless, what went

On Sun, 31 Mar 2019 13:55:18 +0200 Viktor Trojanovic via samba <samba at lists.samba.org> wrote: > On Sat, 30 Mar 2019 at 17:45, L.P.H. van Belle <belle at bazuin.nl> > wrote: > > > > you can upgrade from 4.7 to 4.9. > > but you must run samba-tool dbcheck > > that should work also. after the check run samba-tool dbcheck > > --reindex > > I

First of all, thanks to you all for bearing with me. To answer the questions: - Subnets: yes, different subnets, routing is fine, can connect to Windows DC via telnet (DNS), OpenSSL on 389 and 636 - Naming: I could not find any object in the existing AD with the same name of the Samba DC that I want to add - Join existing: I try to join an existing Windows AD, not Samba AD I wiped the

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

Hi, I use the Van Bell repo, I've upgraded from samba 4.7 to samba 4.9 but now it fails, these are the errors: dic 12 09:14:49 samba4 samba[4881]: task[dnsupdate][4881]: [2018/12/12 09:14:49.372290, 0] ../lib/util/util_runcmd.c:327(samba_runcmd_io_handler) dic 12 09:14:49 samba4 samba[4881]: task[dnsupdate][4881]: /usr/sbin/samba_dnsupdate: Failed to bind to uuid