[Bug 1776576] Re: Ubuntu 18.04 uograde: samba fails to run

2018-08-18 Thread Launchpad Bug Tracker
[Expired for samba (Ubuntu) because there has been no activity for 60
days.]

** Changed in: samba (Ubuntu)
   Status: Incomplete => Expired

-- 
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

[Bug 1776576] Re: Ubuntu 18.04 uograde: samba fails to run

2018-06-19 Thread Andreas Hasenack
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
Server, which is subscribed to samba in 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-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1776576] Re: Ubuntu 18.04 uograde: samba fails to run

2018-06-19 Thread Andreas Hasenack
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

[Bug 1776576] Re: Ubuntu 18.04 uograde: samba fails to run

2018-06-15 Thread C. Jeffery Small
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

[Bug 1776576] Re: Ubuntu 18.04 uograde: samba fails to run

2018-06-13 Thread Andreas Hasenack
The samba-ad-dc service is meant for samba when it is configured as an
Active Directory Controller. Since your role is "standalone server", the
services you should try to start/stop/restart/etc are called smbd and
nmbd, as they were before.

You should check why, if still happening, these are failing:

sudo systemctl restart smbd nmbd

If they are still failing, please attach their output and the logs from
/var/log/samba/log*

Also please run the testparm utility to verify your smb.conf for syntax.
I can't do it with the file you provided because of the bits you
sanitized.

** Changed in: samba (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to samba in 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-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1776576] Re: Ubuntu 18.04 uograde: samba fails to run

2018-06-13 Thread Andreas Hasenack
The samba-ad-dc service is meant for samba when it is configured as an
Active Directory Controller. Since your role is "standalone server", the
services you should try to start/stop/restart/etc are called smbd and
nmbd, as they were before.

You should check why, if still happening, these are failing:

sudo systemctl restart smbd nmbd

If they are still failing, please attach their output and the logs from
/var/log/samba/log*

Also please run the testparm utility to verify your smb.conf for syntax.
I can't do it with the file you provided because of the bits you
sanitized.

** Changed in: samba (Ubuntu)
   Status: New => Incomplete

-- 
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

[Bug 1776576] Re: Ubuntu 18.04 uograde: samba fails to run

2018-06-12 Thread C. Jeffery Small
A slightly modified smb.conf for conceal some personal info.

** Attachment added: "smb.conf"
   
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1776576/+attachment/5151907/+files/smb.conf

-- 
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