similar to: Failed to convert SID to a UID

On 29/05/2023 16:29, Dale Renton via samba wrote: > Hello, > > After upgrading a Samba domain member from 4.16.4 to 4.17.5 our shares > stopped working. This is from Rocky Linux 8.7 to 8.8. The AD domain > controller server is running 4.16.2. Only error message I see is : > > check_account: Failed to convert SID S-1-5-21-..... to a UID > (dom_user[DOMAIN\username] Not

> check_account: Failed to convert SID S-1-5-21-..... to a UID > (dom_user[DOMAIN\username] > Not bothered about the SID, but what was the RID ? S-1-5-21-847089129-1187572071-3330553849-1107 > Also, does the username end with a '$' ? no > Network problem ? > What else changed ? Not a network problem and nothing else has changed. I just downgraded to Samba 4.16.4 from

Hi Experts, We encountered a weird issue after restarting the server. Seems everything working fine on the configuration side but the user?s not able to authenticate with the Samba server. Can you please help to investigate the issue? Our setup details and configuration file + error logs + service status. Samba:- 4.18.3-0 CentOS Linux release 8.4.2105 Authentication mechanism is SSSD [root at

More: users on the BRANDLILAW domain can access the share, but it's incredibly slow. In addition, smbd logs these errors repeatedly: Feb 16 18:49:06 roberts smbd[136]: check_account: Failed to convert SID S-1-5-21-2136821272-1111453333-1140905514-1601 to a UID (dom_user[BRANDLILAW\admin-fh$]) Feb 16 18:49:06 roberts smbd[136]: [2025/02/16 18:49:06.365450, 0]

On Mon, 17 Feb 2025 03:09:45 +0000 Stephen Brandli via samba <samba at lists.samba.org> wrote: > More: users on the BRANDLILAW domain can access the share, but it's > incredibly slow. In addition, smbd logs these errors repeatedly: > > Feb 16 18:49:06 roberts smbd[136]: check_account: Failed to convert > SID S-1-5-21-2136821272-1111453333-1140905514-1601 to a UID >

Hello all, We have been working on the idmap_rfc2307 solution for this. Packet traces on the Samba server and the LDAP server don't show any communication between Samba and the LDAP server at any point. (Configuration below). Samba logs are set at 10 and the error message is consistent: ../../source3/auth/auth_util.c:1946(check_account) check_account: Failed to convert SID

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).

Thank you for your prompt response, Rowland. The idmap_rfc2307 isn't working (yet) for me. I'm working down that path now, however I do need the homedir parameter from RFC 2307. ../../source3/auth/auth_util.c:1946(check_account) check_account: Failed to convert SID S-1-5-21-2286752186-3697686403-1823448917-102506 to a UID (dom_user[UNIV\someusername]) I have considered setting up a

On Sat, 3 May 2025 13:56:25 +0000 Shannon Price <pricesw at auburn.edu> wrote: > > Thank you for your prompt response, Rowland. > > The idmap_rfc2307 isn't working (yet) for me. I'm working down that > path now, however I do need the homedir parameter from RFC 2307. As far as I am aware, only the idmap_ad config backend can obtain the homedir and that only works

On Tue, 6 May 2025 15:39:34 +0000 Shannon Price <pricesw at auburn.edu> wrote: > > > Hello all, > > We have been working on the idmap_rfc2307 solution for this. Packet > traces on the Samba server and the LDAP server don't show any > communication between Samba and the LDAP server at any point. > (Configuration below). Well there wouldn't be. > Samba

Hi, I'm migrating a samba3-server that is used both as a NT4-DC and a filesver into a pair of samba4 servers, one should become the new AD-DC and the other one should be the new fileserver. The new AD-DC seems to work fine. I created all local unix users and unix groups on the new AD-DC before I started the classic upgrade and deleted all of them after the update was finished. That way the

Hi... We are still using NT4 classic domain with a couple of samba server but want to upgrade step by step to AD as a distant goal. We tried to upgrade to samba 4.17.7 as in intermediate step and keep LDAP for now but fail as we could not find a suitable example for id mapping. Hope someone can help! Previously we did run samba 4.7 on CentOS 7 without problems as domain controller and member

>Not a network problem and nothing else has changed. I just downgraded >to >Samba 4.16.4 from the Rocky Linux 8.7 repos, but left everything else as >Rocky 8.8, and everything is working fine. >Thanks, >Dale I?m running Rocky OS 9 with Samba 4.17.5. I have successfully set up Samba on other OSes with other (prior) versions but I?m encountering the exact same issue you are

Am 18. April 2023 14:29:29 MESZ schrieb Roland Schwingel via samba <samba at lists.samba.org>: >Hi... > >We are still using NT4 classic domain with a couple of samba server but >want to upgrade step by step to AD as a distant goal. >We tried to upgrade to samba 4.17.7 as in intermediate step and keep LDAP >for now but fail as we could not find a suitable >example for

Hi again, I had to let this rest for some time, but now, there are new data points available. Am 15.04.2025 um 10:16 schrieb Rowland Penny via samba: > On Mon, 14 Apr 2025 23:13:25 +0200 > Paul Leiber via samba <samba at lists.samba.org> wrote: > >> Am 14.04.2025 um 21:11 schrieb Rowland Penny via samba: >>> On Mon, 14 Apr 2025 15:50:50 +0200 >>> Paul

Hello Rowland and Christian Thanks for your replies... Yes ONEVISION and MYDOM are the very same here. Copy/Paste. "Christian Naumer" <christian.naumer at greyfish.net> wrote on 18.04.2023 20:12:35: > Am 18. April 2023 14:29:29 MESZ schrieb Roland Schwingel via samba > <samba at lists.samba.org>: > >Hi... > > > >We are still using NT4 classic

It works for us with Rocky Linux 8.8 and Samba 4.17.5. DCs are Samba 4.18.2. Looking at your conf I see this: I do _not_ have this: idmap config DOMAIN:unix_primary_group = yes I have and you don't: disable netbios = yes smb ports = 445 server min protocol = SMB2 client min protocol = SMB2 Different: kerberos method = secrets and keytab And this is deprecated: winbind nss info =

On Fri, 23 May 2025 20:42:23 +0200 Paul Leiber via samba <samba at lists.samba.org> wrote: > > However, here is a new angle: I have the suspicion that a temporarily > missing DC has to do with my issue. I installed a second DC (for > redundancy) on a Raspberry Pi some time ago. I had problems with the > setup of the Raspberry Pi, therefore this DC2 was inactive for some

On 18/06/2023 16:29, Dale Renton via samba wrote: > On Sat, Jun 10, 2023 at 1:49?PM Rowland Penny via samba < > samba at lists.samba.org> wrote: >> Dale, just checking back on what you posted earlier and you had: >> >> create krb5 conf = no >> >> in your smb.conf >> >> Is that line still there ? >> If so, try removing it. >>

Thanks for the suggestions. I tried them without success. Strange that wbinfo works but getent does not. On Wed, May 31, 2023 at 10:55?AM Christian Naumer < christian.naumer at greyfish.net> wrote: > It works for us with Rocky Linux 8.8 and Samba 4.17.5. DCs are Samba > 4.18.2. > > > Looking at your conf I see this: > > I do _not_ have this: > > idmap config