Displaying 2 results from an estimated 2 matches for "0d54b3be".
Did you mean:
0x0d54b3be
2020 Aug 26
0
accessing foreign AD users to NT domain
...553, effective(0, 0), real(0, 0)] ../lib/dbwrap/dbwrap.c:114(debug_lock_order)
lock order: 1:/var/run/samba/smbXsrv_session_global.tdb 2:<none> 3:<none>
[2020/08/26 09:53:02.420717, 10, pid=2553, effective(0, 0), real(0, 0)] ../lib/dbwrap/dbwrap_tdb.c:59(db_tdb_log_key)
Locking key 0D54B3BE
[2020/08/26 09:53:02.420740, 10, pid=2553, effective(0, 0), real(0, 0)] ../lib/dbwrap/dbwrap_tdb.c:143(db_tdb_fetch_locked_internal)
Allocated locked data 0x0x205e518
[2020/08/26 09:53:02.420807, 10, pid=2553, effective(0, 0), real(0, 0)] ../source3/smbd/smbXsrv_session.c:943(smbXsrv_session_glob...
2020 Aug 25
4
accessing foreign AD users to NT domain
Mandi! Rowland penny via samba
In chel di` si favelave...
> Even though your users may have the same username in AD as in the NT4-style
> domain, they are different users, so a few thoughts. You have 'map to guest
> = bad user', so I take it you must have 'guest ok = yes' set in the shares
> (you haven't shown us the shares), so try changing 'bad user' to