Sorry for the delay in responding. Everything is finally resolved.
Here is what I found.
The Ubuntu OS was upgraded for a week and the system was rebooted
multiple times before I noticed the samba problem. At that point, in
addition to trying to start the samba-ad-dc service, I also had tried
manually to start smbd and nmbd multiple times and received similar
error messages with a failure of either starting. Since the services
were not running there was no output in the /var/log/samba log files.
Running testparm was showing no problems other than the unimportant
warnings:
rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384)
WARNING: The "syslog" option is deprecated
neither of which should cause any problem. I do not believe that I
changed anything significant, yet upon another system reboot both smbd
and nmbd services started automatically and they continue to run
properly upon subsequent reboots. I'm afraid I cannot explain why this
is the case. Things like this are usually user error, but I cannot
identify what may have been the problem.
Now, the Ubuntu system could see the samba and external Windows shares.
However, the Windows 10 machines could not see the samba server! This
turned out to be due to a recent push of Windows 10 version 1803 which
changed smb behavior by disabling the SMBv1 protocol, supporting only v2
and v3 by default. Now, why samba could not negotiate using these
protocols is unclear, but the workaround was to re-enable SMBv1 on the
Windows 10 machines, at which point they could negotiate with samba once
again. A second difficulty was that it was impossible to connect to the
samba server using the normal username and password that had worked in
the past. The only solution I was able to discover was that the
connection had to be established with hostname\username rather than
username alone. Then everything was back to normal.
Someone may want to take a look at Windows 10 v1803 to see how it is
interacting with the standard samba configuration. In the future
Microsoft may eliminate support for SMBv1 altogether.
Sorry I don't have anything more definitive as to why smbd/nmbd were not
running, but I really appreciate the feedback and support. Let me know
if I can provide any additional useful information.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1776576
Title:
Ubuntu 18.04 uograde: samba fails to run
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1776576/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
