| 2016-06-14 12:59:33 |
Pierre Pouchin |
description |
I have set up a samba domain using an LDAP domain 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... |
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... |
|
| 2016-06-14 13:00:22 |
Pierre Pouchin |
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 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... |
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... |
|
