similar to: Erro Upgrade Samba 4.6.3 to 4.8

Hi, Thank your for your answers. @Rowland: Yes, Winbind is installed but it seems it is not started (or cannot start) @Andrew: Please find extract in log level 4 during a service restart and a connection test with smbclient from another machine. I hope this could help, this is not clear to me : ==> /var/log/samba/log.samba <== [2018/05/29 10:54:00.173894, 0]

On 3/23/2018 8:50 AM, Sven Vogel via samba wrote: > 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

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

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

I could really use some support with this. I understand it's always possible to just restore from a backup but the more interesting question is if something can be done with the data at hand. Basically, I'm trying to understand how it's possible that a dbcheck shows no errors, an ldbsearch is successful, and yet it's not possible to start the AD properly. What else is there that

The two systems I'm referring to are on different domains, different locations. No connection whatsoever except me being the one administering both. According to oEMInformation the server was provisioned by 4.3.3. I just checked the Samba log file and it seems that version 4.7.4 was running before the update. I'm now looking at the logs right before the upgrade and indeed, there have

Hi, I have been running a Samba AD PDC with BIND9_DLZ on a Debian system for a year now without problems, and in the hope for ability to create AD backups I upgraded the samba packages (along with other packages with minor updates). Everything seemed OK during the upgrade, all processes restarted, but soon after I found that PAM refuses to authenticate AD usernames. By checking the samba

Hi, Some time back I had written to the list about integrating Cisco ISE and facing errors with RPC login. When we actually integrated using ISE 2.4.0357 we noticed that Kerberos authentication is working like a charm. But MS-RPC authentication throws error. From the samba logs, we noticed that ISE workstation is able to negotiate the RPC ports switch to higher Dynamic RPC ports,

>sudo systemctl stop systemd-resolved >sudo systemctl disable systemd-resolved.service > >Rowland Now systemd-resolved is inactive, but samba still does not listen.. root at natter:/home/joachim# systemctl start samba-ad-dc Job for samba-ad-dc.service failed because a timeout was exceeded. See "systemctl status samba-ad-dc.service" and "journalctl -xe" for

On 4/19/2016 3:39 PM, Thomas Smith wrote: > Here's what I get at level 0 right after stopping/starting Samba: > > [2016/04/19 12:27:06.043469, 0] > ../source4/smbd/server.c:372(binary_smbd_main) > samba version 4.3.8-Ubuntu started. > Copyright Andrew Tridgell and the Samba Team 1992-2015 > [2016/04/19 12:27:06.157629, 0] >

On 2019/02/14 22:19, Rowland Penny via samba wrote: > On Thu, 14 Feb 2019 21:43:43 +0200 > Ashley via samba <samba at lists.samba.org> wrote: > >> On 2019/02/14 21:12, Rowland Penny via samba wrote: >>> On Thu, 14 Feb 2019 19:14:19 +0200 >>> Ashley via samba <samba at lists.samba.org> wrote: >>> >>>> Hi there >>>>

Am 25.11.19 um 16:07 schrieb Stefan G. Weichinger via samba: > Am 25.11.19 um 11:49 schrieb L.P.H. van Belle via samba: >> Hai Stefan, >> >> Yes, i do recommend the setup from 4.9 to 4.10 first. >> >> If you plan is to upgrade to buster. >> 1) on stretch, update samba to 4.10 >> 2) Change apt sources do buster, * your now also able to add

Hello. I've got a network of FreeBSD servers which traditionally hosted a classic domain. I upgraded some months ago, removing the old PDC and BDC and migrating to an AD DC controller in a jail. This is working fine with Samba 4.4.13. Now I'm trying to add a second DC, so I created a new jail on another physical server and went on with the setup, following: >

Ok, you have found something, and i've seen a bit more. First, this. /usr/bin/samba_kcc: ImportError: /usr/lib/samba/libreplace-samba4.so: version `SAMBA_4.7.4' not found (required by /usr/lib/libsamba-util.so.0) [2018/12/22 19:13:45.004497, 0] There are left overs from a previous install. You are on Arch Linux as i did read. With what i've seen. Stop samba and all related

Here's what I get at level 0 right after stopping/starting Samba: [2016/04/19 12:27:06.043469, 0] ../source4/smbd/server.c:372(binary_smbd_main) samba version 4.3.8-Ubuntu started. Copyright Andrew Tridgell and the Samba Team 1992-2015 [2016/04/19 12:27:06.157629, 0] ../source4/smbd/server.c:490(binary_smbd_main) samba: using 'standard' process model samba: setproctitle not

There is no winbindd--it was never installed. I don't recall exactly why I didn't install it, but I seem to recall something about Samba4 in an AD domain control role not needing it. I ended up using SSS instead. Sanatized smb.conf: # Global parameters [global] workgroup = DCS realm = DCS.LOCAL netbios name = SERVER server role = active directory domain

It was my understanding that winbind wasn't necessary for Samba4. This server has been running for months without it. Sanatized smb.conf: # Global parameters [global] workgroup = DCS realm = DCS.LOCAL netbios name = SERVER server role = active directory domain controller dns forwarder = 8.8.8.8 idmap_ldb:use rfc2307 = yes debug level =

I set the Samba debug level to 4 a bit ago, so the logs are a bit noisy--before that, there didn't seem to be much log activity when I produced that error. So with the debug level at 4, these entries kind of stand out a bit: [2016/04/19 09:55:27.662721, 2] ../source4/smbd/process_standard.c:123(standard_child_pipe_handler) Child 16336 (winbindd) exited with status 1 These entries repeat

On 26/11/2019 19:29, Stefan G. Weichinger via samba wrote: > Am 25.11.19 um 16:07 schrieb Stefan G. Weichinger via samba: >> Am 25.11.19 um 11:49 schrieb L.P.H. van Belle via samba: >>> Hai Stefan, >>> >>> Yes, i do recommend the setup from 4.9 to 4.10 first. >>> >>> If you plan is to upgrade to buster. >>> 1) on stretch, update samba

Ok, thank you--that worked, but it doesn't make sense. The server's been operational for months without winbind. Did something change in Samba that it won't operate now without it? I specifically remember reading that winbind wasn't necessary and, in fact, wasn't recommended with Samba 4 AD. On Tue, Apr 19, 2016 at 1:27 PM Rowland penny <rpenny at samba.org> wrote: