/usr/local/samba/sbin/winbindd broken?

steve steve at steve-ss.com
Thu Aug 30 03:18:18 MDT 2012


On 30/08/12 10:55, Rowland Penny wrote:
> On 30/08/12 08:54, Kai Blin wrote:
>> On 2012-08-29 16:51, Rowland Penny wrote:
>>
>> Hi Rowland,
>>
>>> As some of you may know, I have been testing nmbd,smbd&  winbindd from
>>> Samba 4 as a client.
>>> Well, after a good bit of testing and scratching of head, I have come to
>>> the conclusion that something in the /usr/local/samba/sbin/winbindd
>>> daemon is broken.
>> Ok, just to be sure, on the S4 client, you're running smbd, nmbd and
>> winbindd, but not the "samba" binary?
>>
>> Anything interesting in the winbind logs?
>>
>> Cheers,
>> Ka
>>
>
> I am just running the three daemons:
>
> ps ax | grep samba
>   2914 ?        Ss     0:00 /usr/local/samba/sbin/nmbd -D
>   2916 ?        Ss     0:00 /usr/local/samba/sbin/smbd -D
>   2917 ?        S      0:00 /usr/local/samba/sbin/smbd -D
>   2919 ?        Ss     0:00 /usr/local/samba/sbin/winbindd -D
>   2921 ?        S      0:00 /usr/local/samba/sbin/winbindd -D
>
> There is nothing in the logs apart from showing the daemons starting &
> stopping. I have even looked in the logs on the server, nothing there
> either.
>
> Stop me if I am wrong, but as far as I am aware, winbind is supposed to
> pull the posix info from the server database. If this is so, then
> /usr/local/samba/sbin/winbindd is broken, as I only get the non-posix
> info i.e. it does not work like S3 winbind.
>
> Rowland
>
>
>
Hi
Just to be utterly and 100%'ly correct. As I see it: Rowland is using a 
Samba4 installation as a client. He has a Samba4 DC running on another 
box. He is simply trying to use winbindd on his client to extract posix 
information from his Samba4 DC. As indeed he can with a Samba3 client.

So, to test Samba4 as a client, he should be able to take his smb.conf 
from a Samba3 client and drop it into /usr/local/samba/etc/samba/etc, 
join the domain and have it behave _exactly_ the same.

If Samba4 is a replacement for Samba3 as advertised, then his setup 
proves that something is wrong with the winbindd implementation in 
Samba4 as it is not pulling rfc2307 posix attributes from AD.

Always with the proviso that the samba is _not_ running on the Samba4 
client but _is_ running on his DC.

Summary:
Samba4 DC: samba
Samba4 Client: smbd, nmbd, winbindd

Have I got that right?
Cheers,
Steve






More information about the samba-technical mailing list