Displaying 3 results from an estimated 3 matches for "wb_lookupsids_recv".
2023 Oct 27
1
Print Server not staying working
...1-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_xids_recv)
Could not conver...
2023 Nov 15
1
Fw: Print Server not staying working
...1-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_xids_recv)
Could not conver...
2023 Nov 16
1
Fw: Print Server not staying working
...ation.
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(winbindd_sids_to_xids_recv)
&g...