I am thinking about biting the bullet and upgrading from Slackware 14.0 to -current, but no devices on my LAN (neither Linux nor Windows not iOS) recognize my SAMBA share running -current, and all of them do recognize it running the identical smb.conf in 14.0.

I have simple needs. One share called 'PublicDirectory' mounted at /mnt/dv/public. Guests OK. read/write allowed.

Ideas appreciated.

My current smb.conf:


[global]
workgroup = HOME
server string = %h server
#security = SHARE
# Next 2 lines are a hack because SHARE security now invalid
security = USER
map to guest = Bad User
log file = /var/log/samba/log.%m
max log size = 105000
dns proxy = No
hosts allow = 192.168.8.
hosts deny = ALL
local master = yes
preferred master = yes


[PublicDirectory]
path = /mnt/dv/public
read only = No
guest ok = Yes

I suspect that this is the reason: https://github.com/samba-team/samba/...7/WHATSNEW.txt

What it means is that you might not be able to 'see' the server using it's hostname any more.

You should still be able to see it from Windows Explorer using the IP address like this in the address bar: \\1.2.3.4\PublicDirectory

Windows 10 is a little more fussy, and wants to be connected to a domain, so you need to specify the user name in the format DOMAIN\username. But you can trick it and use (almost) anything before the \

No it isn't and no it doesn't. Windows 10 can still connect to a standalone server, it just cannot do it using SMBv1 by default any more. If you want to use SMBv1, you will need to ensure that Win10 is using it and add these lines to your smb.conf:

client min protocol = NT1
server min protocol = NT1

This is not recommended.

One fallout of the removal of SMBv1 is that Network Browsing no longer works, this is not a problem for Windows, it hasn't used Network Browsing for a few years. Windows now uses Network Discovery and you can get a server to do this on a Linux client here: https://github.com/christgau/wsdd

In my experience it is and does. So my experience clearly differs to yours.

Thank you for your ideas. However, I am still confused.

Neither my Linux clients nor my Windows 10 clients can see the samba share in -current. When I revert to 14.0, they all can. I don't see a way a change (or a deprecation) in Windows 10 explains this. The only difference in the 'natural experiment' is a change in the server from the samba on 14.0 and the samba in -current.

And yes, I also tried using the IP address instead of the hostname, using both Windows and Linux clients. No joy.

My experience of Samba is massively greater than yours, can I suggest that you do not pick an argument unless you know who you are picking an argument with

It is my understanding Slackware was using Samba 4.4.4 and is now using 4.13.0, a massive jump of 9 major versions. There have been multiple changes between those versions, some of which being that 'ntlm auth' now defaults to no and the minimum supported protocol is now SMBv2 by default. You need SMBv1 for Network Browsing, no SMBv1, no Network Browsing.

So, you either turn SMBv1 back on everywhere, or you use SMBv2 everywhere and get used to a different way of doing things.

>It is my understanding Slackware was using Samba 4.4.4

Your understanding may have been accurate at one point but factually is incorrect.
smbstatus
Samba version 4.6.16

Further, one of my clients reports in plain text that it is seeing a SMB 2 server. So your understanding that the 14.0 server defaults to SMBv1 is also incorrect.

I repeat again that my clients running current versions of Windows 10 AND my clients running Linux have no problem whatever seeing the samba share running in 14.0. They are fine with the 'ancient' samba running in 14.0. To repeat thrice, the 14.0 version works perfectly, but the New Improved samba in current makes the share running the exact same smb.conf disappear for every one of my Windows and Linux clients.

I do not use Slackware, so I rely on what I read elsewhere, but what matters is the Samba version, it doesn't really matter if it is 4.4.x or 4.6.x, they both use SMBv1.

If your Windows 10 computer can see the Samba 4.6.16 machine in Explorer, then your Windows 10 machine has SMBv1 enabled. The latest versions of Samba (from 4.11.0) have SMBv1 turned off by default and as I have already said, no SMBv1, no Network Browsing, or to put it another way, they do not appear in Explorer on Windows 10.

If you want then to reappear, you need to turn SMBv1 back on again, you can do this by adding:
client min protocol = CORE
server min protocol = LANMAN1

To your smb.conf on your Slackware machine, this reverts the change made at 4.11.0

It isn't recommended to do this though, because SMBv1 is very insecure.

You are a relative unknown on the LQ forum and we don't know who you are (just as you likely don't know who rkelsen is). Might I suggest that instead of chest thumping, you provide some links to counter what rkelsen said rather than just say you know more than they do?

As rpenny mentioned, the issue is likely due to Samba disabling SMBv1 support by default on the version included in -current. If you want the server to be accessible without opening yourself up to the SMBv1 vulnerabilities, you could use wsdd2. Make sure to read the README as you'll need to add the startup script to your /etc/rc.d/rc.local file.

Well then please enlighten me, oh wise one, as to why after the April Windows update (to v2004) all of my clients disconnected and refused to reconnect until we tried the DOMAIN\username format?

I eagerly anticipate receiving your pearls of wisdom. It is truly an honour to receive them from the fountain of all knowledge of everything SAMBA related.

FYI: I wasn't arguing. I was merely stating facts my friend.

1 members found this post helpful.

Well then please enlighten me, oh wise one, as to why after the April Windows update (to v2004) all of my clients disconnected and refused to reconnect until we tried the DOMAIN\username format?

I eagerly anticipate receiving your pearls of wisdom. It is truly an honour to receive them from the fountain of all knowledge of everything SAMBA related.

FYI: I wasn't arguing. I was merely stating facts my friend.

1 members found this post helpful.

Can you ping the new server from one of the Windows machines?

From a Linux client, what happens when you run:

$ smbclient -L IP_address_of_server -U username

The Domain\username format format might depend on if you are running the Home, Pro versions or Build no. I have a laptop with Windows 10 Home 2004 and do not need to enter Domain\username. SMBv1 has been removed from the Windows. In the file browser I just use \\hostname\share. The workgroup should be the same on all computers. I have physical CentOS box and several other misc VirtualBox virtual machines.

Believe it or not I just installed current ISO in a VirtualBox VM and the laptop could see the share as duplicated from your original post.

I have an environment with both Windows 10 Home and Pro versions, and can connect to both using \\hostname\share. (In fact I can reach using the Avahi hostname .local schema without issue.)

'Connecting' and 'Seeing' are different things, but both may require SMBv1 to succeed. To 'see' a share, you need either Network Browsing or Network Discovery. Network Browsing requires SMBv1, no SMBv1, no Network Browsing. Linux does not really have a Network Discovery server (or client), but there are a few on github.

This thread started because the OP seemingly couldn't 'see' their shares any more, this is what I was replying to.

You brought up 'Connecting' and this should still work, provided you don't use SMBv1 without ensuring that all computers are using SMBv1.