similar to: Joining 2008 R2 to Samba4 AD DC

Try : apt-get remove libbsd-dev restart samba, now is the message gone? Gr. Louis > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens BasSamba via > samba > Verzonden: woensdag 15 maart 2017 16:09 > Aan: samba at lists.samba.org > Onderwerp: [Samba] samba: setproctitle not initialized, please either call >

On 15/06/15 11:52, Steve Ankeny wrote: > I have a "Samba | SOGo | OpenChange" server running in VMware. > > I get the following message when running 'apt-get upgrade' -- > > The following packages have been kept back: > libldb-dev libldb1 libmapi0 libmapiproxy0 libmapistore0 libnss-winbind > libpam-winbind libsmbclient libwbclient0 openchangeproxy >

and just a comment.. when i look at : http://inverse.ca/ubuntu-nightly/dists/trusty/trusty/binary-amd64/Packages /search for : 2:4.1.18+dfsg-3~inverse1 Replaces: libpam-winbind (<< 2:3.6.5-2), samba (<= 2.2.3-2), winbind (<< 2:3.5.11~dfsg-3), winbind4 => winbind4.. this all is build agains the old "samba4" naming which is not used anymore. anyway.. i see..

On 15/06/15 14:01, L.P.H. van Belle wrote: > and just a comment.. > > when i look at : > http://inverse.ca/ubuntu-nightly/dists/trusty/trusty/binary-amd64/Packages > /search for : 2:4.1.18+dfsg-3~inverse1 > Replaces: libpam-winbind (<< 2:3.6.5-2), samba (<= 2.2.3-2), winbind (<< 2:3.5.11~dfsg-3), winbind4 > => winbind4.. > > this all is build agains the

I have a "Samba | SOGo | OpenChange" server running in VMware. I get the following message when running 'apt-get upgrade' -- The following packages have been kept back: libldb-dev libldb1 libmapi0 libmapiproxy0 libmapistore0 libnss-winbind libpam-winbind libsmbclient libwbclient0 openchangeproxy openchangeserver python-ldb python-ocsmanager python-samba samba

Ok Steve, to be sure.. run : apt-key adv --keyserver keys.gnupg.net --recv-key 0x810273C4 if not done yet. add to /etc/apt/source.list.d/openchange.list deb http://inverse.ca/ubuntu trusty trusty or deb http://inverse.ca/ubuntu-nightly trusty trusty to force the needed packages. __COPY_PAST_START cat << EOF >> /etc/apt/preferences.d/preferences-ubuntu-trusty Package: * Pin:

On 06/15/2015 07:14 AM, Rowland Penny wrote: > On 15/06/15 11:52, Steve Ankeny wrote: >> I have a "Samba | SOGo | OpenChange" server running in VMware. >> >> I get the following message when running 'apt-get upgrade' -- >> >> The following packages have been kept back: >> libldb-dev libldb1 libmapi0 libmapiproxy0 libmapistore0

look : winbind depends on samba (= 2:4.1.18+dfsg-3~inverse1); however: >2:4.1.18+dfsg-3~inverse1 so mixed setup of ubuntu with inverse packages of samba. You need to use the inverse packages of samba to keep openchange working. I suggest you set your package pinning. OR ! remove the inverse : winbind version and install the ubuntu version. Greetz, Louis >-----Oorspronkelijk

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

Hello, Some users in my domain report that they have to use different (old) passwords on different computers. They say that they still have to use their "old" passwords after they changed it. My domain setup is that users are asked to automatically change their password on Windows 7 Enterprise after some months. So they have to do that. Otherwise they cannot login. But why is it, that

Thanks to various contributors on the Samba List (particularly Rowland, Marc & Andrew), I have successfully configured a Samba AD DC on Ubuntu 14.04 from scratch and joined my Windows 2008 R2 Servers. However, I have had a recurring error from the beginning -- [2015/04/30 05:06:31.194379, 0] ../source4/smbd/server.c:370(binary_smbd_main) samba version 4.1.6-Ubuntu started.

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

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

On 14/02/15 19:45, Steve Ankeny wrote: > answers below > > On 02/14/2015 02:10 PM, Rowland Penny wrote: >> On 14/02/15 18:05, Steve Ankeny wrote: >>> answers below >>> >>> On 02/14/2015 08:22 AM, Rowland Penny wrote: >>> >>> I've made that change with no change in the results. I've also >>> started 'winbind'

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

Could I get some input regarding restoring ACLs? There's nothing in the Samba wiki about what to do with the ACL archive. I've finished all of the other steps already, what do I need to do to restore this archive? JS On Mar 3, 2016 4:02 PM, "Rowland penny" <rpenny at samba.org> wrote: > On 03/03/16 20:33, IT Admin wrote: > >> I do have the 4.3.3 sources.

On 19/04/16 21:08, Thomas Smith wrote: > 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

I was too quick to send my previous email. It can't really be a problem of the package since I have, as mentioned, another system with the exact same setup and the exact same package versions and it all works there... On Sun, 23 Dec 2018 at 11:18, Viktor Trojanovic <viktor at troja.ch> wrote: > Yes, I tried running dbcheck (see first email), it showed 0 errors from > the start, I

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

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