similar to: Win7 clients problem after upgrading samba file server to 4.12 on Arch

Hi Rowland, User configuration: [root at arch1 /]# pdbedit -L nobody:65534:Nobody root:0: ala:1000: [root at arch1 /]# cat /etc/passwd root:x:0:0::/root:/bin/bash bin:x:1:1::/:/usr/bin/nologin daemon:x:2:2::/:/usr/bin/nologin mail:x:8:12::/var/spool/mail:/usr/bin/nologin ftp:x:14:11::/srv/ftp:/usr/bin/nologin http:x:33:33::/srv/http:/usr/bin/nologin

@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

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

@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 /]#

Logs are here: http://www.mediafire.com/file/qqwfkf3rsuv081k/logs.tar.gz/file 1. I have stopped smb and nmb services, 2. deleted all samba logs, 3. addied 'log level - 10' to smb.conf, 4. started services, 5. performed few tests until some problems appeared, 6. stopped smb and nmb services 7. and grabbed all logs. As this is test environment - nothing to sanitize. All logs unchanged. For

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: >

On 04/05/2020 18:28, pavlos via samba wrote: > Hi All, > I have a simple home network - no domain controller, no DNS, just DHCP on > my router. > I have simple samba file server built on Arch Linux, with single share > exposed and couple of client computers, some ot them running Win7 x32 > (embedded, not-upgradeable), some others with different Win or Linux > systems. All of

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

'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

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 Sat, 2020-05-09 at 18:33 +0200, pavlos via samba wrote: > > Ralph, good news! > > Applying the patch into the original source code of the 'open.c' file > removes the observed misbehavior. > So yes, you've touched and addressed the root-cause of the problem > on my side. MANY THANKS! > Double checked that from two WIn7 stations - x86 and x64, also from my

@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

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

sob., 9 maj 2020 o 14:37 Ralph Boehme <slow at samba.org> napisa?(a): > To be clear: if you're running into this issue that I'm seeing in the > code, then this is *not* a client side bug. It's a server bug that only > gets triggered by a specific access pattern. Likely Win 7 has a > different pattern compared to other Windows versions which explains why > you only

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,

OK, have repeated the test: - samba logs: http://www.mediafire.com/file/jy4qcyvqg6z39zu/logs.tar.gz/file - tcpdump log: http://www.mediafire.com/file/qzex3kxf2vzd87n/tcpdump_all.tar.gz/file The tcpdump log covers the whole period of testing time, from starting to stopping smb and nmb services. Previous logs deleted from mediafire. Now waiting for any advice from you, or let's

Currently 4.12.3 is scheduled for 19 May: https://wiki.samba.org/index.php/Release_Planning_for_Samba_4.12#Samba_4.12.3 As Ralph has a patch and you have confirmed it odds are pretty good this will be in there. Andrew Bartlett On Sun, 2020-05-10 at 00:01 +0200, pavlos wrote: > Hi, > did you already decide if, and - if yes - how and when the patch will be embedded into the mainstream?

Did you note the very second you saw the offending error message? That time would help a lot, I can't see the error packet. But all that said, I'm not the person who needs to look at this, I just hoped I could help get you the information they would need. The only other suggestion, other than the build on master in the hope this has already been fixed, is if you do find you can build

On Mon, 2020-05-04 at 23:18 +0200, pavlos wrote: > @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.... Yes. > 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

Thanks for getting back to us, On Mon, 2020-05-04 at 22:57 +0200, pavlos via samba wrote: > @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