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.

Description of problem:
Portmapper has been missed from the list of open ports both the ipa-adtrust-install and the documentation (https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Windows_Integration_Guide/trust-requirements.html#trust-req-ports). Microsoft link references the complete list of ports here:
https://msdn.microsoft.com/en-us/library/dd560683%28v=ws.10%29.aspx 

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Alexander, should port-mapper port be added to docs and ipa-adtrust-install output as required port to be opened for trusts?

Yes, I asked Christina to file this bug specifically to document the port mapper.

Upstream ticket:
https://fedorahosted.org/freeipa/ticket/5414

master:
    a566657f9d73a01b08017d251c4a0776d46265e2 Incomplete ports for IPA AD Trust 
ipa-4-2:
    e76e86656ae5c8f5e59a340e1ab4f9d107af7916 Incomplete ports for IPA AD Trust

This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions

Fix is seen.

Portmapper port is mentioned in https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Windows_Integration_Guide/trust-requirements.html#trust-req-ports

Endpoint resolution portmapper 	135 	        TCP
NetBIOS-DGM 	                138 	        TCP and UDP
NetBIOS-SSN 	                139 	        TCP and UDP
LDAP 	                        389 	        TCP and UDP ⁠[a]
Microsoft-DS 	                445 	        TCP and UDP
Endpoint mapper listener range  1024-1300 	TCP

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2016-2404.html