samba - Apr 2016 - Upgrading Samba 3 to Samba 4 - Domain Controller unreachable

Think I should actively STOP that service?

On Sat, Apr 2, 2016 at 11:18 AM, Sonic <sonicsmith at gmail.com> wrote:
> On Sat, Apr 2, 2016 at 2:07 PM, Luke Barone <lukebarone at gmail.com>
wrote:
> > [ ok ] Restarting samba-ad-dc (via systemctl): samba-ad-dc.service.
> >
> > I may try rebooting as well, after trying @penny's fix. But
that's what
> > I've always been doing. When I use systemctl start nmbd smbd I get
no
> > output.
>
> OK, that's the Debian packaging, seems fine except I don't think
you
> want the samba-ad-dc.service to start.
>

On Sat, Apr 2, 2016 at 2:20 PM, Luke Barone <lukebarone at gmail.com>
wrote:
> Think I should actively STOP that service?
I would say yes, since you want to run a NT PDC, the samba-ad-dc
service if for an Active Directory controller.

systemctl stop samba-ad-dc.service
systemctl disable samba-ad-dc.service

Stop using the /etc/init.d/... commands. Just use "systemctl start
nmbd smbd" and "systemctl stop nmbd smbd" to control them. If you
have
them enabled "systemctl enable nmbd smbd" they should start
automatically on reboot, and the disabled samba-ad-dc should not.

On Sat, Apr 2, 2016 at 11:27 AM, Sonic <sonicsmith at gmail.com> wrote:
> systemctl stop samba-ad-dc.service
> systemctl disable samba-ad-dc.service
>

OK, I did that. I got it working for Windows 7, I just need it working now
for Windows 10.