Has stopped supporting older smb protocols?

**suse_rasputin** · 07-Nov-2019, 03:29

Hi!

I have some older Buffalo NAS with oooold smb versions. Worked fine till some days ago, now I can't access these shares from KDE/Dolphin any more, I get

Code:

Unknown error condition in stat: Software caused connection abort

while Leap 15.1 ha no problems at all. Tried from different TW installs, reboot didn't help.

Any ideas?

**suse_rasputin** · 07-Nov-2019, 07:14

How crazy is that? The world is full of Windows XP and 7 machines, supporting smb1 and even on Windows 10 you can install support for smb1.

But the linux samba guys decide to make the world a better place by deleting support for smb1, although the vulnerabilities are on the Windows part of the universe. These guys should adjust their medication....

**hcvv** · 07-Nov-2019, 07:31

I am not a SAMBA user, but I do not understand this.

You get an error message, but instead of trying to get help here with understandng the message and repairing things, you jump to the conclusion that it isn't is supported anymore and then you start ranting to people who do not even visit these forums.

Either you want technical help and then provide as much technical information you can, or you post in Soapbox (but even there you are restricted in what you say).

Venting frustration here will at the most deter people to provide help.

**suse_rasputin** · 07-Nov-2019, 08:34

https://tech.slashdot.org/story/19/0...ion-by-default

Code:

smbstatus

Samba version 4.11.0-git.95.c88b5f2c0c6SUSE-oS15.5-x86_64

**hcvv** · 07-Nov-2019, 09:00

A short glance tell me that it talks about "on by default". Thus find out how to switch it on (probably in one of the configuration files).

Again, I do not use SAMB, but what I say above looks as the most logical step to me.

**hcvv** · 07-Nov-2019, 09:03

See also this one:
https://forums.opensuse.org/showthre...=samba+version

**suse_rasputin** · 07-Nov-2019, 09:09

I have no Windowz on these networks. Mounting the NAS in fstab is not an option, if the mount fails the machine will not boot.

**hcvv** · 07-Nov-2019, 09:49

Originally Posted by suse_rasputin

I have no Windowz on these networks. Mounting the NAS in fstab is not an option, if the mount fails the machine will not boot.

I do not understand why you are switching subjects, but adding the option nofail to the fstab entry will avoid the system hang on boot when the server is unavailable.

**suse_rasputin** · 07-Nov-2019, 10:16

Hmmmmm...., the final 2 posts in the thread you linked, maybe? ;-)

**hcvv** · 07-Nov-2019, 10:36

I did not read that whole thread. I had the vague idea that I had seen something like your problem earlier, searched for it, found it and offered you the link (something you could have done yourself btw).