Hi Celina,
thanks for the info but that isn't the same issue that was discussed in this
bug.
Furthermore while enabling SMBv1 is a workaround to the problem you had it is
considered a huge security risk and therefore should be a last resort and only
for e.g. isolated environments.
I tried to
File sharing stopped working after upgrading to Ubuntu 20.04. Turns out
there was a change in behavior in Sambva v4.11 that disabled SMB1
protocol by default.
Here’s the fix, from Reddit
https://www.reddit.com/r/linuxquestions/comments/djvpdn/smb_connection_nautilus_error_debian_bullseye/
You
Mustapa, about files being shown as directories, you are probably being
affected by bug
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1872476 which is an
in-progress SRU and has a fix uploaded to focal-proposed already.
--
You received this bug notification because you are a member of
Mustapa, about files being shown as directories, you are probably being
affected by bug
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1872476 which is an
in-progress SRU and has a fix uploaded to focal-proposed already.
--
You received this bug notification because you are a member of
I just found how to solve it but not the same as ubuntu 19 which has no
issue at all.
I have to rename my file from e.g
from for e.g master.event.200420.hdf.tvs-sv
to for e.g master.event.200420
Then only it works. but it did ask whether you want to merge the files (
even though it is a fresh
Hello, I can transfer files to my NAS. Always error why copying. before
this I cant even access the smb server until i follow your
recommendation, edit smb.conf and add NT1. Even after the changes I can
transfer any files. I am using ubuntu 20.04 which i just upgraded it
from 19 which was working
Thanks for getting back to us.
I'm going to close this bug as invalid, since the software is working as
expected.
** Changed in: samba (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to samba in Ubuntu.
Thanks for getting back to us.
I'm going to close this bug as invalid, since the software is working as
expected.
** Changed in: samba (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
smbclient //192.168.1.1/USB1 --option='client min protocol=NT1'
Enter WORKGROUP\laurent's password:
Try "help" to get a list of possible commands.
smb: \>
I just added "client min protocol=NT1" to my /etc/samba/smb.conf and it works
again. Thanks to all of you for your help and sorry, as
Have you tried smbclient with -m NT1?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1875354
Title:
No more smb access after migration to UBUNTU 20.04 from UBUNTU 19.10
To manage notifications
Have you tried smbclient with -m NT1?
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/1875354
Title:
No more smb access after migration to UBUNTU 20.04 from UBUNTU 19.10
To manage
indeed I have just checked and my router however relatively recent still
uses smb1.
"Morbius1 (morbius1) ", According to what you say, I could not access my
NAS or my router any more than a CIFS mount? it's a pity, even under
windows one can force, even if it is not recommendable from a security
Thank you for your help but I only indicated some tests I had done after
internet research before posting here.
Anyway, despite the changes in the smb.conf that I mentioned at the beginning
of my post, especially concerning the smb1 protocol, smbclient doesn't work. As
I said before posting
You need "client min protocol = NT1" (min not max!),
see https://www.samba.org/samba/history/samba-4.12.0.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1875354
Title:
No more smb access after
"laurent@laurent-iMac:~$ smbclient //192.168.1.1/USB1
...
...
protocol negotiation failed: NT_STATUS_CONNECTION_DISCONNECTED"
You are getting a "protocol negotiation failed" error because the server
can only be accessed with SMB1 ( NT1 ) and there is no SMB1 ( NT1 ) in
the version of samba that
Thanks, since smbclient has the same issue it's probably an issue with
the libsmbclient library, reassigning
** Package changed: gvfs (Ubuntu) => samba (Ubuntu)
** Changed in: samba (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of
In response to the error "Unknown parameter encountered: ", bind interfaces
only"...
Ignoring unknown parameter ", bind interfaces only", I corrected the typo and
I'll send you my smb.conf just in case.
** Attachment added: "smb.conf"
I confirm that it still works with ubuntu 19.10 up to date.
However, I can't navigate in the windows network. The folder remains empty.
The access by smb://IP/folder works, as well as smbclient //IP/folder but
smbtree tells me "Unable to initialise messaging context" but this seems to be
normal
Sorry, I got confused with smb://.
...I've been doing a lot of tests because I'm not getting the same feedback:
laurent@laurent-iMac:~$ smbclient //192.168.1.1/USB1
Unknown parameter encountered: ", bind interfaces only"
Ignoring unknown parameter ", bind interfaces only"
protocol negotiation
Thank you for the details, could you also try with smbclient as
requested at the bottom on my comment?
Does connecting to that share using
$ smbclient //192.168.1.1/USB1
works?
(or similar on other shares)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
IP of my pc : 192.168.1.10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1875354
Title:
No more smb access after migration to UBUNTU 20.04 from UBUNTU 19.10
To manage notifications about this bug
Thank you for coming back.
So I'm going to start from a good base and delete what I did.
laurent@laurent-iMac:~$ pkill gvfs; pkill nautilus
pkill: le pid 1184 n'a pu être tué: Opération non permise
pkill: le pid 1199 n'a pu être tué: Opération non permise
pkill: le pid 1204 n'a pu être tué:
Thank you for your bug report, gnome-vfs hasn't been used by nautilus
for over 10 years so your added files should make a difference.
Could you get a debug log as explained on
https://wiki.gnome.org/Projects/gvfs/debugging ? Using the
GVFS_SMB_DEBUG=10 argument (review the log to filter private
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gvfs (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1875354
Title:
No
modified the source package attributed to this bug
** Package changed: ubuntu => gvfs (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1875354
Title:
No more smb access after migration to
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It seems that your bug report is not filed about a
specific source package though, rather it is just filed against Ubuntu
in general. It is important that bug reports be filed about source
packages so that people
26 matches
Mail list logo
