similar to: Windows 2019 compatibility

/etc/resolv.conf (Both DC's (windows) listed) domain ho-pla.se search ho-pla.se nameserver 10.0.2.10 nameserver 10.0.2.64 /etc/krb5.conf [libdefaults] dns_lookup_realm = false dns_lookup_kdc = true default_realm = HO-PLA.SE On Tue, Aug 6, 2024 at 9:01?PM Luis Peromarta via samba <samba at lists.samba.org> wrote: > > What?s the content of krb conf file and resolv.conf?

Rowland, you nailed it. I had both libpam and libnss installed, but they were not automatically upgraded together witn winbind and samba. They were still on 4.17 from the staged upgrade, but now updated to 4.20. And the shares are working again! Amazing :) Thanks Anders On Tue, Aug 6, 2024 at 9:19?PM Rowland Penny via samba <samba at lists.samba.org> wrote: > > On Tue, 6 Aug 2024

Agreed, I will keep the NT1 share on a separate VM and create a new one for the other services. Air-gapping will be difficult though, but I will check what can be done. Thanks On Wed, Sep 25, 2024 at 11:20?AM Rowland Penny via samba <samba at lists.samba.org> wrote: > > On Wed, 25 Sep 2024 11:08:24 +0200 > Anders ?stling via samba <samba at lists.samba.org> wrote: > >

Hi Thanks for the tip, but i have tried that too. No go. The only thing right now that works is to omit S from /COPY:DATSO, ie skip security descriptors. Makes no sense but that's what I have found out after dozens of tests. I will recreate the shares and be careful to follow Rowlands advise on setting the correct rights on the share. m?n 19 juni 2023 kl. 23:42 skrev spindles7 via samba

Well spoken. If I understand correctly, OP's organisation is a Russian STATE agency, so they can ask for support from Putin and his war criminal friends. Not here. Not now and not ever. On Mon, Dec 4, 2023 at 9:46?AM Rowland Penny via samba < samba at lists.samba.org> wrote: > On Mon, 4 Dec 2023 06:12:23 +0000 > ??????? ?????? ????????? via samba <samba at lists.samba.org>

Hi Some may remember that I asked about configuring a Samba server for the legacy NT1 protocol due to a couple of old industrial systems that do not support SMB2/3. I noticed this today from the Samba server, probably doesnt mean anything but I still would like to ask the group. The server is of course joined to a domain and operates as it should. sysman at hp-srv03:~$ *net domain testjoin -U

Is it possible to have the "min client protocol" statements per share, or must they be global? I am asking since I have the NT1 limit on a specific Samba server with a share for an industrial robot with an ancient Linux/Samba implementation , but there are other shares on the same server that should be better protected with SMB3. Best regards -- ------ -------------------- 8

I wrote a message a couple of days ago asking about Samba and SMB protocol levels on an old industrial robot with a pre-2010 Samba. That was resolved successfully. I now have another question concerning the same systems (the robots and the new Samba server, HP-SRV03). root at hp-srv03:/ *smbclient -L localhost -U administrator* Enter HPLTS\administrator's password: Sharename Type

On Tue, Jun 30, 2020 at 11:57 AM Rowland penny via samba <samba at lists.samba.org> wrote: > > On 30/06/2020 10:34, Anders ?stling wrote: > > On Tue, Jun 30, 2020 at 11:24 AM Rowland penny via samba > > <samba at lists.samba.org> wrote: > >> On 30/06/2020 09:50, Anders ?stling wrote: > >> > >>>> You have 'workgroup = HPLTS' and

Hi I'd like to learn more on the pros and cons of a mixed domain that consists of both MS and Samba domain controllers and member servers. What I have learnt so far is this; I created a new lab domain with an MS DC 2019. I then added a Samba 4.19-3 file server as a domain member w/o any issues. The clients are 2 Win 10 VM's for tests of shares, GPO's and related technologies. Still

I am not convinced that it's a Samba issue, but someone might be able to answer anyway We replicate directories and files from a Windows 2019 server to two destinations, both are supposed to be used in case of a disaster, but are also used for some specific tasks. One of the replication targets is a physical Windows 2012 server and the other one an Ubuntu/Samba virtual machine. The Samba VM

On Tue, 6 Aug 2024 20:41:51 +0200 Anders ?stling via samba <samba at lists.samba.org> wrote: > Hello > I have an older Debian 11 with Samba 4.13 as domain member serving som > industrial systems with files. > Today I decided to upgrade both Debian (to 12) and Samba (to 4.17 and > then 4.20). The upgrade using the backport repo worked after some > extra steps. Som

Hi Rowland, and thank you for quick feedback On Wed, Jun 17, 2020 at 6:45 PM Rowland penny via samba < samba at lists.samba.org> wrote: > On 17/06/2020 17:27, Anders ?stling via samba wrote: > > So my question is; does Win 7 behave differently than Win 10? The shares > > are the same as for the Win 10 clients, including the home directories. > Yes, unless you have changed

On Mon, 6 May 2024 09:06:36 +0200 Anders ?stling via samba <samba at lists.samba.org> wrote: > Hi > Some may remember that I asked about configuring a Samba server for > the legacy NT1 protocol due to a couple of old industrial systems > that do not support SMB2/3. > I noticed this today from the Samba server, probably doesnt mean > anything but I still would like to ask

On Wed, 25 Sep 2024 11:08:24 +0200 Anders ?stling via samba <samba at lists.samba.org> wrote: > Is it possible to have the "min client protocol" statements per share, > or must they be global? I take you meant 'client min protocol', that is a global setting and cannot be per share. > > I am asking since I have the NT1 limit on a specific Samba server with

On Fri, 3 May 2024 15:19:01 +0200 Anders ?stling via samba <samba at lists.samba.org> wrote: > I wrote a message a couple of days ago asking about Samba and SMB > protocol levels on an old industrial robot with a pre-2010 Samba. > That was resolved successfully. I now have another question > concerning the same systems (the robots and the new Samba server, > HP-SRV03). >

On Tue, Jun 30, 2020 at 11:24 AM Rowland penny via samba <samba at lists.samba.org> wrote: > > On 30/06/2020 09:50, Anders ?stling wrote: > > >> You have 'workgroup = HPLTS' and 'idmap config dg11', again, they must match > > As I wrote in the previous reply, that was a mistake from the initial > > deployment. However, I have a copy of the VM and

Hi all I have setup a Samba server for a client, and most things work fine (except a strange problem with some clients and SMB1). However, when I created the virtual server before migrating it to the client, I obviously forgot to change a parameter. [global] netbios name = CLIENTNETBIOSNAME realm = CLIENTNETBIOSNAME.SE workgroup = CLIENTNETBIOSNAME idmap config * : backend = tdb idmap config * :

?and this is a Debian Bookworm with back ported packages. Samba-tool should belong to samba-common-bin which I have installed from the backports. But it isn't there. On 3 Oct 2024, at 20:58, Anders ?stling <anders.ostling at gmail.com> wrote: samba-tool seems not to be installed on this member server. Isn?t that command only available in the samba-ad-dc suite? On 3 Oct 2024, at

I have a client with 10+ Windows 10/32-bit clients and 3 Windows 7/32-bit. I converted them today to Samba 4.12, and after some fixes, I now have working shares and roaming profiles for the Win 10 clients. However, the Win7 clients dont get the shares mapped at logon properly (at all). I tried to run the netlogon script manually from Windows/Sysvol/sysvol/<domain>/scripts after mounting the