sec= in mount.cifs is a client setting, I was quoting the mount.cifs
manpage where it says when that changed defaults in the (client
machine's) kernel.
Either way, I believe the solution to what you reported is in the first
paragraph of comment #21.
--
You received this bug notification because
Ok, so you either change your clients to use "sec=ntlmssp", or change
"ntlm auth" on the server to "yes" as explained by @metze in comment
#17.
This sec= setting in mount.cifs also changed defaults. From its manpage:
"The default in mainline kernel versions prior to v3.8 was sec=ntlm. In v3.8,
Can you try Stefan's suggestion from comment #17 please?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/1703490
Title:
Unable to mount network volume on 17.10 Samba server
To manage
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.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
IP addresses work fine too.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/1703490
Title:
Unable to mount network volume on 17.10 Samba server
To manage notifications about this bug
Here is what I got with xfce on 16.04 using thunar. Just the home share
is read-only, as expected.
** Attachment added: "thunar-xfce.png"
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1703490/+attachment/4913443/+files/thunar-xfce.png
--
You received this bug notification because you
Sorry about your frustration, we are just trying to narrow it down. It
could be that something in artful's samba changed and that thunar needs
to adapt, for example.
We need to determine why this test case that you mentioned when opening
the bug doesn't work:
"""
16.04 client mount.cifs to 17.10
Let's try to narrow it down to a simple test case involving smbclient
and/or mount.cifs.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/1703490
Title:
Unable to mount network volume
I tried your shares, and they seem to work as expected. Note that
[Homes] is read only (default for "read only" is "yes"), so you won't be
able to write to Homes or even Maps under it while connected to Homes,
but if you connect to Maps, then you can:
oot@nsn7:~# for d in Home Maps Media; do
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
10 matches
Mail list logo
