samba-4.14 and previous versions works just fine, including latest 4.14.12. But since 4.15 I'm unable to connect to my server using Fx (https://play.google.com/store/apps/details?id=nextapp.fx.rk). Even with `log level = 10` there is nothing in logs when Fx is trying to connect. Another client (Debian, using `mount -t cifs -o vers=3.02`) works just fine both with 4.14 and 4.15. I've checked both a changelog https://www.samba.org/samba/history/samba-4.15.0.html and open bugs https://bugzilla.samba.org/buglist.cgi?no_redirect=0&quicksearch=4.15 but doesn't see anything related. I'm stuck now, because I've no idea how to debug this without logs or anything like that. tcpdump's output isn't really helpful. Here is my smb.conf: [global] max protocol = SMB3 workgroup = WORKGROUP server string = Samba Server hosts allow = 127. 192.168.2. 192.168.3. guest account = powerman map to guest = bad user guest only = yes smb passwd file = /etc/samba/private/smbpasswd log file = /var/log/samba/log.%m max log size = 50 log level = 10 socket options = IPTOS_LOWDELAY TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 interfaces = 192.168.2.0/24 remote announce = 192.168.2.255 domain master = yes preferred master = yes wins support = yes dns proxy = yes dos charset = 866 unix charset = UTF-8 follow symlinks = no [homes] comment = Home Directories browseable = no writable = no [TEMPORARY] comment = Writable Temp path = /mnt/tmp public = yes writeable = yes printable = no create mask = 0660 directory mask = 0775 force create mode = 0660 force directory mode = 0775 Is there any ideas how to debug this issue? Or is there any other android file managers with SMB support? I had to switch to Fx some time ago because of some security-related change in samba, which breaks all other android clients I used because they implement too outdated SMB protocol, but Fx uses some newer protocol…
