[Samba] Samba-AD-DC package question . . .

Rowland Penny rowlandpenny241155 at gmail.com
Sat Oct 10 13:05:11 UTC 2015


On 10/10/15 13:44, Steve Ankeny wrote:
> I have an existing Samba-AD-DC built from Inverse packages, 
> v.4.1.18+dfsg-3~inverse1
>
> I have OpenChangeServer installed on that machine, v.2.4-zentyal6
>
> When I start OpenChange, it "shuts down" my Samba-AD-DC so that no one 
> can login.
>
> To troubleshoot my problem, I've built a "new" Samba-AD-DC from the 
> same Inverse packages, but I see a slight difference in the installed 
> packages, and my question is whether they might be causing my problem.
>
> *Specifically, could the presence of 'winbind' be causing my problem?*
>
> on the original server (with the OpenChange problem) --
>
> adam at sogo:~$ sudo dpkg --get-selections | egrep 'samba|smb|nmb|winbind'
> libnss-winbind:amd64                         install
> libpam-winbind:amd64                       install
> libsmbclient:amd64                            install
> python-samba                                    install
> samba                                                install
> samba-common                                 install
> samba-common-bin                           install
> samba-dev                                         install
> samba-dsdb-modules                         install
> samba-libs:amd64                              install
> samba-vfs-modules                            install
> smbclient                                            install
> winbind                                               install
> adam at sogo:~$
>
> on the "new" server (without OpenChange at the moment) --
>
> adam at eagle:~$ sudo dpkg --get-selections | egrep 'samba|smb|nmb|winbind'
> python-samba                                    install
> samba                                                install
> samba-common                                 install
> samba-common-bin                           install
> samba-dev                                         install
> samba-dsdb-modules                         install
> samba-libs:amd64                              install
> samba-vfs-modules                            install
> adam at eagle:~$
>
> The difference is in the 'winbind' and 'smbclient' packages.
>
> I realize that Samba-AD-DC runs its own version of 'winbind' and I'm 
> not currently using it otherwise.
>
> on the original server --
>
> adam at sogo:~$ ./samba
> nmbd start/running
> winbind stop/waiting
> smbd stop/waiting
> reload-smbd stop/waiting
> samba-ad-dc start/running, process 927
> adam at sogo:~$
>
> on the "new" server --
>
> adam at eagle:~$ ./samba
> nmbd start/running
> smbd stop/waiting
> reload-smbd stop/waiting
> samba-ad-dc start/running, process 889
> adam at eagle:~$
>
>

Having a package installed is a lot different from the binaries it 
contains being run, what does 'ps ax | grep [w]inbind' return?

What is your 'server services' line in smb.conf and what are the 
openchange lines in smb.conf

Rowland





More information about the samba mailing list