samba - Oct 2018 - Windows Server 2019 / Windows 10 LTSC can't access samba shares on Debian stable 4.5.12

Hello everyone,
when using samba 4.9.1 as a standalone filer, I need to start smbd and
nmbd, don't I?

I'm using:
/local/samba/sbin/smbd -s /local/samba-config/common/smb.conf
/local/samba/sbin/nmbd -s /local/samba-config/common/smb.conf

However smbd. Seems to ignore my lock directory:

(infra) [/local/samba-config/common] grep gencache_notrans.tdb log/smbd
  Opening cache file at /local/samba-4.9.1/var/lock/gencache_notrans.tdb
  Could not get allrecord lock on gencache_notrans.tdb: Locking error

Find smb.conf and log files here:

https://thomas.glanzmann.de/tmp/samba491standalonefile.tar.gz

Cheers,
        Thomas

On Sat, 13 Oct 2018 10:32:09 +0200
Thomas Glanzmann via samba <samba at lists.samba.org> wrote:
> Hello everyone,
> when using samba 4.9.1 as a standalone filer, I need to start smbd and
> nmbd, don't I?
> 
> I'm using:
> /local/samba/sbin/smbd -s /local/samba-config/common/smb.conf
> /local/samba/sbin/nmbd -s /local/samba-config/common/smb.conf
> 
> However smbd. Seems to ignore my lock directory:
> 
> (infra) [/local/samba-config/common] grep gencache_notrans.tdb
> log/smbd Opening cache file
> at /local/samba-4.9.1/var/lock/gencache_notrans.tdb Could not get
> allrecord lock on gencache_notrans.tdb: Locking error
> 
> Find smb.conf and log files here:
> 
> https://thomas.glanzmann.de/tmp/samba491standalonefile.tar.gz
> 
> Cheers,
>         Thomas
> 
OK, replace these lines:

        cache path = /local/samba-config/common/cache
        lock path = /local/samba-config/common/lock

        log file = /local/samba-config/common/log/%m

        ntp signd socket path = /local/samba-config/common/signd
        pid path = /local/samba-config/common/pid
        private dir = /local/samba-config/common/private
        state path = /local/samba-config/common/state

With these lines:

        cache directory = /local/samba-config/common/cache
        lock directory = /local/samba-config/common/lock

        log file = /local/samba-config/common/log/%m

        pid directory = /local/samba-config/common/pid
        private dir = /local/samba-config/common/private
        state directory = /local/samba-config/common/state

You will note that the 'ntp signed' line has been removed, this is on
purpose, it is only required on an AD DC.

Rowland

Hello Rowland,
>         cache directory = /local/samba-config/common/cache
>         lock directory = /local/samba-config/common/lock
>         log file = /local/samba-config/common/log/%m
>         pid directory = /local/samba-config/common/pid
>         private dir = /local/samba-config/common/private
>         state directory = /local/samba-config/common/state
> You will note that the 'ntp signed' line has been removed, this is
on
> purpose, it is only required on an AD DC.
thank you. That works, but there is one thing, I don't understand. In
the past there was a nmbd and smbd process. It seems that now only nmbd
is running, and if someone is connecting, smbd is spanned. Is that
correct?

Thanks to the feedback I have received by you and Andrew, samba is now
running on an unused ethernet interface. Thank you. However I still
can't access the windows share from the new windows versions, but I now
tried it from the cmd prompt and got a good error message:
> C:\Users\Thomas>net use \\10.109.0.1\tmp
> System error 1272 has occurred.
> You can't access this shared folder because your organization's
security
> policies block unauthenticated guest access. These policies help protect
> your PC from unsafe or malicious devices on the network.
The error code lead me to:

https://superuser.com/questions/1280365/can-not-connect-to-share-system-error-1272
https://support.microsoft.com/en-us/help/4046019/guest-access-smb2-disabled-by-default-in-windows-10-server-2016
https://getadmx.com/?Category=Windows_10_2016&Policy=Microsoft.Policies.LanmanWorkstation::Pol_EnableInsecureGuestLogons

The following command resolved my issue:

Set-ItemProperty -Path
"HKLM:\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters"
-Name "AllowInsecureGuestAuth" -Type DWord -Value 1

Afterwards it works. Also with the Debian Samba.

Cheers,
        Thomas