In my case I'm running a Samba server on my Tumbleweed desktop. Below is a copy of my smb.conf Globals and scanner-upload Share section. I have confirmed I'm able to connect to my shares via SMB2 just not SMB1 [global] workgroup = WORKGROUP passdb backend = tdbsam printing = cups printcap name = cups printcap cache time = 750 cups options = raw map to guest = Bad User logon path = \\%L\profiles\.msprofile logon home = \\%L\%U\.9xprofile logon drive = P: usershare allow guests = No add machine script = /usr/sbin/useradd -c Machine -d /var/lib/nobody -s /bin/false %m$ security = user wins support = yes usershare max shares = 100 netbios name = LINUX-THOR client min protocol = NT1 server min protocol = NT1 local master = yes preferred master = yes [scanner-upload] inherit acls = Yes path = /iDrive/scanner-upload read only = No follow symlinks = Yes browseable = yes guest ok = no create mask = 0600 directory mask = 0700 On 11/4/22 09:14, Rainer Klier wrote:
Am 04.11.22 um 14:50 schrieb Larry Len Rainey:
It used to support SMB1 if the /etc/samba/smb.conf had the line "min protocol = NT1" - has that option been removed?
Does it work if it is added? (you can change the smb.conf files and do a "systemcfg restart smb nmb" to force samba to restart with the updated config file.)
at least as client it still works.
in the /etc/samba/smb.conf of my notebook i have this NT1 setting enabled and i am able to browse/open the shares i need, which are still using SMB1 protocol.
at least, the last time i spoke with sysadmin about the shares, he told me, they are still using SMB1.