samba - May 2020 - 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
nobody:x:65534:65534:Nobody:/:/usr/bin/nologin
dbus:x:81:81:System Message Bus:/:/usr/bin/nologin
systemd-journal-remote:x:982:982:systemd Journal Remote:/:/usr/bin/nologin
systemd-network:x:981:981:systemd Network Management:/:/usr/bin/nologin
systemd-resolve:x:980:980:systemd Resolver:/:/usr/bin/nologin
systemd-timesync:x:979:979:systemd Time Synchronization:/:/usr/bin/nologin
systemd-coredump:x:978:978:systemd Core Dumper:/:/usr/bin/nologin
uuidd:x:68:68::/:/usr/bin/nologin
dhcpcd:x:977:977:dhcpcd privilege
separation:/var/lib/dhcpcd:/usr/bin/nologin
ntp:x:87:87:Network Time Protocol:/var/lib/ntp:/bin/false
avahi:x:976:976:Avahi mDNS/DNS-SD daemon:/:/usr/bin/nologin
ala:x:1000:985::/home/ala:/bin/bash
git:x:975:975:git daemon user:/:/usr/bin/git-shell

[root at arch1 /]# id
uid=0(root) gid=0(root) grupy=0(root)

[ala at arch1 ~]$ id
uid=1000(ala) gid=985(users)
groups=985(users),3(sys),98(power),988(storage),998(wheel)


All clients are connecting either anonymously read-only which leverages the
'nobody' samba user, or using 'ala' user/pwd. Both have same
problems.

No local 'ala' users on any client machine. In Windows login dialog I am
supplying username as '192.168.1.115\ala' and the defined password
(....115
is the IP address of the test samba server).

I have also put 'log level = 10' to your smb.conf, but the hiccup on
Win7
remains. As I said - the stupid message box in Windows pops up randomly.
This short exercise has produced about 100 KB of compressed logs. How might
I share them with you and all in the mailing list?

Thanks for your attention!
Regards, Pawel.


pon., 4 maj 2020 o 20:10 Rowland penny via samba <samba at
lists.samba.org>
napisa?(a):
> 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 the client are connecting to the share using the same
> > user/pwd, set up previously on my Arch server.
> > The configuration was running without any issues for couple of years
and
> > through all upgrades (rolling distro) until the last samba upgrade
from
> > 4.11.3 to 4.12.3.
> > Now I have problems with my Win7 clients, and only with those clients:
> the
> > message box "*The process cannot access the file because it is
being used
> > by another process.*" popping unexpectedly in very random
situations.
> >
> > I have also installed new, fresh and minimal Arch Linux in Virtualbox,
> > added just the newest samba package, set up the simplest share with
> > smb.conf as follows. The same problems with Win7 clients using the new
> > share.
> >
> > ------------------------------------
> > [global]
> >   netbios name = ARCH1
> >   workgroup = WORKGROUP
> >   server string = TestSambaServer
> >   server role = standalone
> >   security = user
> >   guest account = nobody
> >   map to guest = bad user
> >   log file = /var/log/samba/logconf.%m
> >   max log size = 50
> >
> > [nas]
> >    comment = some funny stuff
> >    path = /nas
> >    public = yes
> >    writable = no
> >    printable = no
> >    create mask = 0777
> >    directory mask = 0777
> >    write list = @wheel
> > ------------------------------------
> >
> > As you can see - anyone should be able to connect and read, only users
> > belonging to the wheel group are able to login with R/W rights.
> >
> > I have also asked similar question to the marvelous Arch community,
but
> > got nothing but a few 'mee-too' posts...
> >
> > Can you, please, help me in fixing this?
> >
> >     - Is it a bug symptom?
> Possibly
> >     - Or, is it a new 'feature' which i missed when reading
> >     release information? Maybe some defaults in smb.conf have changed
> and I
> >     should adjust them properly?
> Don't think so'
> >     - Or, maybe I should adjust something in Win7 configuration?
> >     - Or, maybe you have definitely abandoned any Win7 support and I
> should
> >     be in a deep ...trouble now?
>
> It could possibly have something to do with SMBv1, but I would have
> expected it to be a problem with 4.11.x as well.
>
> You are running Samba as a standalone server.
>
> I take it you created a few users and made them members of the wheel
> group, but did you make them Samba users with 'smbpasswd -a
username' ?
>
> All other users that connect, do not exist on the computer ?
>
> If so, then I would expect it still to work.
>
> Can you please add 'log level = 10' to your smb.conf and see if
anything
> pops out.
>
> Rowland
>
>
>
>
> --
> To unsubscribe from this list go to the following URL and read the
> instructions:  https://lists.samba.org/mailman/options/samba
>

On 04/05/2020 20:21, pavlos wrote:
>
> All clients are connecting either anonymously read-only which 
> leverages the 'nobody' samba user, or using 'ala' user/pwd.
Both have
> same?problems.
>
> No local 'ala' users on any client machine. In Windows login dialog
I
> am supplying username?as '192.168.1.115\ala' and the defined
password
> (....115 is the IP address of the test samba server).
Try it without the the IP i.e. just 'ala'
>
> I have also put 'log level = 10' to your smb.conf, but the hiccup
on
> Win7 remains. As I said - the stupid message box in Windows pops up 
> randomly.
This could be a Windows error, but something might have changed in Samba 
that is now causing it.
> This short exercise has produced about 100 KB of compressed logs. How 
> might I share them with you and?all in the mailing list?
Post them somewhere (after sanitising them) and then provide a link to it.

Rowland

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

   - 192.168.1.103, netbios name 'saloon' - Win7x32 client
   - 192.168.1.108, netbios name 'attic' - win7x32 client
   - 192.168.1.115, hostname 'arch1' - the test Samba server, Arch Linux
   5.6.10-arch1-1

Regards, Pawel.

pon., 4 maj 2020 o 21:45 Rowland penny via samba <samba at
lists.samba.org>
napisa?(a):
> On 04/05/2020 20:21, pavlos wrote:
> >
> > All clients are connecting either anonymously read-only which
> > leverages the 'nobody' samba user, or using 'ala'
user/pwd. Both have
> > same problems.
> >
> > No local 'ala' users on any client machine. In Windows login
dialog I
> > am supplying username as '192.168.1.115\ala' and the defined
password
> > (....115 is the IP address of the test samba server).
> Try it without the the IP i.e. just 'ala'
> >
> > I have also put 'log level = 10' to your smb.conf, but the
hiccup on
> > Win7 remains. As I said - the stupid message box in Windows pops up
> > randomly.
> This could be a Windows error, but something might have changed in Samba
> that is now causing it.
> > This short exercise has produced about 100 KB of compressed logs. How
> > might I share them with you and all in the mailing list?
>
> Post them somewhere (after sanitising them) and then provide a link to it.
>
> Rowland
>
>
>
>
> --
> To unsubscribe from this list go to the following URL and read the
> instructions:  https://lists.samba.org/mailman/options/samba
>