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:

AD user cannot access samba share using sssd. It doesn't seem to be able to connect at all.


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

samba-libs-4.1.1-31.el7.x86_64
samba-common-4.1.1-31.el7.x86_64
samba-client-4.1.1-31.el7.x86_64

How reproducible:


Steps to Reproduce:
1. changed debugging
2. changed configurations
3.

Actual results:

No change in access

Expected results:

share connection

Additional info:

Created attachment 1095713 [details]
most recent sosreport

Since creating the bz, I determined that the customer was trying to access the share using the ip address, instead of the FQDN. Once they used the FQDN to log in, they were able to connect.

Yes, there are various limitations when using sssd for AD integration and samba, please keep returning feedback when you encounter other problems. 

Thanks for the feedback!