{"id":7536,"date":"2025-11-09T07:02:15","date_gmt":"2025-11-09T13:02:15","guid":{"rendered":"https:\/\/www.logikalsolutions.com\/wordpress\/?p=7536"},"modified":"2025-11-09T07:02:15","modified_gmt":"2025-11-09T13:02:15","slug":"samba-share","status":"publish","type":"post","link":"https:\/\/www.logikalsolutions.com\/wordpress\/information-technology\/samba-share\/","title":{"rendered":"Getting Samba Share to Work on MX Linux"},"content":{"rendered":"\n

I really like MX Linux<\/a>, but with Samba Shares they shot themselves in the foot. The GUI tool is nice, but they made some bad decisions. Yes, I’ve written about Samba Shares and NAS before on this blog<\/a>. If developers would just quit dicking with it, adopt a single standard, and live with that, you wouldn’t need so many blog posts.<\/p>\n\n\n

\n
\"\"<\/figure>\n<\/div>\n\n\n

Gotta admit, the GUI tool is straight forward. You have a nice dialog for creating a Samba Share.<\/p>\n\n\n

\n
\"\"<\/figure>\n<\/div>\n\n\n

They even include a tab for users to remind you about creating Samba users. No, they don’t use your Linux user\/password file. Samba has its own thing. Yes, you will probably replicate your linux username and password despite all the advice to the contrary. The reason they don’t utilize your Linux user information is the entire point of Samba Shares is to share with other users\/machines. They don’t all have an account to log in on your machine, but you can collaborate in a share.<\/p>\n\n\n

\n
\"\"<\/figure>\n<\/div>\n\n
\n
\"\"<\/figure>\n<\/div>\n\n\n

Where it Fails<\/h2>\n\n\n\n

Despite the rest of the known universe keeping share definitions in \/etc\/samba\/smb.conf, the GUI tool does not. This wouldn’t be so bad, but all the documentation you find online instructs users to edit this file. Adding insult to injury, you still have to edit this file.<\/p>\n\n\n

\n
\"\"<\/figure>\n<\/div>\n\n\n

For some inexplicable reason the default workgroup is “Workgroup” instead of WORKGROUP like it has been since Windows first got networking.<\/p>\n\n\n\n

Another mystifying question is why they didn’t go ahead and install winbind and smbclient.<\/p>\n\n\n

\n
\"\"<\/figure>\n<\/div>\n\n
\n
\"\"<\/figure>\n<\/div>\n\n\n

In for a penny, in for a pound.<\/p>\n\n\n\n

You Still Can’t Connect<\/h2>\n\n\n\n

Once you get everything installed and configured, you reboot your MX Linux machine and machines on your local network cannot connect. If they cannot see your machine it is because you forgot to change Workgroup to WORKGROUP or whatever non-standard workgroup name you chose. That, of course requires another reboot.<\/p>\n\n\n

\n
\"\"<\/figure>\n<\/div>\n\n\n

The GUI tool for creating Samba Shares doesn’t open the machine to incoming connections. Despite the GUI looking nice, I don’t like it. You have to really know what you are doing to edit Rules. There is a nice looking GUI but it’s not nice like a check box for “allow CIFS” and “allow Samba.” Having Allow, Reject, Deny for your zone combo box doesn’t fill me with warm and fuzzies. Makes it sound like <\/p>\n\n\n\n

\n

Russia, China, North Korea and every other deviant country, come steal my identity and money!<\/p>\n<\/blockquote>\n\n\n\n

Admittedly you have to search online, but with CachyOS and other Arch based distros<\/p>\n\n\n\n

<\/circle><\/circle><\/circle><\/g><\/svg><\/span>