Bug 180157

Summary: Can't authenticate using win2k3 server when sidhistory is set on user
Product: Red Hat Enterprise Linux 4 Reporter: Bastien Nocera <bnocera>
Component: sambaAssignee: Jay Fenlason <fenlason>
Status: CLOSED ERRATA QA Contact: David Lawrence <dkl>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.0CC: jfeeney, tao
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: RHBA-2006-0599 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-08-10 21:43:08 UTC Type: ---
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: 181409    

Description Bastien Nocera 2006-02-06 13:15:27 UTC
samba-3.0.10-1.4E.2-i386

When running wbinfo -a against such a user:
plaintext password authentication failed
error code was NT code 0x00000001 (0x1)
error messsage was: NT code 0x00000001
Could not authenticate user <stripped> with plaintext password
challenge/response password authentication failed
error code was NT code 0x00000001 (0x1)
error messsage was: NT code 0x00000001
Could not authenticate user <stripped> with challenge/response 

Upstream samba bug at:
https://bugzilla.samba.org/show_bug.cgi?id=2245
And upstream commit message:
http://lists.samba.org/archive/samba-cvs/2005-January/054527.html

Patch tested successfully, and applies with fuzziness against our current samba
version.

Comment 3 Bob Johnson 2006-04-11 15:42:57 UTC
This issue is on Red Hat Engineering's list of planned work items 
for the upcoming Red Hat Enterprise Linux 4.4 release.  Engineering 
resources have been assigned and barring unforeseen circumstances, Red 
Hat intends to include this item in the 4.4 release.

Comment 6 Red Hat Bugzilla 2006-08-10 21:43:08 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2006-0599.html