RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

This bug is created as a clone of upstream ticket:
https://fedorahosted.org/freeipa/ticket/4024

When establishing trust IPA might report following error message:

{{{
[root@host ~]# ipa trust-add ipaqe.com --type=ad --admin administrator --password
Active directory domain administrator's password:
ipa: ERROR: CIFS server communication error: code "-1073741811",
                message "Unexpected information received" (both may be "None")
}}}

The error code -1073741811 is NT_STATUS_INVALID_PARAMETER. What happens is that Samba library that we use tries to establish an authenticated connection to the AD DC using Kerberos credentials of the AD administrator and that fails  due to Kerberos-related issue.

In most cases the actual issue is clock skew, so it would be good to suggest to check time difference between AD and IPA.

Fixed upstream:
master: https://fedorahosted.org/freeipa/changeset/3693b8e51ae11b4bcda9cd7e90ff729fc66a5862
ipa-3-3: https://fedorahosted.org/freeipa/changeset/d2fbcd121eaeb56ab36da6b2f84c780e3af14125

How can we reproduce this one?

I tried skewing the clock a few times and running trust-add but, it's no longer failing.

Alexander or Sumit, can you please advise?

Recent MIT Kerberos versions contain a fix by Stef Walter which fixes  the clock skew issue for TGT requests. So I think this ticket can only be verified by checking if /usr/lib/python2.7/site-packages/ipaserver/dcerpc.py contains explanations for error code -1073741811 (NT_STATUS_INVALID_PARAMETER).

[root@dhcp207-151 ~]# grep -A4 1073741811 /usr/lib/python2.7/site-packages/ipaserver/dcerpc.py
    -1073741811: # NT_STATUS_INVALID_PARAMETER
        errors.RemoteRetrieveError(
            reason=_('AD domain controller complains about communication sequence. It may mean unsynchronized time on both sides, for example')),
}

Verified in version
[root@dhcp207-151 ~]# rpm -qf /usr/lib/python2.7/site-packages/ipaserver/dcerpc.py
ipa-server-trust-ad-3.3.3-17.el7.x86_64

This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.