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.