Samba domain broken by 4.3.9 update on Trusty

Bug #1592397 reported by Pierre Pouchin
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
samba (Ubuntu)
New
Undecided
Unassigned

Bug Description

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

description: updated
description: updated
Revision history for this message
Pierre Pouchin (pierre-pouchin) wrote :

So, I guess I should stick to 4.1.6 if I want the machine to stay in a NT4 domain?

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.