external_storage: smb 2/3 setting but logging a lot of failed smb1 connections

How to use GitHub

• Please use the 👍 reaction to show that you are affected by the same issue.
• Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
• Subscribe to receive notifications on status change and new comments.

Steps to reproduce

Nextcloud produces a lot of SMB1 warnings.

1. create SMB/CIFS Share
2. enable App "External storage support"
3. view samba logfile
4. receive one correct info and hundreds warnings with SMB1

User [xxxxx] from [xxxxx(127.0.0.1)] via [CIFS(SMB3)] accessed shared folder [xxx].
Host [127.0.0.1] failed to connect via [SMB] due to [SMB1 not permitted].
Host [127.0.0.1] failed to connect via [SMB] due to [SMB1 not permitted].
Host [127.0.0.1] failed to connect via [SMB] due to [SMB1 not permitted].
Host [127.0.0.1] failed to connect via [SMB] due to [SMB1 not permitted].
Host [127.0.0.1] failed to connect via [SMB] due to [SMB1 not permitted].
...

5. After disable App "External storage support" no infos or warning appears.

Expected behaviour

Nextcloud "app" external_storage: should not try to connect with smb1
External Storage should first to connect with smb3 and after success, not with smb1

Actual behaviour

Inside "External storage support" there is a problem with smb Connection.

On synology nas terminal with
smbstatus
I get only SMB3_00 connection
SMB3 client and servers works on Synology Diskstation.

But after enable App "External storage support" one connection with smb3 start and a lot of denied connections with smb1.

I can receive files from the samba share.
The samba share is read only.

Server configuration

Operating system:
Synology Nas

Web server:
Apache 2.4

Database:
mysql 10.3.29

PHP version:
7.4.9

Nextcloud version: (see Nextcloud admin page)
Nextcloud 22.2.0

Updated from an older Nextcloud/ownCloud or fresh install:
Nextcloud 22.1.0

Where did you install Nextcloud from:
https://download.nextcloud.com/server/releases/nextcloud-*.tar.bz2

Signing status:
No errors have been found.

List of activated apps:

Nextcloud configuration:

If you have access to your command line run e.g.:
sudo -u www-data php occ config:list system
from within your Nextcloud installation folder

or 

Insert your config.php content here. 
Make sure to remove all sensitive content such as passwords. (e.g. database password, passwordsalt, secret, smtp password, …)

Are you using external storage, if yes which one: local/smb/sftp/...

smb

samba settings

min protocol=SMB2
max protocol=SMB3
client min protocol=SMB2
client max protocol=SMB3

Are you using encryption: yes/no
no

Are you using an external user-backend, if yes which one: LDAP/ActiveDirectory/Webdav/...
no

With access to your command line run e.g.:
sudo -u www-data php occ ldap:show-config
from within your Nextcloud installation folder

Without access to your command line download the data/owncloud.db to your local
computer or access your SQL server remotely and run the select query:
SELECT * FROM `oc_appconfig` WHERE `appid` = 'user_ldap';


Eventually replace sensitive data as the name/IP-address of your LDAP server or groups.

Client configuration

Its a server issue

Browser:

Operating system:

Logs

Web server error log

Insert your webserver log here

Nextcloud log (data/nextcloud.log)

Insert your Nextcloud log here

Browser log

Insert your browser log here, this could for example include:

a) The javascript console log
b) The network log
c) ...

Start with the files_external app's SMB connection path and reproduce the behavior while monitoring the Samba log and smbstatus. Compare the configured SMB2/SMB3 limits with the attempted SMB1 connections; done means a successful SMB3 connection no longer produces repeated SMB1 warnings.