[Bug 1703490] Re: Unable to mount network volume on 17.10 Samba server
Patrick Dunford
kahukowhai at gmail.com
Tue Jul 11 13:38:30 UTC 2017
patrick at MainPC:/etc/X11$ sudo smbstatus
[sudo] password for patrick:
Samba version 4.5.8-Ubuntu
PID Username Group Machine
Protocol Version Encryption Signing
----------------------------------------------------------------------------------------------------------------------------------------
9888 patrick patrick 192.168.1.173
(ipv4:192.168.1.173:39770) NT1 - -
18049 patrick patrick 192.168.1.192
(ipv4:192.168.1.192:49706) SMB3_11 - partial(AES-128-CMAC)
18046 patrick patrick 192.168.1.192
(ipv4:192.168.1.192:49700) SMB3_11 - partial(AES-128-CMAC)
Service pid Machine Connected at
Encryption Signing
---------------------------------------------------------------------------------------------
Media 18046 192.168.1.192 Tue Jul 11 23:25:00 2017 NZST
- -
Maps 18046 192.168.1.192 Tue Jul 11 23:25:00 2017 NZST
- -
Home 18046 192.168.1.192 Tue Jul 11 23:24:52 2017 NZST
- -
Maps 18049 192.168.1.192 Tue Jul 11 23:25:00 2017 NZST
- -
Maps 9888 192.168.1.173 Tue Jul 11 20:01:40 2017 NZST
- -
Locked files:
Pid Uid DenyMode Access R/W Oplock
SharePath Name Time
--------------------------------------------------------------------------------------------------
18046 1000 DENY_NONE 0x80 RDONLY NONE
/home/patrick/Maps . Tue Jul 11 23:25:09 2017
18049 1000 DENY_NONE 0x80 RDONLY NONE
/home/patrick/Maps . Tue Jul 11 23:25:09 2017
18046 1000 DENY_NONE 0x80 RDONLY NONE
/home/patrick/Media . Tue Jul 11 23:25:09 2017
18046 1000 DENY_NONE 0x80 RDONLY NONE
/home/patrick . Tue Jul 11 23:25:09 2017
192.168.1.192 is the Windows 10 client
192.168.1.173 is a Xubuntu 16.04 client.
However, smbstatus isn't showing anything about the clients that were
unable to mount a network resource (as to what version of CIFS they may
have attempted to use).
Computer 192.168.1.173 has been connected via /run/user/1000/gvfs which
on previous servers has been RW but with this 17.10 server is only RO
accessible.
patrick at MainPC:/etc/X11$ testparm
Load smb config files from /etc/samba/smb.conf
rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384)
WARNING: The "syslog" option is deprecated
Processing section "[printers]"
Processing section "[print$]"
Processing section "[Maps]"
Processing section "[Home]"
Processing section "[Media]"
Loaded services file OK.
Server role: ROLE_STANDALONE
Press enter to see a dump of your service definitions
# Global parameters
[global]
server string = %h server (Samba, Ubuntu)
log file = /var/log/samba/log.%m
max log size = 1000
syslog = 0
panic action = /usr/share/samba/panic-action %d
usershare allow guests = Yes
map to guest = Bad User
obey pam restrictions = Yes
pam password change = Yes
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
dns proxy = No
idmap config * : backend = tdb
[printers]
comment = All Printers
path = /var/spool/samba
browseable = No
printable = Yes
create mask = 0700
[print$]
comment = Printer Drivers
path = /var/lib/samba/printers
[Maps]
path = /home/patrick/Maps
read only = No
valid users = patrick
[Home]
path = /home/patrick
valid users = patrick
[Media]
path = /home/patrick/Media
read only = No
valid users = patrick
On 12/07/17 01:05, Andreas Hasenack wrote:
> Thanks for filing this bug in Ubuntu.
>
> Could you please share your /etc/samba/smb.conf on that 17.10 server?
> The output of "testparm -s" would be best.
>
> I tried the same here and could mount the share just fine from xenial.
> Maybe you restricted the smb protocol to higher versions? mount.cifs
> will use SMB1 by default, whereas windows 10 will use SMB2 or 3 (can't
> recall now).
>
> You can check with "smbstatus" on the server which protocol the connected client is using:
> root at 15-89:~# smbstatus
>
> Samba version 4.5.8-Ubuntu
> PID Username Group Machine Protocol Version Encryption Signing
> ----------------------------------------------------------------------------------------------------------------------------------------
> 14179 ubuntu ubuntu 10.0.5.1 (ipv4:10.0.5.1:57260) NT1 - -
>
> Service pid Machine Connected at Encryption Signing
> ---------------------------------------------------------------------------------------------
> data 14179 10.0.5.1 Tue Jul 11 12:59:32 PM 2017 UTC - -
> IPC$ 14179 10.0.5.1 Tue Jul 11 12:59:32 PM 2017 UTC - -
>
> No locked files
>
> To specify a different version, mount the cifs fileysystem like this:
> root at nsn7:~# mount //10.0.5.55/data /data -o user=ubuntu,vers=2.0
> Password for ubuntu@//10.0.5.55/data: ******
>
> root at nsn7:~# cd /data
>
> root at nsn7:/data# ls -l
> total 1024
> -rwxr-xr-x 1 root root 38 Jul 11 09:57 welcome.txt
>
> root at nsn7:/data# cat welcome.txt
> Welcome to the data share, developer.
>
> root at nsn7:/data# echo bye > bye.txt
> root at nsn7:/data# ls -la
> total 2052
> drwxr-xr-x 2 root root 0 Jul 11 10:02 .
> drwxr-xr-x 34 root root 4096 Jul 11 09:59 ..
> -rwxr-xr-x 1 root root 4 Jul 11 10:02 bye.txt
> -rwxr-xr-x 1 root root 38 Jul 11 09:57 welcome.txt
>
>
> And smbstatus on the server in this case (showing only the relevant line, for brevity):
> 14182 ubuntu ubuntu 10.0.5.1 (ipv4:10.0.5.1:57720) SMB2_02 - -
>
> In any case, I can read and write to the share. This is my smb.conf. All default except for the removal of printer shares, and the addition of the [data] share:
> [global]
> server string = %h server (Samba, Ubuntu)
> log file = /var/log/samba/log.%m
> max log size = 1000
> syslog = 0
> panic action = /usr/share/samba/panic-action %d
> usershare allow guests = Yes
> map to guest = Bad User
> obey pam restrictions = Yes
> pam password change = Yes
> 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
> dns proxy = No
> idmap config * : backend = tdb
>
> [data]
> comment = Data share
> path = /data
> read only = no
> browseable = true
> guest ok = no
>
>
> ** Changed in: samba (Ubuntu)
> Status: New => Incomplete
>
--
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 16.04 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