Thanks for getting back to us. I suspect at some point you thought that the right service to start was samba-ad-dc, and you configured it like that, and forgot it. I also find this confusing and hope someday we can have the "switch" between services be automatic, depending on whether you want an AD server or not.
Regarding your smb1 issues, it's not that samba won't negotiate using smb2 or 3. It will. The problem is the network browsing, which relies on smb1. Without smb1, you won't see the other windows/smb machines in the network. But if you try to access them directly via their ips or hostnames, the connection will work and smb2 or smb3 will be spoken just fine. See https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1767454 for some details. I'll leave this bug open as "incomplete". If it happens again, or if you gather more details, then feel free to post them here. Otherwise, the bug will auto-close in about 60 days. Thanks! -- 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
