Displaying 3 results from an estimated 3 matches for "dcesrv_handle_lookup".
2023 Oct 27
1
Print Server not staying working
...winbind at the same time, they come back for a bit, and everyone can print as per normal.
I have seen the bug report to delete printer_list.tdb, and done that yesterday. In the log.rpcd_spoolss file, I see entries such as this below:
[2023/10/26 09:27:21, 0] ../../librpc/rpc/dcesrv_handles.c:130(dcesrv_handle_lookup)
dcesrv_handle_lookup: Attempt to use invalid sid S-1-5-21-3018909051-3044254431-1064828747-1113 - S-1-5-21-3018909051-3044254431-1064828747-1291
[2023/10/26 09:27:21, 0] ../../librpc/rpc/dcesrv_handles.c:130(dcesrv_handle_lookup)
dcesrv_handle_lookup: Attempt to use invalid sid S-1-5-21-30189...
2023 Nov 15
1
Fw: Print Server not staying working
...winbind at the same time, they come back for a bit, and everyone can print as per normal.
I have seen the bug report to delete printer_list.tdb, and done that yesterday. In the log.rpcd_spoolss file, I see entries such as this below:
[2023/10/26 09:27:21, 0] ../../librpc/rpc/dcesrv_handles.c:130(dcesrv_handle_lookup)
dcesrv_handle_lookup: Attempt to use invalid sid S-1-5-21-3018909051-3044254431-1064828747-1113 - S-1-5-21-3018909051-3044254431-1064828747-1291
[2023/10/26 09:27:21, 0] ../../librpc/rpc/dcesrv_handles.c:130(dcesrv_handle_lookup)
dcesrv_handle_lookup: Attempt to use invalid sid S-1-5-21-30189...
2023 Nov 16
1
Fw: Print Server not staying working
...for a bit, and everyone can print as per
> normal.
>
> I have seen the bug report to delete printer_list.tdb, and done that
> yesterday. In the log.rpcd_spoolss file, I see entries such as this
> below:
>
> [2023/10/26 09:27:21, 0]
> ../../librpc/rpc/dcesrv_handles.c:130(dcesrv_handle_lookup)
> dcesrv_handle_lookup: Attempt to use invalid sid
> S-1-5-21-3018909051-3044254431-1064828747-1113 -
> S-1-5-21-3018909051-3044254431-1064828747-1291
Samba expected the SIDs to match, but they don't, so who or what are the
two SIDs ?
what do these two commands produce:
wbinfo -s...