Seems to be a problem with Samba

[shag00]

I have a small LAN of 4 PCs and have updated one of them to Kubuntu 20.04 but when I try to connect to any of the existing 19.10 samba servers I get this error: The file or folder smb://XXXXX.local/ does not exist. From the file manager on the 20.04, when I click on the Network button I can see the samba servers listed, including the server on the client machine which is the 20.04 machine. I get the error message even if I attempt to connect to the server on the 20.04 from the 20.04 machine. Changing max protocol from NT1 to off makes no difference. I am able to access Samba on the 20.04 PC from the 19.10 PCs. The 19.10 PCs can still connect to each other as normal.

Something has obviously changed in 20.04, does anybody know what it is.

####  /etc/samba/samba.conf   ####
[global]
  workgroup = WORKGROUP
  server string = Samba %h
  security = user
  encrypt passwords = yes
  obey pam restrictions = yes
  unix password sync = yes
  passdb backend = tdbsam:/var/lib/samba/private/passdb.tdb
  passwd program = /usr/bin/passwd %u
  passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword$
##    passwd chat debug = yes
##    log level = 100
  idmap config * :backend = tdb
  map to guest = bad user
  socket options = TCP NODELAY
  wins support = yes
  local master = yes
   os level = 99
  domain master = yes
  preferred master = yes
  client max protocol = NT1
  log level = 2
  max log size = 1000
  log file = /var/log/samba/log.%m
  debug timestamp = yes
  syslog = no
  panic action = /usr/share/samba/panic-action %d

[MoonRise]

It is the newer functions of SMABA to support MS Windows newer functions. It's slightly annoying but based on the above and what I had to do there is something you can do that works. Haven't found a way to prevent the addition that causes the problem, but with your smb://XXXXX.local/ you need to remove ".local". When I do that, all is fine, no issues.

The only other issue I'm still researching is having the Network section show Windows machines. I can see my Linux one but not the Windows although I can access it fine via other paths.

Let me know if at least removing .local helps.

EDIT: To note, I did still have to place "min protocol = NT1" under [global] to get everything on my home network passing credentials properly. Not sure why as that shouldn't be a factor with the Windows 10 machine I have but it did.

[shag00]

I tried removing ".local" from the address but no luck. Have you been able to get 2 20.04 machines to talk to each other?

[Augustus]

Hi shag00,
I have a kubuntu 19.10 smb server and can mount it without problem from a kubuntu 20.04 client from the command line as such:

mount -t cifs -o username=augustus,vers=1.0 //my1910.mydomain/mysmbshare /mnt/mysmbshare

I just tried it in dolphin on my kubu2004. Entered smb://my1910.mydomain/mysmbshare , gave my credentials (name, workgroup, passwd) and it connected fine.

good luck

Edit: just checked and noted we have different smb.conf on the server, probably the substatial differences are:

encrypt passwords = true
passdb backend = smbpasswd
obey pam restrictions = no

[hallergard]

I also had problems after upgrading from 19.10 to 20.04. I have a single user multi-boot system, and mainly use SMB shares to be able to read/write files and multi-media on the PC from my Android devices, which includes my Sony Android TV. On the PC I have Windows 10 and Windows 7 and various Linux partitions. My problems started when upgrading to Fedora 31 and then now to Kubuntu 20.04. Seems that Samba no longer supports SMB1, which I prefer as it is possible to use without passwords. So for Fedora (now 32) and Kubuntu 20.04 I have changed the smb.conf line "Client max protocol = NT1" to "Client min protocol = SMB2" - and have to use passwords on my Android devices. When booting my openSUSE partition I can still use SMB1 and no passwords.

[larbac]

I'm in the same situation...
My NAS needs SMB1... How can I enable this again??

[MoonRise]

@OP: Sorry, been busy and didn't see until now.

Do you know how the other SMB.CONF files are on the other machines that are Linux? To get all working I had to place "min protocol = NT1" under [global] to every Linux machine to work properly. Or properly in the sense I needed. Same for my NAS which @larbac might be your answer to. As noted though I still have not found a way to get the Windows machines to show up when browsing. Though I can get to them knowing the path directly, just won't show up in the network browser.

