Has stopped supporting older smb protocols?

English Install/Boot/Login
21

Hi susejunky!

Many thanks for constructive answer! Highly appreciated!

No, there are no updates for these devices, I check once a year at least. But that’s not a problem, no exposure to internet/Windows. I replaced all HDDs in these 7 devices by fresh WD reds, so I will keep them for some more years…

I’m not willing to mount all these devices on all TW clients, it’s not worth the effort, as the NASs are only used for backups from time to time.

As the only option appears to be downgrading/locking samba-client I will go this way.

Thanks for all the helpful input!

22

No, it’s not the only option, but probably simplest for you I think.

23

Hi dino!

I volunteer myself on one or the other tech forum (yes, I’m not completely dull!) and my golden rule is: If I can’t write something constructive/positive, which helps the post opener to solve his problem, I simply don’t write anything at all… :wink:

Have a nice day!

24

And my recommendation is keep rants in the soapbox and when asking for assistance in a technical help forum, try to supply as much definitive information as possible. You were given some information needed to enable SMB1 on the client but chose to ignore it, or at least not ask for further clarification. Remote assistance is not always easy when others are not over your shoulder to check your network environment for themselves.

25

You might elaborate on this:

I don’t see any missing info from my side. TW, kernel version, samba version, all there. What do you miss?

26

Back in post #15, you were advised to edit smb.conf with

client min protocol=NT1

and this is also mentioned in the release notes. It can also be passed as an option if using smbclient.

Similar has recently been posted here BTW…
https://forums.opensuse.org/showthread.php/538028-dolphin-cannot-access-to-smb-server-192-168-204-86?p=2919310#post2919310

That should allow you to access a samba server supporting only SMB1.

27

The post by malcolm in the other thread is for the host, not for the client. :slight_smile:

But adding the proposed line to smb.conf really enables smb1 for the client! I always thought this config was only for the server…

Finally and in the end… :smiley:

28

No, those are client configuration parameters.

But adding the proposed line to smb.conf really enables smb1 for the client! I always thought this config was only for the server…

Finally and in the end… :smiley:

I did say that earlier. :wink:

29

Hi
Perhaps should have clarified on the host running the smb client :wink:

30

I ran into the same problem as you with my old Linkstation (LS-CHL) - see - https://forums.opensuse.org/showthread.php/538002-SMB1

What older NAS do you have?
If it is one of these (LS-XHL,LS-CHL,LS-WXL,LS-WSXL,LS-SL,LS-AVL,LS-VL,LS-WVL,LS-QVL,LS-XL,LS-YL,LS-WXBL ) it is actually possible to enable smbv2

Just make sure you have the latest firmware installed (currently 1.74) and follow the instructions in this thread . . .

31

oops - sorry - wrong link on how to enabl smbv2
Try this one . . .

32

Hey, nice!

If I try to access the linkstation on port 22 I get:

Unable to negotiate with 10.100.110.34 port 22: no matching key exchange method found. Their offer: diffie-hellman-group-exchange-sha1,diffie--group1-sha1

I didn’t know ssh is active on these little beasts! But I would have to root the device first (the linked blog thread is not readable here, too many scripts from facebook, wp etc. need to be allowed, apparently), if I understand the buffalo forums correctly…

I tried to install debian on an older one 2 years ago (found a presentation on the interwebs), took me some time and in the last step I made a mistake, so debian was there but not fully functional (don’t remember the details…).

https://miniconf.debian.or.jp/assets/files/Debian%20Installer%20for%20Buffalo%20Linkstation%20NAS.pdf

33

hmmmm . . . not sure why you can’t read the linked forum thread - it’s just the standard Buffalo message board - no login required.
Anyway - it’s this message specifically that you need to follow but you can ignore the parts about putty and just use ssh in Suse

First you need to enable ssh on the linkstation - download acpcommander-gui (the jar file will run on linux)
disable your firewall while doing all these tasks . . .
using acp commander enable ssh and set root password as root

then ssh into your nas


ssh -oKexAlgorithms=+diffie-hellman-group1-sha1 root@nasipaddress

then

vi  /etc/init.d/smb.sh

scroll to the end of

/usr/local/sbin/nas_configgen -c samba
        if  $? -ne 0 ]; then
                echo "$0 configure fail"
                exit 1
        fi

and add

/bin/sed -i '3i\\    max protocol = SMB2\\' /etc/samba/smb.conf

then hit
[ESC]:wq

after that restart smb on the nas


/etc/init.d/smb.sh restart
34

Many thanks for the details!

Just two questions before I start:

  • Can I change the default password for root or disable ssh again afterwards? Otherwise an old ssh running with root-root appears to me as the more important security issue compared to smb1 :smiley:

  • Wouldn’t it be better to add

 ... **min** protocol = SMB2 ...

instead of max protocol?

35

Yes. I’ve completed you can change the root password and/or disable ssh using acp Commander.
Not sure on the max vs min. I just copied from Buffalo forums and is working.

36

yes, definitely change your root password after you have made the changes. You can do this, and also disable ssh using acpcommander

As for min vs max . . . I’m not sure . . . I just copied the line from the Buffalo forums and it works.