Bug 1327697
Summary: | schannel connections fail to the DC because netlogon credentials are not updated correctly | ||||||
---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Orion Poplawski <orion> | ||||
Component: | samba | Assignee: | Andreas Schneider <asn> | ||||
Status: | CLOSED ERRATA | QA Contact: | Robin Hack <rhack> | ||||
Severity: | high | Docs Contact: | |||||
Priority: | high | ||||||
Version: | 6.7 | CC: | afarley, alden.1, asn, baumanmo, bloch, Colin.Simpson, gdeschner, grundblom, jarrpa, kesquires, lmiksik, lpol, magnus.moren, marvin24, maryinman, metze, michal.bruncko, mkolaja, mvermaes, oirraza, rhack, rich, salmy, sbose, ssn, thomas.jarosch, tscherf, vorpal | ||||
Target Milestone: | rc | Keywords: | Regression, ZStream | ||||
Target Release: | --- | ||||||
Hardware: | All | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | samba-3.6.23-34.el6 | Doc Type: | Bug Fix | ||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | |||||||
: | 1329523 1329960 1329961 1329962 1329964 1329966 1329967 (view as bug list) | Environment: | |||||
Last Closed: | 2017-03-21 10:16:22 UTC | Type: | Bug | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Bug Depends On: | |||||||
Bug Blocks: | 1269194, 1329523, 1329960, 1329961, 1329962, 1329964, 1329966, 1329967 | ||||||
Attachments: |
|
Description
Orion Poplawski
2016-04-15 16:08:53 UTC
Starting winbind fixes this. Apologies. Actually, it doesn't. I do get farther: # smbclient -U USER -L SERVER Enter USER's password: Domain=[DOMAIN] OS=[Unix] Server=[Samba 3.6.23-30.el6_7] Sharename Type Comment --------- ---- ------- homes Disk Home Directories netlogon Disk Network Logon Service web Disk NWRA Boulder web documents ftp Disk NWRA Boulder ftp file repository data Disk Data drives home Disk Home dir local Disk Local dir scans Disk Scanned Documents IPC$ IPC IPC Service (NWRA Boulder Network Server) user Disk Home Directories session setup failed: NT_STATUS_ACCESS_DENIED NetBIOS over TCP disabled -- no workgroup available Then I get an abrt crash report for winbind on the server # smbclient -U USER -L SERVER Enter USER's password: session setup failed: NT_STATUS_ACCESS_DENIED Created attachment 1147713 [details]
abrt report
We are already aware of the issue and working on it. I am also having this issue with Scientific Linux 6.7 and upgraded last Wednesday across our systems. I found that the problem lies in the netbios name resolution (nmb). If the user specifies the fully qualified domain name of the active directory, they are granted access, otherwise if they use the netbios name of the domain, I will see the "NT_STATUS_ACCESS_DENIED" message. I also found that domain joined windows boxes are able to access the samba shares, but I believe that is because they have a current kerberos token. So, ad.domain.local\username - works localdomain\username - does not work I hope this helps, -Glen (In reply to Glen Rundblom from comment #6) > I am also having this issue with Scientific Linux 6.7 and upgraded last > Wednesday across our systems. I found that the problem lies in the netbios > name resolution (nmb). If the user specifies the fully qualified domain name > of the active directory, they are granted access, otherwise if they use the > netbios name of the domain, I will see the "NT_STATUS_ACCESS_DENIED" > message. > > I also found that domain joined windows boxes are able to access the samba > shares, but I believe that is because they have a current kerberos token. > > So, ad.domain.local\username - works > localdomain\username - does not work > > I hope this helps, > -Glen Update: I found that specifying the fully qualified domain name was actually engaging in a kerberos ticket and granting access, I found on an ubuntu machine that installing krb5-user allowed nautilus to get a kerberos ticket, and then allow access (it was not working without it), so I suppose that is the piece that apple/mac clients and Windows clients were doing that I did not notice yet.. Pathetic. 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/RHSA-2017-0662.html |