[shag00]

@Moonrise, all my PCs use the max protocol=NT1.

[shag00]

I tried client min & max = SMB2 with no luck.

[shag00]

Seems the problem was a bug, just installed the latest updates to 19.10 which were released today and my Samba works again.

[shag00]

Seems the fix caused another problem, although I can now access 20.04 > 19.10 I now cannot access 19.10 > 20.04.

[shag00]

A system restart cured the problem, ignore above post, everything working again.

[hallergard]

Thought the problem was with 20.04

[shag00]

So did I and there must have been something but a 19.10 samba patch was released that fixed the problem but there was no samba patch for 20.04.

[larbac]

This is my samba.conf
I can't find nothing about protocol to change...

#
# Sample configuration file for the Samba suite for Debian GNU/Linux.
#
#
# This is the main Samba configuration file. You should read the
# smb.conf(5) manual page in order to understand the options listed
# here. Samba has a huge number of configurable options most of which
# are not shown in this example
#
# Some options that are often worth tuning have been included as
# commented-out examples in this file.
# - When such options are commented with ";", the proposed setting
# differs from the default Samba behaviour
# - When commented with "#", the proposed setting is the default
# behaviour of Samba but the option is considered important
# enough to be mentioned here
#
# NOTE: Whenever you modify this file you should run the command
# "testparm" to check that you have not made any basic syntactic
# errors.

#======================= Global Settings =======================

[global]

## Browsing/Identification ###

# Change this to the workgroup/NT-domain name your Samba server will part of
workgroup = WORKGROUP

# server string is the equivalent of the NT Description field
server string = %h server (Samba, Ubuntu)

#### Networking ####

# The specific set of interfaces / networks to bind to
# This can be either the interface name or an IP address/netmask;
# interface names are normally preferred
; interfaces = 127.0.0.0/8 eth0

# Only bind to the named interfaces and/or networks; you must use the
# 'interfaces' option above to use this.
# It is recommended that you enable this feature if your Samba machine is
# not protected by a firewall or is a firewall itself. However, this
# option cannot handle dynamic or non-broadcast interfaces correctly.
; bind interfaces only = yes

#### Debugging/Accounting ####

# This tells Samba to use a separate log file for each machine
# that connects
log file = /var/log/samba/log.%m

# Cap the size of the individual log files (in KiB).
max log size = 1000

# We want Samba to only log to /var/log/samba/log.{smbd,nmbd}.
# Append syslog@1 if you want important messages to be sent to syslog too.
logging = file

# Do something sensible when Samba crashes: mail the admin a backtrace
panic action = /usr/share/samba/panic-action %d

####### Authentication #######

# Server role. Defines in which mode Samba will operate. Possible
# values are "standalone server", "member server", "classic primary
# domain controller", "classic backup domain controller", "active
# directory domain controller".
#
# Most people will want "standalone server" or "member server".
# Running as "active directory domain controller" will require first
# running "samba-tool domain provision" to wipe databases and create a
# new domain.
server role = standalone server

obey pam restrictions = yes

# This boolean parameter controls whether Samba attempts to sync the Unix
# password with the SMB password when the encrypted SMB password in the
# passdb is changed.
unix password sync = yes

# For Unix password sync to work on a Debian GNU/Linux system, the following
# parameters must be set (thanks to Ian Kahan <<kahan@informatik.tu-muenchen.de> for
# sending the correct chat script for the passwd program in Debian Sarge).
passwd program = /usr/bin/passwd %u
passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .

# This boolean controls whether PAM will be used for password changes
# when requested by an SMB client instead of the program listed in
# 'passwd program'. The default is 'no'.
pam password change = yes

# This option controls how unsuccessful authentication attempts are mapped
# to anonymous connections
map to guest = bad user

########## Domains ###########

#
# The following settings only takes effect if 'server role = primary
# classic domain controller', 'server role = backup domain controller'
# or 'domain logons' is set
#

