currently there seem to be a bug on newer SMB-clients, like Windows 10 or Windows Server 2012 R2, while receiving files from a smbd-server which runs at default config.
So on the network-side the Windows client tend to send a TCP RST while transferring. The Windows client shows up the error 0x8007003b. Else the transfer-window stalls for several seconds and bumps up the progress for several percents.
If the server capabilitys are reduced to "NT1" ("server max protocol") the issue disappears.
Are you sure this is a Samba bug ? See here:
for the same error seen in a Windows -> Windows environment.
Actually I'm pretty sure. We've replaced the thin client which was running the smbd with a windows 10 to access the domains dfs system with it, and the copy with of the same data over the same connection work fluently and very reliable.
We also tried to copy the same data from the samba server and this work as well.
So these ones work:
S2003 ---> smbd (default config)
2012r2 <--- win10
2012r2 ---> smbd (with maxp nt1)
This one not:
2012r2 ---> smbd (default config)
I am also affected, I have problems with Windows 8/8.1/10 workstations trying to send "big" files (more than 5MiB) to my samba server, disabling 2.0/3.0 dialect in Windows solves the issue. It tends to happen over low performance links like 500kbps-5000kbps. Can somebody confirm where the issue is?
Sorry for double post, there is very good description:
I've exactly the same symptoms.
Same problem using Cisco AnyConnect VPN and ~0,6 Mbps upload speed.
My test results:
Client -> Server (upload)
Windows 7/10 -> Windows Srv 2012R2 : OK
Windows 7/10 -> Samba version 4.3.11-Ubuntu : error 0x8007003b
Mac OS X -> Samba version 4.3.11-Ubuntu : OK
Same here, i can reproduce this problem with the following setup
* Windows 8.1 client (KVM) with reduced interface bandwidth
* Linux with samba 4.6.1-1 and a "standard" config.
When trying to copy a "large" file (30MB) from the server to the client, the client fails with Error 0x8007003b. I can see the TCP RST form the client in the network trace.
Copying a 3MB file works, though.
Workaround for me was
Set-SmbClientConfiguration -SessionTimeout 600
on the windows machine, but i am not sure what implications this has.
Attached are the log.samba log.smbd (level 99) and the tcp dump from the failed file copy operation (name of the test file was mytestfile.txt).
Created attachment 13898 [details]
Created attachment 13899 [details]
Created attachment 13900 [details]