Re: [Samba] write list = is ignored
On 24/06/2009, at 18.30, Dale Schroeder wrote: Jon, If I understand your question correctly, and assuming that you're using winbind, have you tried write list = @DOMAIN\* (substitute your winbind separator, if different) I thought i tried that already. Apparently it did work today. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] write list = is ignored
Hi My write list = is ignored. I have tried various combinations of username, groups, different users, groups. The directory has had the same permissions, or world writeable. su - to a user does work, and i can create and change files. But the samba share does just not work. I know i am editing in the right smb.conf file because i made a new share. I have security = DOMAIN and i connect to a windows AD. i run samba 3.2.5-4lenny2 from debian. This is my share configuration [released] comment = Released software path = /data/released write list = @** create mask = 0775 force create mode = 0775 directory mask = 0775 force directory mode = 0775 JonB -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] Re: mod_auth_ntlm_winbind
Scott Barnett wrote: I'm having some difficulties with mod_auth_ntlm_winbind. Winbind and samba are configured and working well, I can create shares and set permissions to AD groups. Wbinfo -u and wbinfo -g work fine. Which samba version are you using? JonB -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Re: Samba + Winbind + SuSE Linux AD auth not working
Dave wrote: ok here's the situation; i've done this on 7 servers same either SLES 9 or 10, and all those work. i have a problem server though which is SLES v9 (same versions of all daemons/services that would be used) and this one just wont allow AD auth to work Which samba version are you using? i recently upgraded from 3.0.22 to 3.0.24, and it failed badly. I had to revert to 3.0.22 JonB -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] upgrade 3.0.22 3.0.24 winbind problem - no reply received to cldap netlogon
Hi After trying a upgrade from 3.0.22 to 3.0.24 winbind stopped working. This was quite serious for us since we use windows domain accounts to login into all kind of services on linux. I saw error messages like: no reply received to cldap netlogon in the /var/log/samba/log.winbindd and log.wb-$DOMAIN This is kind of strange, because i dont remember having told it to use LDAP. But shortly after giving up trying to find a solution i changed back to 3.0.22, and then winbindd started working again. I did not change any parameters in the smb.conf file, and reading the man pages and release notes has not given me a clear indication that i have to change anything. I chose 3.0.24 over 3.0.23 because .24 appears to be .23 with 3 security fixes. there is a firewall between the linux server and the domain controller, but since it does work with 3.0.22, i can not see why it should also not work with 3.0.24 Anyway, since winbind is somewhat unstable in 3.0.22, i wanted to upgrade to make it more stable, so i would like some help getting 3.0.24 to work. JonB -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] winbind issues with AD domain trust
Den 11. okt 2005 kl. 20:06 skrev Giles Mullen: Any luck resolving this issue? I'm running into the same problem. get the posted patch, or checkout the latest from svn, this worked for me. I no longer experience a dead winbindd. JonB -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba 3.0.20a and Winbind crashing (bug?)
Den 10. okt 2005 kl. 23:40 skrev Jeremy Allison: On Sun, Oct 09, 2005 at 06:25:56PM +0100, [EMAIL PROTECTED] wrote: Hi all. having major issues on all my servers at the moment. All running RHES 3, all with samba 3.0.20a and all have the winbind crashing problem :/ the main 2 are the filestore and email servers, also get the most usage. in fact from my systems point of view, its definatly a most usage = most frequent winbind crashing issue. Any help from others or the dev team gratefully received. NB i have also set a cron to restart smb at 22:00 every night. Please try this patch : Succes, well sort off This patch works for me as well. I can no longer crash winbindd by running getent passwd However my auth.log file still contains write to socket failed! But just a few seconds later it appears to be working, but it does not work. Oct 11 11:23:20 frodo pam_winbind[6100]: write to socket failed! Oct 11 11:23:20 frodo pam_winbind[6100]: internal module error (retval = 3, user = `dkrbr1') Oct 11 11:23:27 frodo apache2[6100]: (pam_unix) authentication failure; logname= uid=33 euid=33 tty= ruser= rhost=192.168.119.160 Oct 11 11:23:27 frodo pam_winbind[6100]: write to socket failed! Oct 11 11:23:27 frodo pam_winbind[6100]: internal module error (retval = 3, user = `dkrbr1') (someone was connecting here using ssh and a unix account) Oct 11 11:23:34 frodo apache2[6100]: (pam_unix) authentication failure; logname= uid=33 euid=33 tty= ruser= rhost=192.168.119.160 Oct 11 11:23:34 frodo pam_winbind[6100]: write to socket failed! Oct 11 11:23:34 frodo pam_winbind[6100]: internal module error (retval = 3, user = `dkrbr1') Oct 11 11:23:38 frodo sshd[16016]: Accepted publickey for sergtepkom from 82.179.167.71 port 2932 ssh2 Oct 11 11:23:40 frodo apache2[20839]: (pam_unix) authentication failure; logname= uid=33 euid=33 tty= ruser= rhost=192.168.119.160 Oct 11 11:23:40 frodo pam_winbind[20839]: user 'dkrbr1' granted access Oct 11 11:23:40 frodo apache2[20839]: (pam_unix) could not identify user (from getpwnam(dkrbr1)) Oct 11 11:23:40 frodo apache2[6098]: (pam_unix) authentication failure; logname= uid=33 euid=33 tty= ruser= rhost=192.168.119.160 Oct 11 11:23:40 frodo pam_winbind[6098]: user 'dkrbr1' granted access Oct 11 11:23:40 frodo apache2[6098]: (pam_unix) could not identify user (from getpwnam(dkrbr1)) Oct 11 11:23:52 frodo apache2[20061]: (pam_unix) authentication failure; logname= uid=33 euid=33 tty= ruser= rhost=192.168.119.160 Oct 11 11:23:52 frodo pam_winbind[20061]: user 'dkrbr1' granted access Oct 11 11:23:52 frodo apache2[20061]: (pam_unix) could not identify user (from getpwnam(dkrbr1)) Oct 11 11:23:52 frodo apache2[31528]: (pam_unix) authentication failure; logname= uid=33 euid=33 tty= ruser= rhost=192.168.119.160 Oct 11 11:23:52 frodo pam_winbind[31528]: user 'dkrbr1' granted access Oct 11 11:23:52 frodo apache2[31528]: (pam_unix) could not identify user (from getpwnam(dkrbr1)) Oct 11 11:23:52 frodo apache2[22772]: (pam_unix) authentication failure; logname= uid=33 euid=33 tty= ruser= rhost=192.168.119.160 Oct 11 11:23:52 frodo pam_winbind[22772]: user 'dkrbr1' granted access Oct 11 11:23:52 frodo apache2[22772]: (pam_unix) could not identify user (from getpwnam(dkrbr1)) Oct 11 11:23:54 frodo apache2[6096]: (pam_unix) authentication failure; logname= uid=33 euid=33 tty And the user complains that subversion update through apache2 through pam authentication through winbind to win 2003 server does not work. TortoiseSVN does no longer ask for username/password. A restart of winbindd did not help, i had to restart apache2 as well before it would work. After this restart i tried repeating the error by running getent passwdbut i can nolonger get write to socket failed!messages in auth.log. JonB -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba 3.0.20a and Winbind crashing (bug?)
This sounds like the same problem i had with winbind in both 3.0.14 abd 3.0.20. Mine freezes, and the daemon appears to be still running using ps and top, but it doesnt respond to queries. It seems like i can trigger this event by running getent passwd. It shows the accounts, but then the daemon dies. I run it on debian sarge, and i have another server with different hardware that also runs debian sarge. The other server does not have the problem (havent tested with getent passwd) but it does not see as many auth. attempts as the freezing server does. I use winbindd for pam_winbind. And some times it goes days without crashing other times it freezes several times an hour. I get this following entries in my auth.log: write to socket failed! internal module error (retval = 3 I circumvented it by running wbinfo -p every minute and restarting winbbind if wbinfo failed. JonB -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] winbindd freezes with write to socket failed! and no more windows authentication is possible
Hi I have a problem with winbindd that freezes such that no windows authentication is possible. The auth.log file says write to socket failed! internal module error (retval = 3 i have tried with both debian sarge 3.0.14a packages, and i compiled my own from the source version 3.0.20 I have tried -Y on winbindd, i have looked over the smb.conf file, i tried googling for "write to socket failed" but nothing really usefull came up :( only that others have had the same problem previously in time. JonB -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] winbindd freezes with write to socket failed! and no more windows authentication is possible
Hi I have a problem with winbindd that freezes such that no windows authentication is possible. The auth.log file says write to socket failed! internal module error (retval = 3 i have tried with both debian sarge 3.0.14a packages, and i compiled my own from the source version 3.0.20 I have tried -Y on winbindd, i have looked over the smb.conf file, i tried googling for "write to socket failed" but nothing really usefull came up :( only that others have had the same problem previously in time. JonB -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
