Thanks for the response Rowland. After setting an UID manually for one
of the Windows computers, Samba is logging another message on the file
servers (multiple times in a row, maybe more times than the previous
message):
[2023/01/25 14:09:35.198587, 0]
../../source3/auth/auth_util.c:1937(check_account)
check_account: Failed to find local account with UID XXXXXXXXX for
SID S-X-X-XX-XXXXXXXXX-XXXXXXXXXX-XXXXXXXXXX-XXXX
(dom_user[SMB\host-xxx$])
Is that normal too?. How could we avoid it?.
On Mon, Jan 23, 2023 at 12:32 PM Rowland Penny via samba
<samba at lists.samba.org> wrote:>
>
>
> On 23/01/2023 15:21, tizo via samba wrote:
> > We have a couple of hosts running Samba 4.16.5 as AD DC. Besides, we
> > have other hosts with Samba 4.15.5 as file servers. From time to time
> > the file shares that are mounted with cifs from some Linux clients get
> > stuck.
> >
> > All I can see in Samba logs on the file servers, are message like:
> >
> > check_account: Failed to convert SID
> > S-X-X-XX-XXXXXXXXX-XXXXXXXXXX-XXXXXXXXXX-XXXX to a UID
> > (dom_user[SMB\host-xxx$]), being host-xxx one of the Windows computer
> > client.
> >
> > Is this message normal?. Or should I set an UID manually for Windows
> > computers as I do for users and groups (as idmap backend is ad)?.
>
> That is perfectly normal, on Windows a computer is a user with an extra
> objectclass. On Linux, a computer is just a computer. You can either
> ignore those messages or you can do as you suggest, give each computer a
> uidNumber attribute.
>
> >
> > What about the problem?.
>
> No idea, not enough info provided.
>
> > Could it be related to the message?.
>
> I doubt it.
>
> Rowland
>
> --
> To unsubscribe from this list go to the following URL and read the
> instructions: https://lists.samba.org/mailman/options/samba