[Bug 1703490] Re: Unable to mount network volume on 17.10 Samba server

Patrick Dunford kahukowhai at gmail.com
Thu Jul 13 02:40:39 UTC 2017 

OK here is a fstab from one of my PCs running 17.10 and it tries to 
mount shares from two different computers:

# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type> <options>       <dump>  <pass>
# / was on /dev/sdb1 during installation
UUID=0887068e-fc83-4a98-a90f-ccbfdecd8728 /               ext4 
errors=remount-ro 0       1
# /home was on /dev/sdc1 during installation
UUID=b6c98b89-941b-4e36-b91b-f011633ae70d /home           ext4 
defaults        0       2
/swapfile                                 none            swap 
sw              0       0
//192.168.1.173/media /mnt/share/mediapc/media cifs 
credentials=/home/patrick/.smbcredentials,iocharset=utf8,sec=ntlm 0   0
//192.168.1.116/maps /mnt/share/mainpc/maps cifs 
credentials=/home/patrick/.smbcredentials,iocharset=utf8,sec=ntlm 0   0

so mediapc is acting as a Samba server running 16.04 and this one mounts 
just fine, mainpc is acting as a Samba server running 17.10 and it 
always fails with error 13 permission denied.

Both servers have exactly the same credentials needed so they use the 
same credentials file to provide those credentials to mount.cifs through 
the mount command. So it fails regardless of whether I let it do it at 
startup or if I type sudo mount -a to mount at any time of my choosing.

I have yet to try out any of the other things we have tried with this 
computer so that will be my next step and based on so far it will 
probably succeed.

On 13/07/17 04:53, Andreas Hasenack wrote:
> It could be that, in the case where /etc/fstab is used, there are extra
> options being passed to mount.cifs and that is what is causing the
> difference in behaviour.
>


** Description changed:

  I have a computer with a new 17.10 installation, and I have network
  resources on it that I want to share to other computers on my network,
  using Samba. I set it up the same way with Samba as I did with the old
  16.04 installation, but all the other computers on the network that are
  running Xubuntu can't connect to it like they did before.
  
  The following are the user experiences of different computers in my
  network connecting to shared SMB resources on other computers:
  
  16.04 client mount.cifs to 16.04 server: full access
  16.04 client path run/user/1000/gvfs to 16.04 server: full access
  17.10 client mount.cifs to 16.04 server: full access
  
  16.04 client mount.cifs to 17.10 server: access denied error
- 17.10 client mount.cifs to 16.04 server: access denied error
+ 17.10 client mount.cifs to 17.10 server: access denied error
  16.04 client path run/user/1000/gvfs to 17.10 server: read only access
  Windows 10 client explorer map drive to 17.10 server: full access
  
  the server used to run 16.04 and is now running 17.10. It is the same
  computer and has the same network resources shared on it that it had
  when it was running 16.04.
  
  The server installation of 17.10 was a clean install but the home folder
  was existing on a different volume and was remounted after the install.
  
  As you can see a Windows 10 computer is the only computer in the network
  that can connect to the Samba share with full access and no apparent
  difference in the user experience.
  
  Ubuntu Artful Aardvark (development branch) 17.10
  apt-cache policy samba
  samba:
-   Installed: 2:4.5.8+dfsg-2ubuntu3
-   Candidate: 2:4.5.8+dfsg-2ubuntu3
-   Version table:
-  *** 2:4.5.8+dfsg-2ubuntu3 500
-         500 http://nz.archive.ubuntu.com/ubuntu artful/main amd64 Packages
-         100 /var/lib/dpkg/status
+   Installed: 2:4.5.8+dfsg-2ubuntu3
+   Candidate: 2:4.5.8+dfsg-2ubuntu3
+   Version table:
+  *** 2:4.5.8+dfsg-2ubuntu3 500
+         500 http://nz.archive.ubuntu.com/ubuntu artful/main amd64 Packages
+         100 /var/lib/dpkg/status
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: samba 2:4.5.8+dfsg-2ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17
  Uname: Linux 4.10.0-26-generic x86_64
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Jul 11 13:25:40 2017
  SambaClientRegression: Yes
  SourcePackage: samba
  UpgradeStatus: No upgrade log present (probably fresh install)

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/1703490

Title:
  Unable to mount network volume on 17.10 Samba server

Status in samba package in Ubuntu:
  Incomplete

Bug description:
  I have a computer with a new 17.10 installation, and I have network
  resources on it that I want to share to other computers on my network,
  using Samba. I set it up the same way with Samba as I did with the old
  16.04 installation, but all the other computers on the network that
  are running Xubuntu can't connect to it like they did before.

  The following are the user experiences of different computers in my
  network connecting to shared SMB resources on other computers:

  16.04 client mount.cifs to 16.04 server: full access
  16.04 client path run/user/1000/gvfs to 16.04 server: full access
  17.10 client mount.cifs to 16.04 server: full access

  16.04 client mount.cifs to 17.10 server: access denied error
  17.10 client mount.cifs to 17.10 server: access denied error
  16.04 client path run/user/1000/gvfs to 17.10 server: read only access
  Windows 10 client explorer map drive to 17.10 server: full access

  the server used to run 16.04 and is now running 17.10. It is the same
  computer and has the same network resources shared on it that it had
  when it was running 16.04.

  The server installation of 17.10 was a clean install but the home
  folder was existing on a different volume and was remounted after the
  install.

  As you can see a Windows 10 computer is the only computer in the
  network that can connect to the Samba share with full access and no
  apparent difference in the user experience.

  Ubuntu Artful Aardvark (development branch) 17.10
  apt-cache policy samba
  samba:
    Installed: 2:4.5.8+dfsg-2ubuntu3
    Candidate: 2:4.5.8+dfsg-2ubuntu3
    Version table:
   *** 2:4.5.8+dfsg-2ubuntu3 500
          500 http://nz.archive.ubuntu.com/ubuntu artful/main amd64 Packages
          100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: samba 2:4.5.8+dfsg-2ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17
  Uname: Linux 4.10.0-26-generic x86_64
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Jul 11 13:25:40 2017
  SambaClientRegression: Yes
  SourcePackage: samba
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1703490/+subscriptions

More information about the foundations-bugs mailing list