[Samba] Samba mount error after server packages update

[Andrew Walker]

On Wed, Jul 15, 2020 at 2:19 PM Andrew Walker <walker.aj325 at gmail.com>
wrote:

>
>
> On Wed, Jul 15, 2020 at 1:52 PM andy via samba <samba at lists.samba.org>
> 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").
>>
>> 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
>> \
>> //192.168.213.133/android_share /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--
>> To unsubscribe from this list go to the following URL and read the
>> instructions:  https://lists.samba.org/mailman/options/samba
>
>
> In samba 4.11 the default server minimum protocol was increased to
> SMB3_02. Perhaps your client requires SMB1 (NT1)?
>
> https://www.samba.org/samba/docs/current/man-html/smb.conf.5.html#SERVERMINPROTOCOL
>

Correction: SMB2_02.