MX Linux Forum

Samba does not work for me in MX19.2 - I have tried editing the configuration file
as suggested by dedo'
https://www.dedoimedo.com/computers/ubu ... hares.html
but still get no joy in "Windows Network".

Has anybody managed to get Samba to work in MX19.2?

yes, but I have to direct address my shares, even from windows.

\\servername\sharename

I didn't do anything special, just used the usual samba config tool. the only thing that doesn't work is browsing for the share, but that hasn't worked for me for a while (I blame windows 10).

I had the same problem, but was helped here, and now have as much of it working as I need. I had to enter the following in a terminal as a one-off:
and after a reboot I could connect to my Linux machine from a Windows one.

Chris

Hello, have you tried enabling Samba 1.x in the Windows Programs and Features?

Step 1
Go to settings

Step 2
Click on Apps

Step 3
Click Programs and Features

Step 4
Click Turn Windows features on or off

Step 5
Check SMS 1.0/CIFI File Sharing Support

Thanks, gentlemen.

My complaint is that "Windows Shares" draws a total blank - it
does not even see my other Linuxes which are running.

BTW I do not use Windows10, only XP and 98se.

I can browse and connect to all my running machines from both XP and 98se:
so I believe the trouble is down to MX19.2's defective Samba.

I don't think this is a defective samba. I think this is a defective gvfs backend.

I would be willing to bet if you ran the following command it would list your servers and their shares: My suggestion:

Edit /etc/samba/smb.conf and right under the workgroup = WORKGROUP line add this one: Then restart smbd: In some cases you may need to reboot.

Morbius1 wrote: Thu Sep 03, 2020 3:02 pm My suggestion:

Edit /etc/samba/smb.conf and right under the workgroup = WORKGROUP line add this one:

Code: Select all

client max protocol = NT1

crborga wrote: Thu Sep 03, 2020 11:49 am Hello, have you tried enabling Samba 1.x in the Windows Programs and Features?

No one should ever use NT1 (SMB1) ever again.

It has been depreciated from Windows and Samba for a very big and good reason.
It is a huge vulnerability and exploit vector.

The actual and proper solution is out there though... we just have to find it.

GuiGuy wrote: Thu Sep 03, 2020 11:58 am BTW I do not use Windows10, only XP and 98se.

GuiGuy, is there a reason you're running these legacy systems?

If it is to use legacy Windows applications, have you attempted to use them with WINE?

So this is kind of forum I just entered. Understood.

The problem here is two-fold:

By default the "client min protocol" is already set to "core" in the version of samba you all are using so that's even worse.

From man smb.conf for "client min protocol":

Default: client min protocol = CORE

The second problem is that the "fix" to this problem was for the good folks over at gvfs central to force gvfsd-smb-browse to use smb1 in order to get the list of workgroups and servers in newer versions.

This all happened incidentally when samba decided to change the client max from NT1 in previous versions to SMB3_11. That messed up gvfs.