[Samba] Option configure

[Sonic]

I do get these errors (even when starting with Type=forking):

Jul 12 12:01:36 kwad winbindd[420]: [2016/07/12 12:01:36.491192,  0]
../source3/winbindd/winbindd_cm.c:1849(wb_open_internal_pipe)
Jul 12 12:01:36 kwad winbindd[420]: open_internal_pipe: Could not
connect to dssetup pipe: NT_STATUS_UNSUCCESSFUL
Jul 12 12:01:36 kwad winbindd[420]: [2016/07/12 12:01:36.491833,  0]
../source3/winbindd/winbindd_cm.c:1849(wb_open_internal_pipe)
Jul 12 12:01:36 kwad winbindd[420]: open_internal_pipe: Could not
connect to lsarpc pipe: NT_STATUS_UNSUCCESSFUL
Jul 12 12:01:36 kwad winbindd[420]: [2016/07/12 12:01:36.492488,  0]
../source3/winbindd/winbindd_cm.c:1849(wb_open_internal_pipe)
Jul 12 12:01:36 kwad winbindd[420]: open_internal_pipe: Could not
connect to dssetup pipe: NT_STATUS_UNSUCCESSFUL
Jul 12 12:01:36 kwad winbindd[420]: [2016/07/12 12:01:36.493365,  0]
../source3/winbindd/winbindd_cm.c:1849(wb_open_internal_pipe)
Jul 12 12:01:36 kwad winbindd[420]: open_internal_pipe: Could not
connect to lsarpc pipe: NT_STATUS_UNSUCCESSFUL
Jul 12 12:01:36 kwad winbindd[420]: [2016/07/12 12:01:36.493853,  0]
../source3/winbindd/winbindd_cm.c:1849(wb_open_internal_pipe)
Jul 12 12:01:36 kwad winbindd[420]: open_internal_pipe: Could not
connect to lsarpc pipe: NT_STATUS_UNSUCCESSFUL

although winbindd is running. I can eliminate the errors by removing
winbindd from the server services parameter but I think it is supposed
to be running for an AD installation.

Chris