Samba oddness

William O'Higgins Witteman william.ohiggins-H217xnMUJC0sA/PxXw9srA at
Wed Nov 4 23:09:24 UTC 2009

On Wed, Nov 04, 2009 at 05:11:25PM -0500, Evan Leibovitch wrote:
>> I recently upgraded samba from 2:3.3.4-1 to 2:3.4.2-1, and afterwards
>> none of my windows users were able to connect - they received password
>> errors.
>> I needed to recreate the passwords for all of my users before I was able
>> to get them back on the file server.  This was (of course) a PITA, but
>> hopefully if another TLUGger has a problem, they will read this before
>> they tear out their hair.
>Thanks for the warning.
>I assume you mean just the Samba password (ie, set using `smbpasswd`),

Correct - I had to freshen each user's password (which I had
conveniently set for them, and recorded)

>I've looked on launchpad and don't see this reported as a bug. Is this
>expected upgrade behaviour?

Goodness, I hope not.  I did see a reference to this in the past, so
I'll keep an eye on things.  I read that this can revert and you have to
refresh the passwords again.  I'll keep you posted.

After samba issues and a round of ignorant users spreading virii around
my network, I wish I could move everyone off windows - I could set
things up very nicely with sshfs and Linux or Mac computers that I could
not only keep clean of viruses, but could also effectively administer
remotely.  Someday...



-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 190 bytes
Desc: Digital signature
URL: <>

More information about the Legacy mailing list