search for: wb_lookupsid

...invalid sid S-1-5-21-3018909051-3044254431-1064828747-1113 - S-1-5-21-3018909051-3044254431-1064828747-1291 The SIDs are valid, and point to a logged on user and their workstation. The winbindd.log file has thousands of entries like these: [2023/10/26 09:28:58.028357, 1] ../../source3/winbindd/wb_lookupsids.c:667(wb_lookupsids_recv) Failed with NT_STATUS_INVALID_SID. [2023/10/26 09:28:58.028372, 1] ../../source3/winbindd/wb_sids2xids.c:765(wb_sids2xids_recv) Failed with NT_STATUS_INVALID_SID. [2023/10/26 09:28:58.028385, 1] ../../source3/winbindd/winbindd_sids_to_xids.c:113(winbindd_sids_to_xid...

Here are the lines of the winbind.log justs after a restart of winbind: [2024/09/25 07:32:24.878544,? 1] ../../source3/winbindd/wb_lookupsid.c:102(wb_lookupsid_recv) ? Failed with STATUS_SOME_UNMAPPED. [2024/09/25 07:32:41.921563,? 0] ../../source3/winbindd/winbindd_dual.c:1964(winbindd_sig_term_handler) ? Got sig[15] terminate (is_parent=1) [2024/09/25 07:32:42.042654,? 0] ../../source3/winbindd/winbindd.c:1441(main) ? winbindd ve...

...invalid sid S-1-5-21-3018909051-3044254431-1064828747-1113 - S-1-5-21-3018909051-3044254431-1064828747-1291 The SIDs are valid, and point to a logged on user and their workstation. The winbindd.log file has thousands of entries like these: [2023/10/26 09:28:58.028357, 1] ../../source3/winbindd/wb_lookupsids.c:667(wb_lookupsids_recv) Failed with NT_STATUS_INVALID_SID. [2023/10/26 09:28:58.028372, 1] ../../source3/winbindd/wb_sids2xids.c:765(wb_sids2xids_recv) Failed with NT_STATUS_INVALID_SID. [2023/10/26 09:28:58.028385, 1] ../../source3/winbindd/winbindd_sids_to_xids.c:113(winbindd_sids_to_xid...

...nd their > workstation. Could it be that the workstation is starting the printing and then the user takes over (bit lost here, I do not print anything). > > The winbindd.log file has thousands of entries like these: > > [2023/10/26 09:28:58.028357, 1] > ../../source3/winbindd/wb_lookupsids.c:667(wb_lookupsids_recv) Failed > with NT_STATUS_INVALID_SID. [2023/10/26 09:28:58.028372, 1] > ../../source3/winbindd/wb_sids2xids.c:765(wb_sids2xids_recv) Failed > with NT_STATUS_INVALID_SID. [2023/10/26 09:28:58.028385, 1] > ../../source3/winbindd/winbindd_sids_to_xids.c:113(winb...

On Mon, 23 Sep 2024 16:08:54 +0200 Jochen Eggemann via samba <samba at lists.samba.org> wrote: > Hi, > > my file server winbind.log is full of "Could not convert sid S-0-0: > NT_STATUS_NONE_MAPPED" > > Searching for that string does not produce any helpfull hints on how > to resolv the problem. > > We are using 4.19.3-SerNet-5ubuntu22.04 > >

...ver: Init local_server_* in make_internal_rpc_pipe_socketpair. * BUG 13382: smbclient: Fix broken notify. o Stefan Metzmacher <metze at samba.org> * BUG 13273: libads: Fix the build --without-ads. * BUG 13279: winbindd: Don't split the rid for SID_NAME_DOMAIN sids in wb_lookupsids. * BUG 13280: winbindd: initialize type = SID_NAME_UNKNOWN in wb_lookupsids_single_done(). * BUG 13289: s4:rpc_server: Fix call_id truncation in dcesrv_find_fragmented_call(). * BUG 13290: A disconnecting winbind client can cause a problem in the winbind parent child commu...

...ver: Init local_server_* in make_internal_rpc_pipe_socketpair. * BUG 13382: smbclient: Fix broken notify. o Stefan Metzmacher <metze at samba.org> * BUG 13273: libads: Fix the build --without-ads. * BUG 13279: winbindd: Don't split the rid for SID_NAME_DOMAIN sids in wb_lookupsids. * BUG 13280: winbindd: initialize type = SID_NAME_UNKNOWN in wb_lookupsids_single_done(). * BUG 13289: s4:rpc_server: Fix call_id truncation in dcesrv_find_fragmented_call(). * BUG 13290: A disconnecting winbind client can cause a problem in the winbind parent child commu...