similar to: Troubles upgrading jailed DC from 4.8.7 to 4.8.9

On Sun, 17 Feb 2019 18:26:21 +0100 Andrea Venturoli via samba <samba at lists.samba.org> wrote: > Hello. > > On several FreeBSD 11.2/amd64 servers, I've got a jail dedicated to > running Samba as an AD DC. > > Some days ago I upgraded one of them from 4.8.7 to 4.8.9 and suddenly > everything stopped working. > Since it was a production box, I immediately

On 2/17/19 8:18 PM, Rowland Penny via samba wrote: > Possible things to check: > Is the ip for vlan1 10.1.2.34 ? Sure. It's the only IP vlan1 has inside the jail; it's shown as an alias on the base host. > Try just setting 'vlan1' You mean change "interfaces=vlan1 10.1.2.34/24" to just "interfaces=vlan1"? It doesn't change anything (still

I am working on a FreeBSD jail (12.1p4) using samba410. I have joined this service to our existing Samab DC DOMAIN using samba-tool domain join. This worked as far as I can tell. I have these entries in smb4.conf # BOF # Global parameters [global] netbios name = SAMBA-02 realm = BROCKLEY-2016.HARTE-LYNE.CA server role = active directory domain controller workgroup = BROCKLEY-2016

FreeBSD-12.1p7 jail running Samba-4.10.15 on ZFS. When I run 'samba-tool domain backup offline targetdir=/tmp' I see this: running backup on dirs: /var/db/samba4/private /var/db/samba4 /usr/local/etc Starting transaction on /var/db/samba4/private/secrets At which point samba-tool enters a permanent wait state. 86064 root 1 52 0 131M 78M wait 3 0:01 0.00%

Hello. I'm running a few sites where the AD DC is a FreeBSD jail. Due to the recent CVEs, I upgraded one of them from 4.3.11 to 4.3.13 and suddenly I run into problems. I don't know whether this matters, but the upgrade involved replacing openldap-client with openldap-sasl-client. Anyway, after the new binaries were in place, Samba would not start. Relevant part of the logs (I can

This sounds familiar... I suggest you try without the interface names and only ipnumbers. Test 1) interfaces = 10.1.2.34/24 127.0.0.1 bind interfaces only = yes nbt client socket address = 127.0.0.1 Try again. In addition to test 1, Test 2. > ntlm auth=YES Remove that from the smb.conf then try again. At least for this test remove it. After a web search I found the solution

On Mon, 18 Feb 2019 09:13:45 +0100 Andrea Venturoli <ml at netfence.it> wrote: > On 2/17/19 8:18 PM, Rowland Penny via samba wrote: > > > Possible things to check: > > Is the ip for vlan1 10.1.2.34 ? > > Sure. > It's the only IP vlan1 has inside the jail; it's shown as an alias on > the base host. > > > > > Try just setting

On Wed, July 22, 2020 14:48, Rowland penny wrote: > On 22/07/2020 19:40, James B. Byrne via samba wrote: >> >> On Wed, July 22, 2020 12:35, James B. Byrne wrote: >>> FreeBSD-12.1p7 jail running Samba-4.10.15 on ZFS. >>> >>> When I run 'samba-tool domain backup offline targetdir=/tmp' I see this: >>> >>> running backup on dirs:

Hello to the samba users list again. I've got an emergency here, a Samba AD DC I've got deployed has crashed again, this is the third time since 12/17/2015 that this domain has failed completely. No power outages or unexpected shutdowns, samba simply fails to start, it appears my database is yet again corrupt: [2016/03/02 11:27:17.025235, 0]

I touched the two missing files /var/db/samba4/private/dns_update_list /var/db/samba4/private/spn_update_list And restarted the Samba44 service. This is what I see now: [2017/02/09 15:48:47.507874, 0] ../source4/smbd/server.c:372(binary_smbd_main) samba version 4.4.8 started. Copyright Andrew Tridgell and the Samba Team 1992-2016 [2017/02/09 15:48:47.922389, 0]

