Hi all,
I have a machine joined to AD domain “mydomain.com” and there is also domain “mydomain2.com”. The two are connected with full two way trust.
SSSD can happily recognize users from “mydomain.com”, but fails with users from “mydomain2.com” - sssd complains that:
(Mon Jul 30 08:26:38 2018) [sssd[be[adesto]]] [get_port_status] (0x1000): Port status of port 389 for server 'server.mydomain2.com' is 'not working'
(Mon Jul 30 08:26:38 2018) [sssd[be[adesto]]] [get_port_status] (0x0080): SSSD is unable to complete the full connection request, this internal status does not necessarily indicate network port issues.
But I can connect to that server with ldapsearch just fine (using a TGT obtained with kinit –k hostname$).
Earlier in the logs I spotted that SSSD is trying to obtain TGT with a wrong principal “host/hostname@REALM” instead of “hostname$@REALM”:
(Mon Jul 30 08:32:34 2018) [sssd[be[adesto]]] [sdap_get_tgt_recv] (0x0400): Child responded: 14 [Client 'host/hostname@mydomain.COM' not found in Kerberos database], expired on [0]
(Mon Jul 30 08:32:34 2018) [sssd[be[adesto]]] [sdap_kinit_done] (0x0100): Could not get TGT: 14 [Bad address]
(Mon Jul 30 08:32:34 2018) [sssd[be[adesto]]] [sdap_cli_kinit_done] (0x0400): Cannot get a TGT: ret [1432158226](Authentication Failed)
I am wondering why is SSSD trying now, all of sudden, to obtain a TGT using wrong principal?
Using RHEL-7.
Thanks,
Ondrej