# It specifies the location of the user's
# profile directory from the client point of view) The following
# required a [profiles] share to be setup on the samba server (see
# below)
; logon path = \\%N\profiles\%U
# Another common choice is storing the profile in the user's home directory
# (this is Samba's default)
# logon path = \\%N\%U\profile

# The following setting only takes effect if 'domain logons' is set
# It specifies the location of a user's home directory (from the client
# point of view)
; logon drive = H:
# logon home = \\%N\%U

# The following setting only takes effect if 'domain logons' is set
# It specifies the script to run during logon. The script must be stored
# in the [netlogon] share
# NOTE: Must be store in 'DOS' file format convention
; logon script = logon.cmd

# This allows Unix users to be created on the domain controller via the SAMR
# RPC pipe. The example command creates a user account with a disabled Unix
# password; please adapt to your needs
; add user script = /usr/sbin/adduser --quiet --disabled-password --gecos "" %u

# This allows machine accounts to be created on the domain controller via the
# SAMR RPC pipe.
# The following assumes a "machines" group exists on the system
; add machine script = /usr/sbin/useradd -g machines -c "%u machine account" -d /var/lib/samba -s /bin/false %u

# This allows Unix groups to be created on the domain controller via the SAMR
# RPC pipe.
; add group script = /usr/sbin/addgroup --force-badname %g

############ Misc ############

# Using the following line enables you to customise your configuration
# on a per machine basis. The %m gets replaced with the netbios name
# of the machine that is connecting
; include = /home/samba/etc/smb.conf.%m

# Some defaults for winbind (make sure you're not using the ranges
# for something else.)
; idmap config * : backend = tdb
; idmap config * : range = 3000-7999
; idmap config YOURDOMAINHERE : backend = tdb
; idmap config YOURDOMAINHERE : range = 100000-999999
; template shell = /bin/bash

# Setup usershare options to enable non-root users to share folders
# with the net usershare command.

# Maximum number of usershare. 0 means that usershare is disabled.
# usershare max shares = 100

# Allow users who've been granted usershare privileges to create
# public shares, not just authenticated ones
usershare allow guests = yes

#======================= Share Definitions =======================

# Un-comment the following (and tweak the other settings below to suit)
# to enable the default home directory shares. This will share each
# user's home directory as \\server\username
;[homes]
; comment = Home Directories
; browseable = no

# By default, the home directories are exported read-only. Change the
# next parameter to 'no' if you want to be able to write to them.
; read only = yes

# File creation mask is set to 0700 for security reasons. If you want to
# create files with group=rw permissions, set next parameter to 0775.
; create mask = 0700

# Directory creation mask is set to 0700 for security reasons. If you want to
# create dirs. with group=rw permissions, set next parameter to 0775.
; directory mask = 0700

# By default, \\server\username shares can be connected to by anyone
# with access to the samba server.
# Un-comment the following parameter to make sure that only "username"
# can connect to \\server\username
# This might need tweaking when using external authentication schemes
; valid users = %S

# Un-comment the following and create the netlogon directory for Domain Logons
# (you need to configure Samba to act as a domain controller too.)
;[netlogon]
; comment = Network Logon Service
; path = /home/samba/netlogon
; guest ok = yes
; read only = yes

# Un-comment the following and create the profiles directory to store
# users profiles (see the "logon path" option above)
# (you need to configure Samba to act as a domain controller too.)
# The path below should be writable by all users so that their
# profile directory may be created the first time they log on
;[profiles]
; comment = Users profiles
; path = /home/samba/profiles
; guest ok = no
; browseable = no
; create mask = 0600
; directory mask = 0700

[printers]
comment = All Printers
browseable = no
path = /var/spool/samba
printable = yes
guest ok = no
read only = yes
create mask = 0700

# Windows clients look for this share name as a source of downloadable
# printer drivers
[print$]
comment = Printer Drivers
path = /var/lib/samba/printers
browseable = yes
read only = yes
guest ok = no
# Uncomment to allow remote administration of Windows print drivers.
# You may need to replace 'lpadmin' with the name of the group your
# admin users are members of.
# Please note that you also need to set appropriate Unix permissions
# to the drivers directory for these users to have write rights in it
; write list = root, @lpadmin