search for: profile_dummi

Hi , I use Tranquil IT's repo. Best, Robert 2020. 02. 11. 10:16 keltez?ssel, Rowland penny via samba ?rta: > On 11/02/2020 06:51, Csorba R?bert via samba wrote: >> Hi, >> >> After I have updated my SAMBA AD environment from version 4.9.18 to >> version 4.10.12 on my secondary server the program is unable to start >> and displays the following error

We should test and post: OS, Samba version, and use all same loglevels in smb.conf I tested 4.11.6 with log level = 0 auth_audit:3 Robert is running samba 4.10.12 (not latest) and log level = 4 @Rowland what did you test? Greetz, Louis > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens > Rowland penny via samba > Verzonden:

Hi, After I have updated my SAMBA AD environment from version 4.9.18 to version 4.10.12 on my secondary server the program is unable to start and displays the following error message:"ERROR:failed to setup profiling". The testparm result didn't print any warning or error. System details: CentOS Linux release 7.7.1908 (Core) with kernel 3.10.0-1062.9.1.el7.x86_64 smb.conf

On 11/02/2020 06:51, Csorba R?bert via samba wrote: > Hi, > > After I have updated my SAMBA AD environment from version 4.9.18 to > version 4.10.12 on my secondary server the program is unable to start > and displays the following error message:"ERROR:failed to setup > profiling". > > The testparm result didn't print any warning or error. > > System

Hi, on my servers I install 2 instances of samba: one samba AD (on 3.X DC)? and an additional samba instance for printserver issues. This have worked until version 4.8.9. With version 4.10.4 the smbd process of the printserver instance stop with: exit_daemon: daemon failed to start: Failed to create session, error code 1 The configuration of the AD: global] ??????? netbios name = admin

On 16/09/2020 19:38, Rommel Rodriguez Toirac via samba wrote: > Hello all; > > I am installing samba4 (version 4.9.5) on Debian 10.5 to use it as a member of a samba4 AD DC domain (version 4.11.4). I am following the guide https://wiki.samba.org/index.php/Setting_up_Samba_as_a_Domain_Member but I am having problems starting samba. > > So far I have installed the necessary packages

Hello all; I am installing samba4 (version 4.9.5) on Debian 10.5 to use it as a member of a samba4 AD DC domain (version 4.11.4). I am following the guide https://wiki.samba.org/index.php/Setting_up_Samba_as_a_Domain_Member but I am having problems starting samba. So far I have installed the necessary packages listed here

Hi for all! I have Samba 4.3.9-Ubuntu DC in ADDC_Mode and it's working perfectly But in Samba Log have this: "samba: setproctitle not initialized, please either call setproctitle_init() or link against libbsd-ctor." The libbsd-dev package is installed Is this a problem? SAMBA.CONF: # Global parameters [global] workgroup = TESTEAD realm = testead.xxxxx.xxx netbios name = GTESTE2

Hello - I'm working on a project that when deployed I'll need wireless access for updates / configuration changes. I've installed Samba but can't get it to work. I can SSH and ping both the host name and IP, but no Samba. I've searched online for help and tried everything that sounded reasonable but I'm at a dead end. Here's some of the relevant info and I'd be glad

Am Do 01.02.2018 um 12:04 schrieb Martin Schwenke: > Hi Nicolas, > > On Thu, 1 Feb 2018 10:57:59 +0100, Nicolas Zuber via samba > <samba at lists.samba.org> wrote: > >> I try to update two clustered samba file servers. Right now samba 4.7.0 >> with ctdb is running on both of them. To update samba I stopped ctdb on >> one of the servers, and compiled and

Hi all, I try to update two clustered samba file servers. Right now samba 4.7.0 with ctdb is running on both of them. To update samba I stopped ctdb on one of the servers, and compiled and installed samba 4.7.1 with: ./configure --with-cluster-support --with-shared-modules=idmap_tdb2,idmap_ad,vfs_glusterfs --with-systemd Trying to start ctdb on the updated server fails with "

Hi, I have a samba 4.5.8 AD DC (debian 9.1 package) which is having problems with RPC requests. This DC has been updated from the wheezy-backports package (4.1.17) via the jessie package (4.2.14) but I'm not sure if RPC worked immediately before the upgrade either since most of the time it only serves LDAP and krb5. Connecting using RSAT from windows gives "RPC Server