similar to: Issue after upgrade to samba-client-4.9.1-6.el7.x86_64 - Unable to initialize messaging context

Hello Andrew, Thank you this reponce.. Ah, ok, now, im testing it on 4.10.8 on Debian and i see the same. So we can ignore it for now? As far i can tell everything works correctly here with 4.10.8. Greetz, Louis > -----Oorspronkelijk bericht----- > Van: Andrew Bartlett [mailto:abartlet at samba.org] > Verzonden: woensdag 18 september 2019 11:25 > Aan: L.P.H. van Belle;

On 17/09/2019 23:35, Stephen Black wrote: > Done. And for those that didn't get the smb.conf [global] ??? workgroup = SAMBA ??? security = user ??? passdb backend = tdbsam ??? printing = cups ??? printcap name = cups ??? load printers = yes ??? cups options = raw [homes] ??? comment = Home Directories ??? valid users = %S, %D%w%S ??? browseable = No ??? read only = No ???

Hi All, First time poster. Not a unix pro. We had samba client installed (v. 3.6) and working to run a single file print command. smbclient --debuglevel=1 --log-basename=/mnt/autofs/logs/print/ -U bbldtl\\adminuser //$3/$2 'obscured-password' --command "print $1" | tee -a /mnt/autofs/logs/print/print.log It would output [2019/07/04 04:27:36, 0]

Am 21.12.18 um 16:47 schrieb Peter Eriksson via samba: >> What is "Unable to initialize messaging context"? >> >> I see a patch back in July, related to "Fix bug 13465", >> https://lists.samba.org/archive/samba-technical/2018-July/129186.html but it >> is unclear why the message is still being issued? > > Because that patch for bug 13465

Sambadevs, I don't know if this is a bug or just a spurious error message when using smbclient (on a standalone config), but checking smbclient, I get: 02:47 2pi:~> smbclient -U% -Llocalhost Unable to initialize messaging context Sharename Type Comment --------- ---- ------- samba Disk 2pi - Law IPC$ IPC

Hello, I am getting this when trying to run testparm and I'm also unable to start the samba daemon. I am trying to set up a AD DC. This is a fresh install of CentOS 7 minimal with the dependency script from the wiki run. The version is 4.11.2 and was successfully compiled. I believe the two issues are related but I'm unable to find anything on google that indicates what could be the

Contrary to best practices, on my boxes I'm always root so it is doing this when run as root. I'm getting the error for the daemon also when run as a system service in systemd. Configure line: ./configure \ --disable-cups \ --without-ldb-lmdb \ --prefix=/opt/samba \ --sysconfdir=/etc/samba \ --localstatedir=/var \ --with-systemd \ --systemd-install-services \

> On 21 Dec 2018, at 09:54, David C. Rankin via samba <samba at lists.samba.org> wrote: > > Sambadevs, > > I don't know if this is a bug or just a spurious error message when using > smbclient (on a standalone config), but checking smbclient, I get: > > 02:47 2pi:~> smbclient -U% -Llocalhost > Unable to initialize messaging context > >

On Wed, 2 Jan 2019 09:32:55 +0100 "Stefan G. Weichinger via samba" <samba at lists.samba.org> wrote: > Am 21.12.18 um 16:47 schrieb Peter Eriksson via samba: > > >> What is "Unable to initialize messaging context"? > >> > >> I see a patch back in July, related to "Fix bug 13465", > >>

On 30/10/2019 18:40, Rich Webb via samba wrote: > Contrary to best practices, on my boxes I'm always root so it is doing this when run as root. I'm getting the error for the daemon also when run as a system service in systemd. Hmm, if I run smbclient as a normal user (output cut for brevity), I get this: rowland at devstation:~$ smbclient -L localhost -N Unable to initialize

OK I recompiled with --with-lockdir=/var/lib/samba/lock and it's now getting further... now I'm getting this when I try to start the samba daemon: Calling SPN name update script /opt/samba/sbin/winbindd: winbindd version 4.11.2 started. /opt/samba/sbin/winbindd: Copyright Andrew Tridgell and the Samba Team 1992-2019 /opt/samba/sbin/winbindd: Failed to create directory /var/run for pid

No, it's as if it can't create the file for some reason... permissions are 755 on that directory - owned by root. Thanks, Rich ----- On Oct 30, 2019, at 3:08 PM, samba samba at lists.samba.org wrote: > On 30/10/2019 18:40, Rich Webb via samba wrote: >> Contrary to best practices, on my boxes I'm always root so it is doing this when >> run as root. I'm getting

Hi Team, I am trying to setup a samba CTDB cluster to export gluster volme as samba share. While CTDB cluster works well, I ran into an issue with creating subdirectories and also creating files/directories within subdictories when accessing the share from both linux and windows servers. Setup details : We have a three node cluster with nodes snode1, snode2 and snode3. I have a gluster

Hi Team, I am trying to setup a samba CTDB cluster to export gluster volme as samba share. While CTDB cluster works well, I ran into an issue with creating subdirectories and also creating files/directories within subdictories when accessing the share from both linux and windows servers. Setup details : We have a three node cluster with nodes snode1, snode2 and snode3. I have a

Hello again, So I made an overall change to the config and removed the sambashare entirely. I just want to have a basic connection before any further modification. Below is the config setup: [global]? ? ? ? log file = %S.log? ? ? ? log level = 3? ? ? ? workgroup = WORKGROUP? ? ? ? security = user? ? ? ? printing = cups? ? ? ? printcap name = cups? ? ? ? cups options = raw? ? ? ? ntlm auth = yes? ?

I used to be able to load printer drivers via "server properties". Now when I go in the printer drivers are listed and I can use the properties button but the Add/Remove buttons are greyed out. This is a Samba 3.0.0/2.4.2-SGI_XFS_1.0 box and I've tried both NT4sp6 and Win2003beta clients (both exhibit the same behaviour). I see the following in the log when I connect to

Hi Rowland, Made some changes as shown below: [global]? ? ? ? log file = %S.log? ? ? ? log level = 3? ? ? ? workgroup = WORKGROUP? ? ? ? security = user? ? ? ? passdb backend = tdbsam? ? ? ? printing = cups? ? ? ? printcap name = cups? ? ? ? load printers = yes? ? ? ? cups options = raw? ? ? ? lanman auth = no? ? ? ? ntlm auth = yes [Anonymous]? ? ? ? comment = anonymous file share? ? ? ? path =

Hi, I'm using samba-2.2.1a on a Debian Linux box as a Debian package. It only serves as a printserver for about 35 printers which are all in /etc/printcap. Samba exports them all through the [printers] section in smb.conf. "guest ok = yes" for the [printers] The problem is as follows: - printadmin (having uid 0) logs onto the printserver using a win2k client - printadmin

Thank you Rowland - adding "ntlm auth = yes" in the global section and rebooting the machine has provided access once again to the NAS. In answer to your questions - the smb.conf was from the PCLOS machine.  Question - I had tried sec=ntlm in the mount statement without it being in the smb.conf - did that not work because ntlmv1 had not been enabled? As to the question marks, that

On Tue, 7 May 2019 18:06:35 -0400 Phil Dermott <pdermott at rogers.com> wrote: > As requested - smb.conf > > # See smb.conf.example for a more detailed config file or > # read the smb.conf manpage. > # Run 'testparm' to verify the config is correct after > # you modified it. > > [global] > ?????????????? workgroup = HOME > ?????????????? server