Unable to connect to share unless "Guest access" is checked

Bug #1556740 reported by Christopher M. Peñalver on 2016-03-14
This bug affects 1 person
Affects Status Importance Assigned to Milestone
samba (Ubuntu)

Bug Description

What is expected to happen:

On the Ubuntu 16.04 samba server with hostname HOSTNAME log in as first user created when installing USERNAME with password PASSWORD > create a new folder via nautilus (no gksudo) called test > secondary click test > Properties > tab Local Network Share > check "Share this folder" > Share name: test > other checkboxes unchecked > click button "Create Share"

On another Ubuntu 16.04 client click Places > Network > Windows Network > WORKGROUP > HOSTNAME > test > in the new connection window it notes at top:
Password required for share test on HOSTNAME

to the right of "Connect As" click radio button "Registered User" > put in Username field USERNAME > put in field Domain WORKGROUP > put in field Password PASSWORD > click radio button Forget password immediately > Connect

and it does so.

What happens instead is the connection window comes back up, but this time the "Connect As" radio button is now on Anonymous (Default) and everything else is grayed out. Hitting the X to close the window intermittently shows:

Unable to access location
Failed to mount Windows share: Invalid argument

The only way to allow the share to be connected is if one clicks on the server the checkbox "Guest access (for people without a user account)".

This prevents easily implementing secure and authenticated data transfers between server and client.

Attempting to connect via Windows 10 client notes Access Denied.

Attempting to smbclient via the Ubuntu 16.04 client notes:
lp_load_ex: refreshing parameters
Initialising global parameters
rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384)
Processing section "[global]"
doing parameter workgroup = WORKGROUP
doing parameter server string = %h server (Samba, Ubuntu)
doing parameter dns proxy = no
doing parameter log file = /var/log/samba/log.%m
doing parameter max log size = 1000
doing parameter syslog = 0
WARNING: The "syslog" option is deprecated
doing parameter panic action = /usr/share/samba/panic-action %d
doing parameter server role = standalone server
doing parameter passdb backend = tdbsam
doing parameter obey pam restrictions = yes
doing parameter unix password sync = yes
doing parameter passwd program = /usr/bin/passwd %u
doing parameter passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .
doing parameter pam password change = yes
doing parameter map to guest = bad user
doing parameter usershare allow guests = yes
pm_process() returned Yes
tdb(/var/lib/samba/private/secrets.tdb): tdb_open_ex: could not open file /var/lib/samba/private/secrets.tdb: Permission denied
Could not open tdb: Permission denied
Failed to open /var/lib/samba/private/secrets.tdb
ERROR: Unable to open secrets database

It is confirmed the file /var/lib/samba/private/secrets.tdb exists on both server and client, and the permissions for this file have not been adjusted in anyway. It's the default setup after installing the samba package.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: samba 2:4.3.6+dfsg-1ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4
Uname: Linux 4.4.0-12-generic x86_64
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
CurrentDesktop: GNOME-Flashback:Unity
Date: Sun Mar 13 23:03:51 2016
InstallationDate: Installed on 2015-12-18 (86 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
 nautilus 1:3.18.4.is.3.14.3-0ubuntu2
 gvfs 1.27.90-1ubuntu1
SambaClientRegression: Yes
SourcePackage: samba
UpgradeStatus: Upgraded to xenial on 2016-01-20 (53 days ago)

description: updated
summary: - Unable to connect to share unless "Guess access" is checked
+ Unable to connect to share unless "Guest access" is checked
Marc Deslauriers (mdeslaur) wrote :

Today's Samba update may contain the fix for this issue:


Could the original bug reporter please test the update and comment here? Thanks!

Same problem, same error message. I completely unshared the folder and reshared in the same way.

After mulling this over for a while, it appears too ambitious to expect for the original user to automatically have this access, despite this being what one would expect (especially those coming from the Windows world). Hence, I'm content with the help.ubuntu.com documentation discussing different use cases of Samba (ex. SOHO setups), where presently it's a bit limited.

Changed in samba (Ubuntu):
status: Triaged → Invalid
no longer affects: samba (Ubuntu Xenial)
no longer affects: samba (Ubuntu)
affects: samba → samba (Ubuntu)
Changed in samba (Ubuntu):
importance: Unknown → Undecided
status: Unknown → New
status: New → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.