[Pkg-samba-maint] Bug#918432: Bug#918432: samba: net ads join to armel arch Samba DC failed

[Mathieu Parent]

Le  lun. 28 janv. 2019 à 22:16, Tomasz Jeliński <tjelinski at gmail.com> a écrit :
[...]
> > Please keep the bug CC-ed.

Yes, please always keep 918432 at bugs.debian.org in CC.

> I'm tracking Samba bugzilla thread but I can't create account to CC
> answer there. I can't register, there is no active option to create
> new account.

As said at: https://bugzilla.samba.org/createaccount-save.html, you
need to send an email to request an account. Please do, I'm adding too
much lag...

> I'am sending to You in attachments tarball with config
> files requested by Louis and additional debugging information.

Thanks

> Workstation is samba amd64 arch (stable branch). Workstation samba
> client (stable branch) connects without problem to samba AD-DC server
> amd64 arch  (tested on stable and testing branches). The problem only
> occurs when I'am trying to join to samba ad-dc server installed on
> QNAP TS device (armel arch)  from my Workstation. I checked stable and
> testing branch samba on QNAP TS device (armel arch) and notice the
> same error message when I was trying to connect from samba stable
> workstation.
>
> Today I attempt to connect from samba testing amd64 arch client
> (hostname DC2)  to AD-DC server. Error is the same but I have got
> additional info:
>
> "Starting GENSEC submechanism gse_krb5
> gse_get_client_auth_token: Server principal not found
> gensec_update_done: gse_krb5[0x560c3a869f90]: NT_STATUS_INVALID_PARAMETER
> gensec_spnego_create_negTokenInit_step: gse_krb5: creating
> NEG_TOKEN_INIT for ldap/dc1.ad.rowerowanorka.pl failed (next[(null)]):
> NT_STATUS_INVALID_PARAMETER
> gensec_update_done: spnego[0x560c3a864610]: NT_STATUS_INVALID_PARAMETER"
>
> When I analyzing Wireshark dump I found something strange. Kerberos
> "NT Status Error" is a part of string  "AD.ROWEROWANORKA.PL" what is
> Kerberos REALM name.
>
> I send to You all gathered samba debuging files in attachment. There
> are net ads join logs  from stable and testing samba client (amd64),
> wireshark dumps and screenshot with this strange packet in Wireshark
> dump.

This is too low level for me. I hope a samba team member will take a
look at it...

Regards

-- 
Mathieu Parent