Arch Linux

nuts

Member

Registered: 2010-01-13

Posts: 15

[solved] smb-Accessing to a samba server does not work anymore.

Hi!
Before 2020/03/29, I used to use Thunar and gvfs-smb to access to a NAS of my provider (freebox), and it worked well. I know the samba protocole is NT1
Then smbclient and libwbclient moved from version 4.10.10-1 to 4.11.3-3 and now I can't mount smb shares.
I use thunar 1.8.14-1 and gvfs-smb 1.44.1-1. If I try to go on the server's directory, I have

Software caused connection abort

https://image.noelshack.com/fichiers/20 … bissue.png
I can see folders but I can't go in.
I'm searching on web, but I have no solution yet.

I have the same issue both on my desktop and laptop. No problem with same machines with windows 10.

edit: it works with

mount -t cifs -o vers=1.0 //192.168.0.254/Goinfre /mnt

But I like using gvfs instead

PS: sorry for my english

Mod Edit - Replaced oversized image with link.
CoC - Pasting pictures and code

Last edited by nuts (2020-04-08 16:30:14)

WFV

Member

From: ☭USSA⛧⭒⭒⭒⭒

Registered: 2013-04-23

Posts: 288

Re: [solved] smb-Accessing to a samba server does not work anymore.

maybe look at this thread https://bbs.archlinux.org/viewtopic.php?id=254083 ?

---

∞ hard times make the strong, the strong make good times, good times make the weak, the weak make hard times ∞

nuts

Member

Registered: 2010-01-13

Posts: 15

Re: [solved] smb-Accessing to a samba server does not work anymore.

Thank you.

WFV

Member

From: ☭USSA⛧⭒⭒⭒⭒

Registered: 2013-04-23

Posts: 288

Re: [solved] smb-Accessing to a samba server does not work anymore.

It looks like for some setting smb.conf

client max protocol =

to CORE works, and for others setting it to default works, else roll back. According to Samba default = SMB3_11. So if devices on the network are Win10 (or devices requiring smb3_11) then yes "default" will work, and for older Windows machines or devices that aren't SMB3, it won't.

default

works for my W10 machines on the network, but doesn't connect my older devices. As mentioned in that other thread and elsewhere, Samba 4.11.3 moves away from SMB1 potential vulnerabilities.

EDIT: Samba-4.12.0-3 in Testing but doesn't appear to address the connection issues, more to do with mit-ad-dc and ceph

Last edited by WFV (2020-04-05 21:22:40)

---

∞ hard times make the strong, the strong make good times, good times make the weak, the weak make hard times ∞

nuts

Member

Registered: 2010-01-13

Posts: 15

Re: [solved] smb-Accessing to a samba server does not work anymore.

I don't install samba on my client computers, just gvfs. I can't configure the nas, because it's not mine. So there is not any smb.conf in my system. I've followed the URL above and I downgrade smbclient and co.

It works.

progandy

Member

Registered: 2012-05-17

Posts: 5,190

Re: [solved] smb-Accessing to a samba server does not work anymore.

smbclient reads /etc/samba/smb.conf as well. You could create that file by hand without installing samba.
https://manned.org/smb.conf.5

client min protocol
client max protocol

Last edited by progandy (2020-04-06 11:14:53)

---

| alias CUTF='LANG=en_XX.UTF-8@POSIX ' |

nuts

Member

Registered: 2010-01-13

Posts: 15

Re: [solved] smb-Accessing to a samba server does not work anymore.

it works, thanks!

Last edited by nuts (2020-04-08 16:40:25)