-   Linux - Networking (
-   -   Problem with samba large files copy Win10 to Ubuntu (

Sz4r1ej 06-21-2020 07:23 PM

Problem with samba large files copy Win10 to Ubuntu

I've finished setting up and run samba service to which i can successfully connect from Win10 machine using file explorer however trying to copy anything that is at least couple of hundreds of MBs results in unexpected network error 0x8007003B and log entry :

become_local_master_browser: Error - cannot find server FTPADMIN-VIRTUAL-MACHINE in workgroup WORKGROUP on subnet

What's puzzling is that copying any small files goes through without a problem.

I've enabled SMB 1.0 CIFS client on windows side but it didn't do anything.
My samba config is :

        browsable = yes
        writeable = yes
        comment = Samba on Ubuntu
        path = /media/ftpadmin/Share Data
        available = yes
        read only = no
        public = yes
# Sample configuration file for the Samba suite for Debian GNU/Linux.
# This is the main Samba configuration file. You should read the
# smb.conf(5) manual page in order to understand the options listed
# here. Samba has a huge number of configurable options most of which
# are not shown in this example
# Some options that are often worth tuning have been included as
# commented-out examples in this file.
#  - When such options are commented with ";", the proposed setting
#    differs from the default Samba behaviour
#  - When commented with "#", the proposed setting is the default
#    behaviour of Samba but the option is considered important
#    enough to be mentioned here
# NOTE: Whenever you modify this file you should run the command
# "testparm" to check that you have not made any basic syntactic
# errors.

#======================= Global Settings =======================

        server role = standalone server
        passwd program = /usr/bin/passwd %u
        passdb backend = tdbsam
        encrypt passwords = yes
        max log size = 1000
        usershare allow guests = yes
        map to guest = bad user
        unix password sync = yes
        syslog = 0
        log file = /var/log/samba/log.%m
        workgroup = WORKGROUP
        dns proxy = no
        panic action = /usr/share/samba/panic-action %d
        obey pam restrictions = yes
        server string = %h server (Samba, Ubuntu)
        pam password change = yes
        null passwords = yes
        ntlm auth = yes
        passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .

## Browsing/Identification ###

# Change this to the workgroup/NT-domain name your Samba server will part of

# server string is the equivalent of the NT Description field

# Windows Internet Name Serving Support Section:
# WINS Support - Tells the NMBD component of Samba to enable its WINS Server
#  wins support = no

# WINS Server - Tells the NMBD components of Samba to be a WINS Client
# Note: Samba can be either a WINS Server, or a WINS Client, but NOT both
;  wins server = w.x.y.z

# This will prevent nmbd to search for NetBIOS names through DNS.

#### Networking ####

# The specific set of interfaces / networks to bind to
# This can be either the interface name or an IP address/netmask;
# interface names are normally preferred
;  interfaces = eth0

# Only bind to the named interfaces and/or networks; you must use the
# 'interfaces' option above to use this.
# It is recommended that you enable this feature if your Samba machine is
# not protected by a firewall or is a firewall itself.  However, this
# option cannot handle dynamic or non-broadcast interfaces correctly.
;  bind interfaces only = yes

#### Debugging/Accounting ####

# This tells Samba to use a separate log file for each machine
# that connects

# Cap the size of the individual log files (in KiB).

# If you want Samba to only log through syslog then set the following
# parameter to 'yes'.
#  syslog only = no

# We want Samba to log a minimum amount of information to syslog. Everything
# should go to /var/log/samba/log.{smbd,nmbd} instead. If you want to log
# through syslog you should set the following parameter to something higher.

# Do something sensible when Samba crashes: mail the admin a backtrace

####### Authentication #######

# Server role. Defines in which mode Samba will operate. Possible
# values are "standalone server", "member server", "classic primary
# domain controller", "classic backup domain controller", "active
# directory domain controller".
# Most people will want "standalone sever" or "member server".
# Running as "active directory domain controller" will require first
# running "samba-tool domain provision" to wipe databases and create a
# new domain.

# If you are using encrypted passwords, Samba will need to know what
# password database type you are using. 

# This boolean parameter controls whether Samba attempts to sync the Unix
# password with the SMB password when the encrypted SMB password in the
# passdb is changed.

# For Unix password sync to work on a Debian GNU/Linux system, the following
# parameters must be set (thanks to Ian Kahan <<> for
# sending the correct chat script for the passwd program in Debian Sarge).

# This boolean controls whether PAM will be used for password changes
# when requested by an SMB client instead of the program listed in
# 'passwd program'. The default is 'no'.

# This option controls how unsuccessful authentication attempts are mapped
# to anonymous connections

########## Domains ###########

# The following settings only takes effect if 'server role = primary
# classic domain controller', 'server role = backup domain controller'
# or 'domain logons' is set

# It specifies the location of the user's
# profile directory from the client point of view) The following
# required a [profiles] share to be setup on the samba server (see
# below)
;  logon path = \\%N\profiles\%U
# Another common choice is storing the profile in the user's home directory
# (this is Samba's default)
#  logon path = \\%N\%U\profile

# The following setting only takes effect if 'domain logons' is set
# It specifies the location of a user's home directory (from the client
# point of view)
;  logon drive = H:
#  logon home = \\%N\%U

# The following setting only takes effect if 'domain logons' is set
# It specifies the script to run during logon. The script must be stored
# in the [netlogon] share
# NOTE: Must be store in 'DOS' file format convention
;  logon script = logon.cmd

# This allows Unix users to be created on the domain controller via the SAMR
# RPC pipe.  The example command creates a user account with a disabled Unix
# password; please adapt to your needs
; add user script = /usr/sbin/adduser --quiet --disabled-password --gecos "" %u

# This allows machine accounts to be created on the domain controller via the
# SAMR RPC pipe. 
# The following assumes a "machines" group exists on the system
; add machine script  = /usr/sbin/useradd -g machines -c "%u machine account" -d /var/lib/samba -s /bin/false %u

# This allows Unix groups to be created on the domain controller via the SAMR
# RPC pipe. 
; add group script = /usr/sbin/addgroup --force-badname %g

############ Misc ############

# Using the following line enables you to customise your configuration
# on a per machine basis. The %m gets replaced with the netbios name
# of the machine that is connecting
;  include = /home/samba/etc/smb.conf.%m

# Some defaults for winbind (make sure you're not using the ranges
# for something else.)
;  idmap uid = 10000-20000
;  idmap gid = 10000-20000
;  template shell = /bin/bash

# Setup usershare options to enable non-root users to share folders
# with the net usershare command.

# Maximum number of usershare. 0 (default) means that usershare is disabled.
;  usershare max shares = 100

# Allow users who've been granted usershare privileges to create
# public shares, not just authenticated ones

#======================= Share Definitions =======================

# Un-comment the following (and tweak the other settings below to suit)
# to enable the default home directory shares. This will share each
# user's home directory as \\server\username
;  comment = Home Directories
;  browseable = no

# By default, the home directories are exported read-only. Change the
# next parameter to 'no' if you want to be able to write to them.
;  read only = yes

# File creation mask is set to 0700 for security reasons. If you want to
# create files with group=rw permissions, set next parameter to 0775.
;  create mask = 0700

# Directory creation mask is set to 0700 for security reasons. If you want to
# create dirs. with group=rw permissions, set next parameter to 0775.
;  directory mask = 0700

# By default, \\server\username shares can be connected to by anyone
# with access to the samba server.
# Un-comment the following parameter to make sure that only "username"
# can connect to \\server\username
# This might need tweaking when using external authentication schemes
;  valid users = %S

# Un-comment the following and create the netlogon directory for Domain Logons
# (you need to configure Samba to act as a domain controller too.)
;  comment = Network Logon Service
;  path = /home/samba/netlogon
;  guest ok = yes
;  read only = yes

# Un-comment the following and create the profiles directory to store
# users profiles (see the "logon path" option above)
# (you need to configure Samba to act as a domain controller too.)
# The path below should be writable by all users so that their
# profile directory may be created the first time they log on
;  comment = Users profiles
;  path = /home/samba/profiles
;  guest ok = no
;  browseable = no
;  create mask = 0600
;  directory mask = 0700

  comment = All Printers
  browseable = no
  path = /var/spool/samba
  printable = yes
  guest ok = no
  read only = yes
  create mask = 0700

# Windows clients look for this share name as a source of downloadable
# printer drivers
  comment = Printer Drivers
  path = /var/lib/samba/printers
  browseable = yes
  read only = yes
  guest ok = no
# Uncomment to allow remote administration of Windows print drivers.
# You may need to replace 'lpadmin' with the name of the group your
# admin users are members of.
# Please note that you also need to set appropriate Unix permissions
# to the drivers directory for these users to have write rights in it
;  write list = root, @lpadmin

Can anyone point me in the right direction?
Obviously I'm missing something.
At first I thought it's permission related but then small files went through fine.

The share is an attached disk to a VMWARE box running Ubuntu 18.04
The file system on that drive is vfat
Size approx 2TB

ferrari 06-21-2020 08:21 PM

I would avoid reverting to SMBv1 at all costs. Assuming that you're using a recent samba version SMBv2 or SMBv3 is the way to go.

I don't have a definitive answer here, but I have seen discussions about the Windows firewall causing issues like this. Some examples...

Sz4r1ej 06-22-2020 02:05 AM

I've tried switching firewall and eset32 off but still the transfers failed.
The SMB1 was a last ditch effort but that didn't make a difference too.

I've run out of ideas

pan64 06-22-2020 04:46 AM

I can guess only: become_local_master_browser may mean you have two (or more) AD configured. For example on in Windows and another one using samba. And they conflict with each other.
But it is only a guess. Another reason can be if your file is too big. You can’t transfer files any larger than 4 GB to a FAT32 hard drive.
0x8007003B is a windows error, so probably the error is windows related (so you cannot solve it by configuring samba).

ferrari 06-22-2020 04:52 AM

A samba bug report describing similar behaviour. Comment #6 mentions a possible workaround that might be worth trying...

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.
That seems to me to be an extreme value (600s), but perhaps you could try experimenting with reasonable timeout values that mitigate against this error.

It seems that the connection speed between hosts can be a factor here, so you may need to check that as well.

BTW, you might find WinSCP is a viable option for copying large files to/from Windows to your Linux machine(s) using the SFTP protocol.

That's about all I can offer here.

Sz4r1ej 06-22-2020 04:52 AM

The file size varied from 1.1 to 2.5 GB and all failed.
if it was AD and therefore permissions why would it allow to copy over small files?

I'm also running CrushFTP server on that box and that has no problems with accepting and writing large files.

sigh ... got to love mixed environments

ferrari 06-22-2020 04:54 AM


I'm also running CrushFTP server on that box and that has no problems with accepting and writing large files.

sigh ... got to love mixed environments
Similar thoughts with my suggestion to use WinSCP. :)

All times are GMT -5. The time now is 04:31 AM.