Tony Pursell, your workaround works for me..
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1880305
Title:
Failed to mount Windows share: Software caused connection abort
To manage notifications abo
I should clarify that it works when I put it in the [global] section in
/usr/share/samba/smb.conf
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1880305
Title:
Failed to mount Windows share: Software
I tried to apply the work-around given here (min client protocol), but
am having trouble. It works if I put it into ~/.smb/smb.conf or
/etc/samba/smb.conf. However, for various reasons neither file is really
appropriate in my case. Instead, I would like to add it to a file that
is included from /et
I have done that but I shouldn't have had to. There must have been some
change to Samba on the upgrade to 20.04 that caused it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1880305
Title:
Failed t
fyi, this was an intentional upstream change, thanks @vtapia for
pointing me to the upstream wiki:
https://wiki.samba.org/index.php/Samba_4.11_Features_added/changed#SMB1_is_disabled_by_default
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I have done that but I shouldn't have had to. There must have been some
change to Samba on the upgrade to 20.04 that caused it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1880305
Title:
Failed t
Then you need to downgrade the client side of the connection to SMB1,
via 'client min protocol = NT1' in smb.conf on the client.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1880305
Title:
Failed t
Thanks for your comment Jim. My NAS is a ZyXEL NSA325 v2 and doesn't
have any access to SMB settings.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1880305
Title:
Failed to mount Windows share: Sof
Another workaround (if you're having this problem on a Synology
DiskStation, like me) is to pick a higher maximum protocol under the
file services advanced settings for SMB on your NAS.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
h
Hi Robie
I think you've missed the point. There is a bug that was introduced by
the upgrade from 19.10 to 20.04. I assume it is somewhere in Samba.
My use of NT1 is not meant to be a fix for the reason you have given.
It is just a workaround.
Please change it back from Won't Fix to something s
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
I believe that there are no plans to allow NT1 by default for security
reasons, so I'm marking this as Won't Fix. The workaround is to manually
allow it as you found.
** Changed in: samba (Ubuntu)
Status: N
** No longer affects: nautilus (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1880305
Title:
Failed to mount Windows share: Software caused connection abort
To manage notifications about th
Have created a workaround which works:
1. created directory ~/.smb
2. copied /etc/samba/smb.conf to it
3. added 'client min protocol = NT1' to [global] section.
as suggested in bug #1879776
** Also affects: samba (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug not
13 matches
Mail list logo
