enterprise-support team mailing list archive

[Pierre Pouchin <pierre.pouchin@xxxxxxx>]

Public bug reported:

I have set up a samba domain using an LDAP backend a few years ago.
The primary domain controller is under Debian Jessie.

Whenever I try to update my domain client server (under Ubuntu Trusty),
I get NT_STATUS_NO_LOGON_SERVERS while trying to access a share (on the
Trusty server) from a computer.

Reverting back to 4.1.6 fixes the problem, but it is not a viable
solution.

There are other servers that are part of this domain (with Debian Jessie
and Ubuntu Precise), but these work fine, although I needed to tweak the
signing parameters for Precise.

I tried adjusting several parameters on Trusty (require strong auth,
client ipc signing) but to no avail...

** Affects: samba (Ubuntu)
     Importance: Undecided
         Status: New

** Description changed:

- I have set up a samba domain using an LDAP domain a few years ago. 
- The primary domain controller is under Debian Jessie. 
+ I have set up a samba domain using an LDAP backend a few years ago.
+ The primary domain controller is under Debian Jessie.
  
  Whenever I try to update my domain client server (under Ubuntu Trusty),
  I get NT_STATUS_NO_LOGON_SERVERS while trying to access a share from a
  computer.
  
  Reverting back to 4.1.6 fixes the problem, but it is not a viable
  solution.
  
  There are other servers that are part of this domain (with Debian Jessie
  and Ubuntu Precise), but these work fine, although I needed to tweak the
  signing parameters for Precise.
  
  I tried adjusting several parameters on Trusty (require strong auth,
  client ipc signing) but to no avail...

** Description changed:

  I have set up a samba domain using an LDAP backend a few years ago.
  The primary domain controller is under Debian Jessie.
  
  Whenever I try to update my domain client server (under Ubuntu Trusty),
- I get NT_STATUS_NO_LOGON_SERVERS while trying to access a share from a
- computer.
+ I get NT_STATUS_NO_LOGON_SERVERS while trying to access a share (on the
+ Trusty server) from a computer.
  
  Reverting back to 4.1.6 fixes the problem, but it is not a viable
  solution.
  
  There are other servers that are part of this domain (with Debian Jessie
  and Ubuntu Precise), but these work fine, although I needed to tweak the
  signing parameters for Precise.
  
  I tried adjusting several parameters on Trusty (require strong auth,
  client ipc signing) but to no avail...

-- 
You received this bug notification because you are a member of Ubuntu
Server/Client Support Team, which is subscribed to samba in Ubuntu.
Matching subscriptions: Ubuntu Server/Client Support Team
https://bugs.launchpad.net/bugs/1592397

Title:
  Samba domain broken by 4.3.9 update on Trusty

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1592397/+subscriptions