The Samba-Bugzilla – Bug 7392
File Server: Samba 4 - SMB2 Win7
Last modified: 2012-10-24 21:36:08 UTC
Running Samba 4 Alpha12, which was just downloaded via git yesterday. OS is Fedora 12, latest version.
Client is Windows 7 Ultimate version 6.1.7600
Problem: Large files copied to/from the samba SMB2 share cause "Network Error" message in Windows 7. "There is a problem accessing X:\" "Make sure you are connected to the network and try again".
I am able to browse the files.
Small files < 1MB usually has no problems. After looking at a packet capture it seems that the samba server shuts down on large transfers by transmitting nothing but TCP resets to the client, seems to be in absence of a 'write reply' from the server to the client. It happens on reads as well.
Setup was clean Fedora 12 install, latest Samba 4 install followed HowTo guide. Using Samba as a member of 2003 domain. Winbind and Pam integration in use. All works well, other than the SMB2 file transfers back and forth. SMB1 has no issues.
To duplicate try a 10+ MB .mp3. If you play the file from the samba share all is well, as it is streaming, but if you do a copy and a bulk file transfer begins, you'll see the TCP resets and the connection dies. This is just an example. I can send the capture if needed. Any ideas?
Well, I hope you know that the s4 SMB2 server is highly experimental - and not supported yet on a regular way. If you need reliable data transfer then please use SMB1.
Any improvements here?
The s3fs (default) file server in 4.0.0 will support SMB2/3