[Samba] No Samba NT DOMAIN Name found exitting now...

[Robert Wooden]

working in what Louis has suggested.


On Tue, Sep 29, 2020 at 9:32 AM Robert Wooden <wdn2420systm at gmail.com>
wrote:

> Rowland,
>
> If I stop one of the DC's the other will run fine.
> The non-running DC when "samba -i" complains that it cannot communicate
> with the other DC.
> Running "systemctl start samba=ad=dc.service" has the same cannot connect
> to other DC.
>
> If I stop the running DC with "systemctl stop samba-ad-dc.service" and
> start the second DC with "systemctl start samba-ad-dc.service" the
> "starting" machine does not return to a command prompt (as if it has
> completed the start.) I can "ctrl+c" (to get cli) and run systemctl status
> samba-ad-dc.service" and the service will be running.
>
> At the point my W10 domain member can login with some minor complaints.
> Networked drive connections have failed and use rprofile did not load.
>
> On Tue, Sep 29, 2020 at 9:02 AM Rowland penny via samba <
> samba at lists.samba.org> wrote:
>
>> On 29/09/2020 14:46, Robert Wooden via samba wrote:
>> > In addition, both DC's are not "running"
>> >
>> > root at tdc2:~# systemctl status samba-ad-dc.service
>> >> ● samba-ad-dc.service - Samba AD Daemon
>> >>     Loaded: loaded (/lib/systemd/system/samba-ad-dc.service; enabled;
>> >> vendor preset: enabled)
>> >>     Active: failed (Result: timeout) since Tue 2020-09-29 06:25:00
>> CDT; 2h
>> >> 17min ago
>> >>       Docs: man:samba(8)
>> >>             man:samba(7)
>> >>
>> >             man:smb.conf(5)
>> >>    Process: 407 ExecStart=/usr/sbin/samba --foreground
>> --no-process-group
>> >> $SAMBAOPTIONS (code=exited, status=127)
>> >>   Main PID: 407 (code=exited, status=127)
>> >>
>> >> Sep 29 06:23:33 dc2 systemd[1]: samba-ad-dc.service: Got notification
>> >> message from PID 445, but reception only permitted for mai
>> >> Sep 29 06:23:33 dc2 smbd[445]:   daemon_ready: daemon 'smbd' finished
>> >> starting up and ready to serve connections
>> >> Sep 29 06:25:00 dc2 systemd[1]: samba-ad-dc.service: Start operation
>> timed
>> >> out. Terminating.
>> >> Sep 29 06:25:00 dc2 winbindd[591]: [2020/09/29 06:25:00.232182,  0]
>> >> ../../source3/winbindd/winbindd.c:248(winbindd_sig_term_hand
>> >> Sep 29 06:25:00 dc2 winbindd[591]:   Got sig[15] terminate
>> (is_parent=0)
>> >> Sep 29 06:25:00 dc2 winbindd[597]: [2020/09/29 06:25:00.232517,  0]
>> >> ../../source3/winbindd/winbindd.c:248(winbindd_sig_term_hand
>> >> Sep 29 06:25:00 dc2 winbindd[597]:   Got sig[15] terminate
>> (is_parent=0)
>> >> Sep 29 06:25:00 dc2 systemd[1]: samba-ad-dc.service: Main process
>> exited,
>> >> code=exited, status=127/n/a
>> >> Sep 29 06:25:00 dc2 systemd[1]: samba-ad-dc.service: Failed with result
>> >> 'timeout'.
>> >> Sep 29 06:25:00 dc2 systemd[1]: Failed to start Samba AD Daemon.
>> >> lines 1-19/19 (END)
>> >>
>> > Suggestions?
>>
>> Find out why the DC's are not running ?
>>
>> Try opening a terminal on a DC and run this: samba -i
>>
>> This will output everything into the terminal.
>>
>> Rowland
>>
>>
>>
>> --
>> To unsubscribe from this list go to the following URL and read the
>> instructions:  https://lists.samba.org/mailman/options/samba
>>
>