Bug 189502

Summary: smbclient locks up Active Directory account
Product: [Fedora] Fedora Reporter: Steve Isaacson <stevei>
Component: sambaAssignee: Simo Sorce <ssorce>
Status: CLOSED DUPLICATE QA Contact: David Lawrence <dkl>
Severity: medium Docs Contact:
Priority: medium    
Version: 5CC: gdeschner, jplans
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2007-03-23 23:05: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:
Attachments:
Description Flags
smbclient run with debug=10 none

Description Steve Isaacson 2006-04-20 16:30:55 UTC 
Description of problem:

While running smbclient that came with fc4, this command ran fine, day in and
day out from a cronjob:

smbclient $server_service -A $authfile -Tc $DIR/$dir.tar $dir

It simply connects to a Windows machine and tars up the directory.

After upgrading to fc5, the command would cause the Active Directory account to
be LOCKED OUT. Unfortunately I don't know anything about Active Directory so I
can't tell you what that means. What I know is that I would have to call the IT
department, they would confirm that the account is LOCKED, and then they would
UNLOCK it. Presumably the effect is the same as if someone attempted to log in
multiple times with the wrong password.


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

smbclient: Version 3.0.22-1.fc5
Active Directory: OS=[Windows 5.0] Server=[Windows 2000 LAN Manager]

How reproducible:

Easy to reproduce. Over and over. Just run the command above.



Steps to Reproduce:
1. Run a command similar to this:

smbclient $server_service -A $authfile -Tc $DIR/$dir.tar $dir

Actual results:

You receive an UNABLE TO CONNECT ACCOUNT IS LOCKED error message.
  


Expected results:

For smblient to connect and create tar file.

Additional info:

Connecting manually and issuing the tar command works fine.
I worked around the bug by writing a script that uses Expect to connect
and then do the tar.
Comment 1 Steve Isaacson 2006-04-20 16:46:10 UTC 
Created attachment 128044 [details]
smbclient run with debug=10

Output from running smbclient command with debug turned on. Error message
displayed at end of file.
Comment 2 Guenther Deschner 2007-03-14 15:29:52 UTC 
We need to see the contents of your $authfile (gray out the password of course)
for reproduction.
Comment 3 Steve Isaacson 2007-03-15 02:32:05 UTC 
I no longer have access to the file. Sorry.
Comment 4 Simo Sorce 2007-03-23 22:44:49 UTC 
I reproduced the bug, need to investigate more, thanks for reporting.
Comment 5 Simo Sorce 2007-03-23 23:05:08 UTC 

*** This bug has been marked as a duplicate of 176649 ***