[Samba] smb2 create

[Rowland Penny]

On Mon, 16 Jul 2018 10:21:21 -0400
rac8006 at aol.com wrote:

> 
> 
>  If it is only a windows problem.  Wouldn't windows try to do this
> sequence to all shared devices? This only happens to the devices
> running 4.3.11.  Each device has a Public folder mapped to a windows
> drive letter.  There are 5 samba shares 
> 
> mapped on the windows PC.  Two running 4.3.11 and the rest running an
> older version. The smbd log show that it is doing something with
> Public/. directory.  The strace shows
> geteuid32()                             = 0
> getegid32()                             = 0 setgroups32(3, [1000,
> 501, 2000])       = 0 setresgid32(-1, 1000, -1)               = 0
> getegid32()                             = 1000
> setresuid32(1002, 1002, -1)             = 0
> geteuid32()                             = 1002
> stat64(".", {st_mode=S_IFDIR|0777, st_size=4096, ...}) = 0
> stat64(".", {st_mode=S_IFDIR|0777, st_size=4096, ...}) = 0
> getxattr(".", "system.posix_acl_access", 0xbe92eee0, 132) = -1
> ENODATA (No data available) stat64(".", {st_mode=S_IFDIR|0777,
> st_size=4096, ...}) = 0 getxattr(".", "system.posix_acl_default",
> 0xbe92eee0, 132) = -1 ENODATA (No data available) stat64(".",
> {st_mode=S_IFDIR|0777, st_size=4096, ...}) = 0
> 
> 
> I'm not well versed on samba and smb protocol. I'm not looking for a
> fix to 4.3.11.  I'm trying to understand what is happening.
> All of the mapped shares are working.
> 

No, it doesn't mean it is only happening with 4.3.11, it means it is
only being reported on 4.3.11, it is very probably happening on your
4.0.0 machine, it just isn't getting reported.

What ever is happening, it is originating from your Windows 10 machine,
neither the 4.0.0 or any 4.3.11 Samba machine is starting it, it is all
coming from the Windows 10 machine, Samba is just reacting to it.

If something does need fixing on your Samba machine (and I am not
saying anything does need fixing), you have less than no chance of
getting it fixed. As far as Samba is concerned, the only supported
Samba versions are 4.6.x, 4.7.x and 4.8.x and, in a matter weeks, 4.6.x
will go EOL when 4.9.0 is released.

You need to find what is connecting to Samba from the Windows 10 PC and
fix this, your problem seems to be a Windows problem and not a Samba
problem.

Rowland