search for: ltsc

On Sat, 13 Oct 2018 10:17:19 +0200 Thomas Glanzmann via samba <samba at lists.samba.org> wrote: > Hello Andrew, > > > Do you actually have any ethernet interfaces up? Why are you not > > binding Samba to that? > > I do, but I run multiple samba servers on one machine. I have a few > active directory controllers bound on a per VLAN basis to different >

On Sat, 13 Oct 2018 10:43:31 +0200 Thomas Glanzmann via samba <samba at lists.samba.org> wrote: > Hello Rowland, > > > Stop me if I am wrong (and I often am), but doesn't the 'loopback' > > device do exactly that ? Anything 'lo' receives on its input just > > gets shoved out of its output, or to put it another way, it just > > goes around

On Sat, 13 Oct 2018 16:14:44 +0200 Thomas Glanzmann <thomas at glanzmann.de> wrote: > 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 > >

Hallo Rowland, > How are you checking, what is the actual command you are using ? the problem was that the debian samba was listing on all interface even if I told him not to do so. So the new one never worked for me. I only thought it would but it was actually served by the old one. The current smbd seems to still choke on me not having winbind. Is there a way to disable winbind? Current

Hello Rowland, > There are actually 4 Samba processes: > samba, only used on a DC and this starts any other required processes. > smbd, this is the cifs process > nmbd, the netbios browsing process > winbind, authentication process > The above is a rather simplistic view, but I hope you get the idea. > on a standalone server, you need the smbd process to be running and

Hello Rowland, > Stop me if I am wrong (and I often am), but doesn't the 'loopback' > device do exactly that ? Anything 'lo' receives on its input just gets > shoved out of its output, or to put it another way, it just goes > around in a circle, so how does this work with Samba etc ? Not saying > it will not work, trying to understand how it works if it does

...browseable = No public = Yes guest only = Yes writable = No directory = /export/ISO I'm using Debian 9.5 with samba version 4.5.12+dfsg-2+deb9u3. I can access the share find with windows xp - windows server 2016. However with Windows Server 2019 and Windows 10 LTSC I can't access it. Any idea what I have to change? I already tried to use samba-4.9.1 with the following configuration: [global] workgroup = DIRECTORY interfaces = 10.10.10.1 security = user map to guest = Bad User rndc command = /bin/true # serv...

Hello Andrew, > Do you actually have any ethernet interfaces up? Why are you not > binding Samba to that? I do, but I run multiple samba servers on one machine. I have a few active directory controllers bound on a per VLAN basis to different interfaces. And one additional samba just for shares that should serve all VLANs. That is why I have the 10.10.10.1 on the lo interface. I use that

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

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