similar to: Errors for shares since 4.12.0

Hi All, Sorry for being quiet, I was busy last days. But tonight I am doing bisecting to find the "guilty commit" - started from master as "bad" and v4-11-latest as "good". Still 8 steps to test in bisecting - each one takes about half an hour (2 cores VM on the i3 cpu computer). Will let you know. Pawel. czw., 7 maj 2020 o 09:30 Andrew Bartlett <abartlet at

On Thu, 2020-05-07 at 08:41 +0200, Andreas Hauffe via samba wrote: > Error verifying signature: parse error > Hi, > > in March I wrote a mail to the list and reported an error I got > using > samba 4.12.0. I just want to inform, that I got personal mails from > five > or six samba users, that had the same problem without any solution. > So > I'm not the only

Hi, I tried samba 4.12.0 on our file server which is a domain member and exporting some shares. We're getting some strange errors on some shares since the update. Right after starting or restarting smbd everything is fine. After short while (seconds or a few minutes) users are getting errors when trying to access the shares, e.q. "Invalid Handle Error", "An unexpected

Thanks, I will give that a try. But I need the 'winbind separator = +'. We use some expensive commercial software (e.g. ANSYS, ABAQUS, ...), which uses shell scripts to start their software under linux. These scripts are not able to handle a backslash in the user name. The only solution was to switch to a "+" character. We reported these issues two years ago. Regards,

Hi All, It's already 6am at my side. After the whole night of bisecting, compiling and testing I think I have nailed it: fd61e550acec6e9924a71712eef739b58c7d68e8 is the first bad commit commit fd61e550acec6e9924a71712eef739b58c7d68e8 Author: Volker Lendecke <vl at samba.org> Date: Mon Sep 16 16:16:40 2019 -0700 smbd: Don't always walk the share mode array in

Hi Am 09.03.20 um 16:32 schrieb Rowland penny via samba: > On 09/03/2020 14:25, Andreas Hauffe via samba wrote: >> [global] >> ??????? dedicated keytab file = /etc/krb5.keytab >> ??????? kerberos method = secrets and keytab > Why the dedicated keytab ? We have a kerberized NFS4 running on that machine, too. > >> workgroup = ILRW >> ??????? idmap config dom :

'git checkout' in your first sentence- please be more detailed. And please remember where I start - I am just after 'git clone' and build of 4.13.x Pawel wt., 5 maj 2020 o 23:28 Andrew Bartlett <abartlet at samba.org> napisa?(a): > On Tue, 2020-05-05 at 22:32 +0200, pavlos wrote: > > Hi Andrew et al, > > > > Now is the time to come back to my

Hi Andrew et al, Now is the time to come back to my leisure... Preparing the environment to the 'git bisect' surgery: - Got a clone of the last VM with 4.12.2 installed from https://download.samba.org/pub/samba/samba-latest.tar.gz - Stopped smb/nmb services and uninstalled 'sudo make uninstall' within the directory 4.12.2. - Got the current master with 'git

My plans are as follows, step by step: - clone the VM, clean and build the newest from gitlab, I can see it is 4.13.0pre1 - clone the VM. clean and build the latest supported 4.11.8 - create a new fresh VM with another distro, not Arch or Arch-based, build the official 4.12.2 - to check/confirm that it is not distro-related I will start playing in couple of hours, now I am at work... Pawel. wt.,

On 09/03/2020 14:25, Andreas Hauffe via samba wrote: > [global] > ??????? dedicated keytab file = /etc/krb5.keytab > ??????? kerberos method = secrets and keytab Why the dedicated keytab ? > workgroup = ILRW > ??????? idmap config dom : range = 10000-9999999 > ??????? idmap config dom : backend = rid > ??????? idmap config subdom : range = 3000-9999 > ??????? idmap config

On 10/03/2020 08:03, Andreas Hauffe via samba wrote: > We have a kerberized NFS4 running on that machine, too. I do hope that you are not resharing the NFS share(s) via Samba, that way lies madness ;-) Try this smb.conf: [global] ??????? workgroup = SUBDOM ??????? realm = SUBDOM.DOM.EXAMPLE.COM ??????? security = ADS ??????? bind interfaces only = Yes ??????? interfaces = lo enp1s0f0

@Andrew Unfortunately I didn't make notes on exact time of errors when doing my tests... But, I've spend last couple of hours on building samba from master: - Have made a clone of the virtual machine, with new name and network interface mac address, and a new dynamic IP assigned by my router. - Uninstalled Arch packages: samba, smbclient and cifs-tools (depending on

Forgot to add the tcpdump command used: tcpdump -p -s 0 -n -w /root/tcpdump_all.txt Pawel. wt., 5 maj 2020 o 00:01 pavlos <pavlos.audiofreak at gmail.com> napisa?(a): > OK, have repeated the test: > > - samba logs: > http://www.mediafire.com/file/jy4qcyvqg6z39zu/logs.tar.gz/file > - tcpdump log: >

Hi all, I am experiencing something similar to what Andreas described on march 9th. Since upgrade to samba-4.12.0, users can sometimes have errors on accessing shares. Errors can be different, most often NT_STATUS_SHARING_VIOLATION, but also "Invalid handle". Just restarting smbd fixes the issue, for a while. The server serves six shares: one or a few may be locked, the other are

Hi Volker, Jermey, and the Community, To be clear: I didn't analyze your code, I don't know structures of Samba, definitely I am not a person to judge and blame anybody :) I am sure that there were reasons, you wanted to clarify some issues around controlling share mode flags. And it's rather everything OK with your code. Even more: most probably your change revealed a bug in Win7,

@Rowland, Installing and changing to LTS kernel 5.4.38-1-lts doesn't help. Downgrading samba and smbclient to 4.11.3 DOES help. @Andrew, let me first clean up with kernel/samba versions, set log level to 10 and log limit to 0, delete all logs and repeat the whole exercise. Please advice how to get a network capture, I am not that expert... Regards, Pawel. pon., 4 maj 2020 o 22:50 Andrew

Hi After Fedora 31 upgrade to F32, samba started to break after more clients connect (up to 10). No config change, no clients change, no sharing changes.? F31 had smb 4.11.7 and was working fine after restarting service it works for a while then it breaks with various messages for each client I tried removing some old parameters (no help), I had mounted ssd drive into folder structure and I

@Andrew, Samba master - what do you mean? A clean compile and install from genuine samba.org sources? As a matter of fact, I was thinking about it.... Let me do the tests now, with tcpdump. Will send some logs and outputs later on. You've asked previously - this is the smbstatus, already on the latest kernel/samba versions. The problem is persistent, no wonder... [root at arch1 /]#

On 5/25/2017 12:07 PM, Robert Moskowitz wrote: > > > On 05/25/2017 11:22 AM, Bowie Bailey wrote: >> On 5/25/2017 10:04 AM, Robert Moskowitz wrote: >>> >>> >>> On 05/25/2017 09:32 AM, Leon Fauster wrote: >>>>> Am 25.05.2017 um 15:27 schrieb Robert Moskowitz >>>>> <rgm at htt-consult.com>: >>>>>

This is the smbstatus with 4.11.x. No problems on clients. Using LC_ALL=C because have Polish locale set up. [root at arch1 ~]# LC_ALL=C smbstatus Samba version 4.11.3 PID Username Group Machine Protocol Version Encryption Signing