Document URL:
https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html/integrating_rhel_systems_directly_with_windows_active_directory/connecting-rhel-systems-directly-to-ad-using-sssd_integrating-rhel-systems-directly-with-active-directory#discovering-and-joining-an-ad-domain-using-sssd_connecting-directly-to-ad

Describe the issue:
We have x number of cases were `realm join` fails due to required ports not open. `realm join` verbose output should show which port is open/close

1. realm join example.com -U administrator --verbose
   <snip>
   connection to ldap server/AD on port 389 = pass
   connection to ldap server/AD on port 88 = pass
   connection to ldap server/AD on port 3268 = fail
   ..
   <snip>

Suggestions for improvement:
As most of the join issues are related to port not open having this information in verbose output can reduce large number of cases.

Additional information:
The actual intention is to show customer which required ports are closed so they can figure out themself the ports which are required to be open instead of creating a case with Red Hat. More than 50% of the unable to join issues are due to required ports not open.

If customer still proceeds and opens the case even then its easier for the engineer to troubleshoot the issue and cases can be resolved within few comments.

https://access.redhat.com/solutions/5444941

I understand we present customer with above URL when the join fails. But providing exact specific data will be more beneficial.

IMPACT:
The RFE will be really helpful if implemented, A quick search in SFDC gives me around 245 cases and KCS article #1350723 has around 1078 cases linked. KCS #5444941 has around 280 Number of links.