[Samba] Samba mount error after server packages update

Rowland penny rpenny at samba.org
Wed Jul 15 18:19:09 UTC 2020

On 15/07/2020 18:51, andy via samba wrote:
> Hello,
> I've a virtual machine working as a samba server ("clear linux release 28640", whose relevant information are in the attached file "server_clearmi_28640.txt").
What I cannot understand is why portions of your smb.conf are only 
really relevant on an NT4-style PDC or an AD DC/member and the smb.conf 
is for a standalone server ?
> The samba client is an android 4 virtual machine (https://www.android-x86.org/releases/releasenote-4-4-r5.html).
> I can succesfully mount samba shares from the android "terminal emulator", with the following command, for example:
> ---
> # android_share
> su root busybox mount -v -t cifs \
> -o username=andy,password=pass,nounix,nosuid,nodev,noexec,noatime,gid=10028,uid=10023,rw \
> // /sdcard/android_share
> ---
> So far so good.
> Now I have just upgraded the server machine to "clear linux release 33490". Only the full system upgrade has been performed, with no other changes.
> After the upgrade, the samba version has been updated from 4.10.0 to 4.12.3.
> The samba server starts correctly (and it works correctly with windows clients), but when I try to mount the filesystem on the android client (with the same command shown before), I get the following error:
> "operation not supported on transport endpoint".
> I don't understand if this is a bug in the new server, or if the updated samba release requires different parameters in the smb.conf file.
> Any suggestion?
> Andy

I would hazard a guess that your Android client needs updating, Samba 
turned SMBv1 off at 4.11.0, so it now only uses SMBv2 or SMBv3


More information about the samba mailing list