search for: sid_alias

...y|Distribution root at dc1:~# /usr/local/samba/bin/samba-tool group add SambaTool-DL-Sec --group-scope=Domain --group-type=Security Added group SambaTool-DL-Sec getent group shows nothing root at dc1:~# /usr/local/samba/bin/wbinfo -n SambaTool-DL-Sec S-1-5-21-3390367671-3527586854-3401016232-1128 SID_ALIAS (4) root at dc1:~# /usr/local/samba/bin/ldbedit -e vi -H /usr/local/samba/private/idmap.ldb objectsid=S-1-5-21-3390367671-3527586854-3401016232-1128 no matching records - cannot edit Shows in ADUC. root at dc1:~# /usr/local/samba/bin/samba-tool group add SambaTool-GG-Sec --group-scope=Global --...

Hai, Does anyone know more if this is adressed or point me to the bug report? There should be one, but i cant find it. Im finding the following again, tested with samba 4.4.5, now samba 4.5.3. These reports go back to the year 2013. I searched in my mail samba folder for S-1-5-18 The problem. I create a "computer" Scheduled task. Now this task MUST run as : SYSTEM (S-1-5-18)

Hello, i have a fresh installed/compiled from source samba 4.11.2 on ubuntu 18.04. But samba wont start. Syslog output: Nov? 6 12:15:19 dms systemd[1]: Starting Samba4 smbd... Nov? 6 12:15:19 dms systemd[1]: Started Samba4 smbd. Nov? 6 12:15:19 dms smbd[1557]: [2019/11/06 12:15:19.594448,? 0] ../../source3/auth/auth_util.c:1385(make_new_session_info_guest) Nov? 6 12:15:19 dms smbd[1557]:??

Samba version : 3.6.3 Filesystem : BTRFS Clients : XP, Win7 Log Level : 5 When we start our samba server everything works fine. After a few days, some of our users are not allowed to connect to shares anymore. When we restart the clients they can connect for a short time and then say have the same problem again. When we restart the server everything works fine for a few days again.