You know, I really hate updates.
What I really hate is how the Linux world thinks a major (&)(&*ing change should go in a minor update. Not long ago I wrote this post on getting Manjaro to work with NAS and all was beautiful. Manjaro worked much like other mainstream Linux distros when it came to NAS.
Well we can’t have that!
One of the more annoying things about Manjaro KDE and NAS is the network discovery. Actually it is the support/development staff. One person fixes it so it works very main stream. Then someone else changes it back to an expert friendly hack.
If your one and only target market is a corporate desktop, I guess I can understand this. Department IT people will email you the server name(s) you have access to and tell you the credentials you should use. There could be thousands of network shares in a sizeable corporation.
You shouldn’t be seeking out regular users if you are really writing for the corporate market. First go read the post I linked to. It will provide you some frame of reference for this rant.
Pictures will help explain my current rant.
As you can see with Fedora 33, finding the NAS you want to use is a nice graphical progression. That assumes you have applied this hack so your Buffalo devices show up. You apply that same hack to Ubuntu for a more direct approach.
Ubuntu 20.04 LTS
With Manjaro (KDE at least, haven’t tried others) you have to click on Network, then double click “Add Network Folder.”
I think you are starting to see the “expert friendly” portion of this. Most mere mortal users won’t know how to find this information.
I’m sure there are hundreds of other ways. I’m also certain most GUI users aren’t going to did deep enough to find such obscure commands. They are just going to install Ubuntu, Fedora, etc.
Note, you still have to identify which shares are on the server.
If you have NAS on your network that supports the new standard, but your routers and some of your other NAS don’t support the SMB2 protocol this is what you have to do. None of your WORKGROUP drives will show up in the GUI because the router hosting your WORKGROUP doesn’t directly support the newer protocol.
Yes, we now have to apply the hack previously applied to Ubuntu and Fedora. It looks a little different here though.
sudo nano /etc/samba/smb.conf
Change the “client min protocol” line from SMB2 to NT1. Once you save that, if you are using the smbclient command in a terminal, you don’t even have to reboot. You do have to reboot so the GUI notices the change.
Once you reboot things will seem a bit more normal.
I know one thing for certain; not going to upgrade my router until my Buffalo NAS dies.