[Samba] open_sockets_smbd: accept: Software caused connection abort

Steve McKenna mckennst at earthlink.net
Sat Aug 28 08:33:57 GMT 2004


Great call, Mac!  You are entirely correct.  I have a small and static user 
community.  My smbpasswd file was generated from /etc/passwd by an older 
version of smbpasswd and *did not even have* LCT fields.  The old entries 
looked like this:

steve:19261:9A44F80C320B12A4E72C567C8AF76A05:B96E3B9B62962D61AA2D97F3DAE5365D:I. 
Ama Bonehead:/home/steve:/bin/csh

New entries look like:

steve:19261:9A44F80C320B12A4E72C567C8AF76A05:B96E3B9B62962D61AA2D97F3DAE5365D:[U 
]:LCT-41371D64:

I trashed the whole file and rebuilt from scratch.  Everything's working again.

Thanks much,
Steve


 >>>Mac wrote:
 >>><snip...I love a good one-liner>

Somewhere in the 3.x release series security was tightened up.  I'll bet 
that the LCT for each of your users is 000000.  When Samba 3.0.6 finds such 
an entry, it disables the user and wipes both their passwords.

I wrote the following one-liner:-

awk -F: '$3 !~ /XX/ && $6=="LCT-00000000" {print $1 ":" $2 ":" $3 ":" $4 
":" $5 ":LCT-00000010:"; next } {print }' smbpasswd.back | wc -l > 
smbpasswd.LCT

which searched through my backup copy of the smbpasswd file and changed the 
LCT.
 >>><snip>




More information about the samba mailing list