search for: computer3

...nnection(722) smbldap_open_connection: connection opened [2006/01/23 11:36:30, 3] lib/smbldap.c:smbldap_connect_system(905) ldap_connect_system: succesful connection to the LDAP server [2006/01/23 11:36:30, 2] passdb/pdb_ldap.c:init_sam_from_ldap(640) init_sam_from_ldap: Entry found for user: computer3$ [2006/01/23 11:36:30, 3] smbd/sec_ctx.c:pop_sec_ctx(386) pop_sec_ctx (65534, 65534) - sec_ctx_stack_ndx = 0 [2006/01/23 11:36:30, 0] libsmb/credentials.c:creds_server_check(159) creds_server_check: credentials check failed. [2006/01/23 11:36:30, 0] rpc_server/srv_netlog_nt.c:_net_auth_2(424)...

...rading process shouldn''t work) What I came up with is this : ------------------------- #!/bin/sh ipt="/usr/sbin/iptables" $ipt -F $ipt -F -t nat $ipt -t filter -N computer1 >/dev/null 2>&1 $ipt -t filter -N computer2 >/dev/null 2>&1 $ipt -t filter -N computer3 >/dev/null 2>&1 $ipt -t filter -N computer4 >/dev/null 2>&1 $ipt -t filter -N computer5 >/dev/null 2>&1 $ipt -A FORWARD -s 192.168.10.2 -j computer1 $ipt -A FORWARD -s 192.168.10.3 -j computer2 $ipt -A FORWARD -s 192.168.10.4 -j computer3 $ipt -A FORWARD -s 192.168.10...

...dap_open_connection: connection opened > [2006/01/23 11:36:30, 3] lib/smbldap.c:smbldap_connect_system(905) > ldap_connect_system: succesful connection to the LDAP server > [2006/01/23 11:36:30, 2] passdb/pdb_ldap.c:init_sam_from_ldap(640) > init_sam_from_ldap: Entry found for user: computer3$ > [2006/01/23 11:36:30, 3] smbd/sec_ctx.c:pop_sec_ctx(386) > pop_sec_ctx (65534, 65534) - sec_ctx_stack_ndx = 0 > [2006/01/23 11:36:30, 0] libsmb/credentials.c:creds_server_check(159) > creds_server_check: credentials check failed. > [2006/01/23 11:36:30, 0] rpc_server/srv_netlo...

...cache list | grep -i computer The group itself can be resolved just fine, even though the computer accounts can't - and it shows that the computer accounts are definitely members of the group in question: [root at fileserver ~]# wbinfo --group-info sw-dist sw-dist:x:12345:computer$,computer2$,computer3$,computer4$ All of this inevitably leads to the key directories in question not being accessible by the computers who need them. When the computer account connects to the file server, its group memberships don't really seem to work. I suspect that sssd had different behaviour to winbind in thi...

...pid machine Connected at ------------------------------------------------------- xxxxx 16894 computer1 Fri May 21 11:46:57 2004 yyyyy 16894 computer1 Fri May 21 11:46:57 2004 zzzzz 16940 aaa.bbb.ccc.ddd Fri May 21 11:45:35 2004 zzzzz 17071 computer3 Fri May 21 11:48:38 2004 xxxxx 16908 aaa.bbb.ccc.eee Fri May 21 11:44:34 2004 Locked files: Pid DenyMode Access R/W Oplock Name -------------------------------------------------------------- 16908 DENY_NONE 0x2019f RDWR EXCLUSIVE+BATCH /somepat...

...> The group itself can be resolved just fine, even though the computer > accounts can't - and it shows that the computer accounts are > definitely members of the group in question: > > [root at fileserver ~]# wbinfo --group-info sw-dist > sw-dist:x:12345:computer$,computer2$,computer3$,computer4$ > > All of this inevitably leads to the key directories in question not > being accessible by the computers who need them. When the computer > account connects to the file server, its group memberships don't > really seem to work. I suspect that sssd had different be...

...an be resolved just fine, even though the computer > > accounts can't - and it shows that the computer accounts are > > definitely members of the group in question: > > > > [root at fileserver ~]# wbinfo --group-info sw-dist > > sw-dist:x:12345:computer$,computer2$,computer3$,computer4$ > > > > All of this inevitably leads to the key directories in question not > > being accessible by the computers who need them. When the computer > > account connects to the file server, its group memberships don't > > really seem to work. I suspect th...