On 02/03/16 20:46, IT Admin wrote: > Any further information required? Any troubleshooting steps? I need to > get this domain functional ASAP. > > Please advise. > > JS > On Mar 2, 2016 11:39 AM, "IT Admin" <it at cliffbells.com> wrote: > >> Hello to the samba users list again. I've got an emergency here, a Samba >> AD DC I've got

On Wed, July 22, 2020 12:35, James B. Byrne wrote: > FreeBSD-12.1p7 jail running Samba-4.10.15 on ZFS. > > When I run 'samba-tool domain backup offline targetdir=/tmp' I see this: > > running backup on dirs: /var/db/samba4/private /var/db/samba4 /usr/local/etc > Starting transaction on /var/db/samba4/private/secrets > I tried the backup online option instead and

On Sun, 2016-11-20 at 16:50 -0500, Adam Tauno Williams via samba wrote: > On Sun, 2016-11-20 at 21:11 +0000, Rowland Penny via samba wrote: > > On Sun, 20 Nov 2016 15:55:08 -0500 > > Adam Tauno Williams via samba <samba at lists.samba.org> wrote: > > > And it looks like nobody is listening on port 135 - > > > [root at larkin26 ~]# netstat --listen --inet

I just upgraded one of my DCs ununtu 20.04 -> 22.04 and samba 4.18 -> 4.19, but the Dc is not yet working again. systemctl status samba-ad-dc shows: Dec 05 12:48:39 cobra samba[749]: [2023/12/05 12:48:39.562920, 0] ../../source4/samba/service_task.c:36(task_server_terminate) Dec 05 12:48:39 cobra samba[749]: task_server_terminate: task_server_terminate: [winbindd child process

On Sun, 20 Nov 2016 16:50:34 -0500 Adam Tauno Williams <awilliam at whitemice.org> wrote: > On Sun, 2016-11-20 at 21:11 +0000, Rowland Penny via samba wrote: > > On Sun, 20 Nov 2016 15:55:08 -0500 > > Adam Tauno Williams via samba <samba at lists.samba.org> wrote: > > > And it looks like nobody is listening on port 135 - > > > [root at larkin26 ~]#

On Wed, July 8, 2020 04:23, Rowland penny wrote: > On 08/07/2020 08:50, Mani Wieser via samba wrote: >> >> On 07.07.2020 22:14, Mani Wieser via samba wrote: >> Found it (while having my morning walk with the dog): same as with >> SOA: this is a zone/domain thing and not record >> >> Usage: samba-tool dns delete <server> <zone> <name>

Hi, I upgraded my Samba 4.5.16 installed (by apt-get) on Debian 9.9 to Samba 4.10 through the Van Belle repository (apt.van-belle.nl). apt-get install -t stretch-samba410 samba attr winbind libpam-winbind libnss-winbind libpam-krb5 krb5-config krb5-user bind9 ctdb ldb-tools smbldap-tools ufw glusterfs-common libcephfs1 The packages "bind9 ctdb ldb-tools smbldap-tools ufw glusterfs-common

Hello. I'm trying to perform a classic upgrade from Samba 3.6.6 with LDAP backend on Debian to 4.1.6 on Ubuntu on a new machine. The samba-tools creates the following *smb.con*f: *# cat /etc/samba/smb.conf** *[global] workgroup = SOMEDOM realm = somedom.local netbios name = SOMEDOM server role = member server passdb backend = samba_dsdb server

I've been using Samba4 on Debian/Jessie since it became "stable". After the last upgrade however, I got a massive failure. The first symptom I noticed was that I couldn't grab updates from the Debian servers. However when clients tried to log in, the real problem revealed itself. They could only log on using a temporary profile and couldn't connect to any of the shares

Hi, after rebooting the AD DC i regularly get NT_STATUS_ADDRESS_NOT_ASSOCIATED and - as a consequence - task_server_terminate: [XXXd failed to setup interfaces] error messages in log.samba (I removed a couple of "samba: setproctitle not initialized, please either call setproctitle_init() or link against libbsd-ctor." lines for better readability): [2019/06/11 09:23:47.400171, 0]