DebianThis forum is for the discussion of Debian Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I'm having trouble with my current Debian Sid machine, and I'm pretty sure the problem comes from my installation, and it's not a bug or something.
Basically, there are some shared folders in my laptop, via SAMBA. I have no problems accessing this shares from another Debian installation (stable, in this case), but Android has issues accessing the folders. Now, bare with my, because you're going to point out that that's on Android, but wait.
I use two Android apps that let me browse my shares: VLC and Amaze File Explorer.
Amaze fails to connect to my computer every time. Actually, it does nothing. It's not even logged in SAMBA's log.
VLC is able to access the shares, but mostly the ones where guests are allowed. Those are accessible pretty easily. The ones that need authentication usually fail. But if you struggle long enough, you may get through and authenticate successfully. The log gets some input when VLC tries to authenticate (see below)
As I mentioned, I also have another Debian stable installation. I set up SAMBA in that installation, and the app that is never able to connect to my PC (Amaze), does it without any hesitation to this PC. You may think that there's a bug in Unstable's SAMBA, but I don't think that's what going on. I've been having this problem for years.
I suspect that there are some files or packages that are bothering a proper connection to the server. I've purged SAMBA and all related files, but that hasn't made any difference.
I should also mention that smbtree command shows nothing on my computer. And I can't help to think that those problems are related.
Here there are some config files and logs:
/etc/samba/smb.conf
Code:
#
# 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
#### 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 =======================
#[homes]
# comment = Home Directories
# browseable = yes
# 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 = 0755
# 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 = 0755
# By default, \\server\username shares can be connected to by anyone
# with access to the samba server.
# The following parameter makes 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
[The98]
comment = Home
browseable = yes
path = /home/the98
guest ok = no
read only = yes
create mask = 0755
directory mask = 0755
[Musica]
comment = Musica del Home
browseable = yes
path = /home/the98/Musica
guest ok = yes
read only = yes
create mask = 0700
[Descargas]
comment = Descargas del Home
browseable = yes
path = /home/the98/Descargas
guest ok = yes
read only = yes
create mask = 0700
[TMP]
comment = TMP
browseable = yes
path = /tmp
guest ok = no
read only = no
create mask = 0755
directory mask = 0755
$ smbtree -d3
Code:
lp_load_ex: refreshing parameters
Initialising global parameters
rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384)
Processing section "[global]"
added interface wlan0 ip=2800:810:54a:8681:ae81:12ff:fe28:5672 bcast= netmask=ffff:ffff:ffff:ffff::
added interface wlan0 ip=192.168.0.10 bcast=192.168.0.255 netmask=255.255.255.0
tdb(/run/samba/gencache.tdb): tdb_open_ex: could not open file /run/samba/gencache.tdb: Permiso denegado
resolve_lmhosts: Attempting lmhosts lookup for name WORKGROUP<0x1d>
name_resolve_bcast: Attempting broadcast lookup for name WORKGROUP<0x1d>
Got a positive name query response from 192.168.0.2 ( 192.168.0.2 )
tdb(/run/samba/gencache.tdb): tdb_open_ex: could not open file /run/samba/gencache.tdb: Permiso denegado
Enter WORKGROUP\the98's password:
Connecting to 192.168.0.2 at port 445
Connecting to 192.168.0.2 at port 139
tdb(/run/samba/gencache.tdb): tdb_open_ex: could not open file /run/samba/gencache.tdb: Permiso denegado
tdb(/run/samba/gencache.tdb): tdb_open_ex: could not open file /run/samba/gencache.tdb: Permiso denegado
Connecting to 192.168.0.2 at port 445
Connecting to 192.168.0.2 at port 139
When VLC tries to authenticate, I get this on:
/var/log/samba/log.
Code:
[2020/04/28 12:13:51.107893, 0] ../../source3/smbd/smb2_server.c:735(smb2_validate_message_id)
smb2_validate_message_id: smb2_validate_message_id: client used more credits than granted, mid 5, charge 1, credits_granted 0, seqnum low/range: 5/0
# testparm -s
Code:
Load smb config files from /etc/samba/smb.conf
Loaded services file OK.
Server role: ROLE_STANDALONE
# Global parameters
[global]
log file = /var/log/samba/log.%m
logging = file
map to guest = Bad User
max log size = 1000
obey pam restrictions = Yes
panic action = /usr/share/samba/panic-action %d
passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .
passwd program = /usr/bin/passwd %u
server role = standalone server
unix password sync = Yes
usershare allow guests = Yes
idmap config * : backend = tdb
[The98]
comment = Home
create mask = 0755
path = /home/the98
[Musica]
comment = Musica del Home
create mask = 0700
guest ok = Yes
path = /home/the98/Musica
[Descargas]
comment = Descargas del Home
create mask = 0700
guest ok = Yes
path = /home/the98/Descargas
[TMP]
comment = TMP
create mask = 0755
path = /tmp
read only = No
Let me know if there's something else I can post to get to a solution.
Ferrari, thanks for your response. I haven't tried an alternative. However, is Debian stable using some other protocol other than SMBvs2/SMBv3?
Remember that VLC on Android has no problem accessing as guest, but it has some authentication issues with no guest allowed shares. And Amaze File Maganager is able to authenticate without any problems to a SAMBA server under Debian Stable.
The problem is my computer, which it's been years behaving this way through different versions of SAMBA. I been having Debian Sid installed on this PC for years now. I think it never worked properly. There might be some legacy files or packages that are "making noise". That's what I suspect, at least.
The problem is my computer, which it's been years behaving this way through different versions of SAMBA. I been having Debian Sid installed on this PC for years now. I think it never worked properly. There might be some legacy files or packages that are "making noise". That's what I suspect, at least.
Consider upgrading any legacy samba hosts perhaps.
What do you mean by stable. The current stable version is 10.3 i.e. Buster.
Since sid is not an official release your system could be in any configuration so really no way for anyone to know what is really broken. On the other hand with stable all the bugs have been worked out so I would expect samba to work.
What do you mean by stable. The current stable version is 10.3 i.e. Buster.
Since sid is not an official release your system could be in any configuration so really no way for anyone to know what is really broken. On the other hand with stable all the bugs have been worked out so I would expect samba to work.
I mean I have two laptops. One of them is running Debian Unstable. That's my main computer, and I've running the same installation for years. Upgrading constantly, using aptitude safe-upgrade feature, mostly. I've almost never had a problem with the system or the applications.
I also have another laptop that runs Debian Stable (Buster). The Android Apps connect without any hesitation to that stable installation. But I don't think it's a bug on Debian Unstable.
I recently remembered my parent's computer, which also runs Debian Unstable. If I connect to that computer using the same phone and apps, I have no problems. The trouble one has always been my main laptop. But this is not something recent, it was always this way. But since I've purged all SAMBA packages and reinstall them, I think that there is something that's messing up the communication between server and Android clients. And I think the main problem is authentication.
What about smbtree not showing anything? Why can that be? I think that's related to the problem the apps have.
Amaze still does not create any entry on that log file.
I should mention that VLC fails to connect to a protected share when you input the right user and password. What I do to log in is; first input a wrong password, VLC fails to connect. Then input the right password, and VLC connects Ok.
This is what is logged when that happens:
When accessing via VLC to the server's shared folders:
Code:
2020/04/29 11:21:10.175316, 5] ../../source3/auth/auth.c:547(make_auth3_context_for_ntlm)
Making default auth method list for server role = 'standalone server', encrypt passwords = yes
[2020/04/29 11:21:10.175386, 5] ../../source3/auth/auth.c:422(load_auth_module)
load_auth_module: Attempting to find an auth method to match anonymous
[2020/04/29 11:21:10.175415, 5] ../../source3/auth/auth.c:447(load_auth_module)
load_auth_module: auth method anonymous has a valid init
[2020/04/29 11:21:10.175438, 5] ../../source3/auth/auth.c:422(load_auth_module)
load_auth_module: Attempting to find an auth method to match sam_ignoredomain
[2020/04/29 11:21:10.175462, 5] ../../source3/auth/auth.c:447(load_auth_module)
load_auth_module: auth method sam_ignoredomain has a valid init
[2020/04/29 11:21:10.228418, 4] ../../source3/auth/pampass.c:483(smb_pam_start)
smb_pam_start: PAM: Init user: nobody
[2020/04/29 11:21:10.234462, 4] ../../source3/auth/pampass.c:492(smb_pam_start)
smb_pam_start: PAM: setting rhost to: 192.168.0.5
[2020/04/29 11:21:10.234522, 4] ../../source3/auth/pampass.c:501(smb_pam_start)
smb_pam_start: PAM: setting tty
[2020/04/29 11:21:10.234553, 4] ../../source3/auth/pampass.c:509(smb_pam_start)
smb_pam_start: PAM: Init passed for user: nobody
[2020/04/29 11:21:10.234582, 4] ../../source3/auth/pampass.c:646(smb_internal_pam_session)
smb_internal_pam_session: PAM: tty set to: smb/2141682504
[2020/04/29 11:21:10.235921, 4] ../../source3/auth/pampass.c:465(smb_pam_end)
smb_pam_end: PAM: PAM_END OK.
[2020/04/29 11:21:10.407070, 4] ../../source3/auth/pampass.c:483(smb_pam_start)
smb_pam_start: PAM: Init user: nobody
[2020/04/29 11:21:10.412495, 4] ../../source3/auth/pampass.c:492(smb_pam_start)
smb_pam_start: PAM: setting rhost to: 192.168.0.5
[2020/04/29 11:21:10.412572, 4] ../../source3/auth/pampass.c:501(smb_pam_start)
smb_pam_start: PAM: setting tty
[2020/04/29 11:21:10.412600, 4] ../../source3/auth/pampass.c:509(smb_pam_start)
smb_pam_start: PAM: Init passed for user: nobody
[2020/04/29 11:21:10.412624, 4] ../../source3/auth/pampass.c:646(smb_internal_pam_session)
smb_internal_pam_session: PAM: tty set to: smb/2258749750
[2020/04/29 11:21:10.413764, 4] ../../source3/auth/pampass.c:465(smb_pam_end)
smb_pam_end: PAM: PAM_END OK.
[2020/04/29 11:21:10.710082, 4] ../../source3/auth/pampass.c:483(smb_pam_start)
smb_pam_start: PAM: Init user: nobody
[2020/04/29 11:21:10.716136, 4] ../../source3/auth/pampass.c:492(smb_pam_start)
smb_pam_start: PAM: setting rhost to: 192.168.0.5
[2020/04/29 11:21:10.716191, 4] ../../source3/auth/pampass.c:501(smb_pam_start)
smb_pam_start: PAM: setting tty
[2020/04/29 11:21:10.716221, 4] ../../source3/auth/pampass.c:509(smb_pam_start)
smb_pam_start: PAM: Init passed for user: nobody
[2020/04/29 11:21:10.716248, 4] ../../source3/auth/pampass.c:646(smb_internal_pam_session)
smb_internal_pam_session: PAM: tty set to: smb/550611482
[2020/04/29 11:21:10.717553, 4] ../../source3/auth/pampass.c:465(smb_pam_end)
smb_pam_end: PAM: PAM_END OK.
[2020/04/29 11:21:10.862800, 1] ../../source3/smbd/service.c:346(create_connection_session_info)
create_connection_session_info: guest user (from session setup) not permitted to access this share (The98)
[2020/04/29 11:21:10.862842, 1] ../../source3/smbd/service.c:530(make_connection_snum)
create_connection_session_info failed: NT_STATUS_ACCESS_DENIED
[2020/04/29 11:21:10.882099, 4] ../../source3/auth/pampass.c:483(smb_pam_start)
smb_pam_start: PAM: Init user: nobody
[2020/04/29 11:21:10.887531, 4] ../../source3/auth/pampass.c:492(smb_pam_start)
smb_pam_start: PAM: setting rhost to: 192.168.0.5
[2020/04/29 11:21:10.887578, 4] ../../source3/auth/pampass.c:501(smb_pam_start)
smb_pam_start: PAM: setting tty
[2020/04/29 11:21:10.887604, 4] ../../source3/auth/pampass.c:509(smb_pam_start)
smb_pam_start: PAM: Init passed for user: nobody
[2020/04/29 11:21:10.887628, 4] ../../source3/auth/pampass.c:646(smb_internal_pam_session)
smb_internal_pam_session: PAM: tty set to: smb/1452360668
[2020/04/29 11:21:10.888816, 4] ../../source3/auth/pampass.c:465(smb_pam_end)
smb_pam_end: PAM: PAM_END OK.
When selecting my Home folder, but not logging in, just selecting the folder:
Code:
[2020/04/29 11:22:05.210335, 1] ../../source3/smbd/service.c:346(create_connection_session_info)
create_connection_session_info: guest user (from session setup) not permitted to access this share (The98)
[2020/04/29 11:22:05.210386, 1] ../../source3/smbd/service.c:530(make_connection_snum)
create_connection_session_info failed: NT_STATUS_ACCESS_DENIED
[2020/04/29 11:22:05.212933, 4] ../../source3/auth/pampass.c:483(smb_pam_start)
smb_pam_start: PAM: Init user: nobody
[2020/04/29 11:22:05.217679, 4] ../../source3/auth/pampass.c:492(smb_pam_start)
smb_pam_start: PAM: setting rhost to: 192.168.0.5
[2020/04/29 11:22:05.217727, 4] ../../source3/auth/pampass.c:501(smb_pam_start)
smb_pam_start: PAM: setting tty
[2020/04/29 11:22:05.217751, 4] ../../source3/auth/pampass.c:509(smb_pam_start)
smb_pam_start: PAM: Init passed for user: nobody
[2020/04/29 11:22:05.217774, 4] ../../source3/auth/pampass.c:646(smb_internal_pam_session)
smb_internal_pam_session: PAM: tty set to: smb/901647929
[2020/04/29 11:22:05.218817, 4] ../../source3/auth/pampass.c:465(smb_pam_end)
When logging in with the wrong password: No entries in the samba log.
So I grabbed another HDD and made a fresh installation of Debian Sid there. I get the same issue. I also had another old installation of Debian Stretch on that HDD. Installed SAMBA on Stretch and everything works.
The problem narrows down to a bug in Sid, or a new version of Samba that is not compatible with those Android apps. I was refusing to believe it was a bug, because I remembered I always had problems, but maybe it's some kind of "Mandela effect". I don't know.
SMB1 is disabled by default
---------------------------
The defaults of 'client min protocol' and 'server min protocol'
have been changed to SMB2_02.
This means clients without support for SMB2 or SMB3 are no longer
able to connect to smbd (by default).
It also means client tools like smbclient and other,
as well as applications making use of libsmbclient are no longer
able to connect to servers without SMB2 or SMB3 support (by default).
It's still possible to allow SMB1 dialects, e.g. NT1, LANMAN2
and LANMAN1 for client and server, as well as CORE and COREPLUS on
the client.
Note that most commandline tools e.g. smbclient, smbcacls and others
also support the '--option' argument to overwrite smb.conf options,
e.g. --option='client min protocol=NT1' might be useful.
As Microsoft no longer installs SMB1 support in recent releases
or uninstalls it after 30 days without usage, the Samba Team
tries to get remove the SMB1 usage as much as possible.
SMB1 is officially deprecated and might be removed step by step
in the following years. If you have a strong requirement for SMB1
(except for supporting old Linux Kernels), please file a bug
at https://bugzilla.samba.org and let us know about the details.
LanMan and plaintext authentication deprecated
----------------------------------------------
The "lanman auth" and "encrypt passwords" parameters are deprecated
with this release as both are only applicable to SMB1 and are quite
insecure. NTLM, NTLMv2 and Kerberos authentication are unaffected, as
"encrypt passwords = yes" has been the default since Samba 3.0.0.
If you have a strong requirement for these authentication protocols,
please file a bug at https://bugzilla.samba.org and let us know about
the details.
I'm not sure if setting 'server min protocol = NT1' is still possible or not, along with the 'ntlm auth = ntlmv1-permitted'. As you're aware SMBv1 is deprecated and samba is moving to get rid of any residual support for this protocol suite.
Well… i HAVE A WORKAROUND.
It seems that when gvfs mounts my samba drive, the max allow length of the path its larger than when i access form the network samba folder itself.
After testing with short names, it seems that even in KDE i can drag the entire EXTERNO folder to vlc and it works great without doing anything (at least in the vm, with bridge network, allow all in promiscous mode and without update anything.)
PS:
I've left SAMBA for many years, using Webdav as share, needs authentication
This works I found quickly, as I never tested VLC on my Webdav shares my self. https://github.com/danfr/webdav-player
For me Webdav via htttps port 443, is safer to share outside my home and when a VPN-connection does give some problems, do not want to be dependent on VPN.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
