similar to: Upgrade from 4.7 and Idmap check

On Thu, 6 Feb 2025 07:32:48 -0300 Edson Tadeu Almeida da Silveira via samba <samba at lists.samba.org> wrote: > Good morning everybody. > > I searched the list here but I haven't found anything close to my > problem yet. > > I'm using 2 DCs Samba 4.7 and now planning to upgrade to 4.21. So, not in a rush then, seeing as 4.7.x went EOL from the Samba point of

> > 2- I the log.smbd: > > > > [2025/02/06 06:55:04.483261, 1, traceid=3] > > > > 3 - When issue the command: 'samba-tool ntacl sysvolcheck' i receive: > > > > ERROR(<class 'OSError'>): Could not access > > /usr/local/samba/var/locks/sysvol/mydom.local: No data avaiable - > > [Errno 61] No data

On Thu, 6 Feb 2025 09:04:21 -0300 Edson Tadeu Almeida da Silveira <edson.tadeu at gmail.com> wrote: > > > 2- I the log.smbd: > > > > > > [2025/02/06 06:55:04.483261, 1, traceid=3] > > > > > > 3 - When issue the command: 'samba-tool ntacl sysvolcheck' i > > > receive: > > > > > > ERROR(<class

Hi guys! I'm looking for a way to solve the problem between my Samba 4.4.4 DC and my samba 4.3 File Server. The users and groups ids are not the same in both servers and i can't find the solution for this. Can anyone help me? This is the environment: DC: Samba 4.4.4 ------------------------ smb.conf: [global] interfaces = lo eth0 workgroup = DOMAIN realm = DOMAIN.LOCAL netbios

Il 06/12/24 10:45, Rowland Penny via samba ha scritto: > On Fri, 6 Dec 2024 10:19:31 +0100 > Mitja Tav?ar via samba <samba at lists.samba.org> wrote: > >> But the machine accoounts are not completely lost, they seem lost if >> i query the Read Only DC, when i query some of the other DC the >> machine accounts result ok. >> >> I'have found that

I'm not able to access a samba file server that I recently created and joined to a domain. I have two domains with an external trust: BRANDLILAW and BRANDLI. The server is joined to BRANDLILAW. I am trying to access it from a user on the BRANDLI domain. This worked with the prior server that the new server is replacing. All domain controllers and the server are Debian backports (21.3).

I recently upgraded my Samba Domain Member server that provides a share for Windows clients to write their backups to. The backup clients use an AD credential to connect to the share, so individuals are not connecting to the share. This works well and has for years. However, when I upgraded to Samba v4.21.3 (built from source, same distro as my Samba AD DCs), I started getting my logs cluttered up

On Fri, 6 Dec 2024 12:29:03 +0100 Mitja Tav?ar via samba <samba at lists.samba.org> wrote: > Il 06/12/24 10:45, Rowland Penny via samba ha scritto: > > On Fri, 6 Dec 2024 10:19:31 +0100 > > Mitja Tav?ar via samba <samba at lists.samba.org> wrote: > > > >> But the machine accoounts are not completely lost, they seem lost > >> if i query the Read

On Fri, 6 Dec 2024 10:19:31 +0100 Mitja Tav?ar via samba <samba at lists.samba.org> wrote: > > > > When you say '30 servers' is this 30 servers plus clients, or 30 > > servers including clients ? if the former, then I suggest you > > upgrade to an RWDC. > > Only the servers some of them are application servers therefore they > will become clients

Dear List, I am trying to set up Samba 3.6.25 (solaris 11.3 packaged) to provide unix file shares to windows users. I can successfully list groups and users with wbinfo -u / wbinfo -g, but I do not get any data with "getent group" or "getent passwd". In AD, we have set "gidNumber" Attribute for Group "Domain Users" to a value in the specified range

Hi guys! I´m experiencing a problem with samba 4 policies and acl and i don´t known how it starded to do. Some problems like copy Policies, edit them, etc. It seems like permissions, but i´ve checked the list and can´t find a solution. Here are some outputs that i hope can help to understand: # Sysvol permissions: drwxrwxrwx+ 3 root DOMAIN\domain admins 4096 Mar 7 12:17 sysvol #

Back on February 28, 2018, I started a thread "User permissions of profile/home directory lost" describing a problem occurring with my wife's user account. Since that time the random problem has persisted so I turned on some debugging. I have been able to determine that somehow her account idmap is broken. Here is the entry for my wife's SID as found in the idmap.ldb file

Release Announcements ===================== This is the first release candidate of Samba 4.19.? This is *not* intended for production environments and is designed for testing purposes only.? Please report any defects via the Samba bug reporting system at https://bugzilla.samba.org/. Samba 4.19 will be the next version of the Samba suite. UPGRADING ========= NEW FEATURES/CHANGES

Release Announcements ===================== This is the first release candidate of Samba 4.19.? This is *not* intended for production environments and is designed for testing purposes only.? Please report any defects via the Samba bug reporting system at https://bugzilla.samba.org/. Samba 4.19 will be the next version of the Samba suite. UPGRADING ========= NEW FEATURES/CHANGES

Release Announcements ===================== This is the second release candidate of Samba 4.19.? This is *not* intended for production environments and is designed for testing purposes only.? Please report any defects via the Samba bug reporting system at https://bugzilla.samba.org/. Samba 4.19 will be the next version of the Samba suite. UPGRADING ========= NEW FEATURES/CHANGES

Release Announcements ===================== This is the second release candidate of Samba 4.19.? This is *not* intended for production environments and is designed for testing purposes only.? Please report any defects via the Samba bug reporting system at https://bugzilla.samba.org/. Samba 4.19 will be the next version of the Samba suite. UPGRADING ========= NEW FEATURES/CHANGES

Release Announcements ===================== This is the third release candidate of Samba 4.19.? This is *not* intended for production environments and is designed for testing purposes only.? Please report any defects via the Samba bug reporting system at https://bugzilla.samba.org/. Samba 4.19 will be the next version of the Samba suite. UPGRADING ========= NEW FEATURES/CHANGES

Release Announcements ===================== This is the third release candidate of Samba 4.19.? This is *not* intended for production environments and is designed for testing purposes only.? Please report any defects via the Samba bug reporting system at https://bugzilla.samba.org/. Samba 4.19 will be the next version of the Samba suite. UPGRADING ========= NEW FEATURES/CHANGES

hi again. after some tests, (on my operational domain and on a new testdomain) i detected this behavior: on samba 4.11.6 sometimes the new DNS-records finisches on a wrong dns zone. the problem occurs, if more then 5 records are created with the same name in more then one domain zone for example: testa1.jupiter.mydom.org testa2.jupiter.mydom.org testa3.jupiter.mydom.org

Release Announcements ===================== This is the fourth release candidate of Samba 4.19.? This is *not* intended for production environments and is designed for testing purposes only.? Please report any defects via the Samba bug reporting system at https://bugzilla.samba.org/. Samba 4.19 will be the next version of the Samba suite. UPGRADING ========= NEW FEATURES/CHANGES