Red Hat Bugzilla – Bug 115984
Upgrade from samba-3.0.2-1rc1 to 3.0.2-5 broke samba: cannot log in no more
Last modified: 2014-08-31 19:25:53 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7a)
Description of problem:
Last night, yum upgraded my samba from samba-3.0.2-1rc1 to 3.0.2-5
Since then I can't log in no more. It keeps rejecting my password. The
curious thing is, I can't find anything in the samba logs nor in
I went back to samba-3.0.2-1rc1 and everything works again.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. upgrade to 3.0.2-5
At the very least I'll need a copy of your /etc/samba/smb.conf and a
better description of your Windows network configuration before I'll
have any chance at all of debugging this.
Created attachment 97764 [details]
Yes, sorry for being curt. I meant to provide more info, but then got
drawn to other tasks.
I attached the smb.conf (changed a few host names and ip addresses to
protect the innocent.)
I tried connecting from XP SP1, and another Fedora Core 1 box with
I tried resetting the smb user passwd with smbpasswd, didn't help.
The allow hosts line seems not to be the culprit: if I connect from
disallowed host, I _do_ get a log entry into /var/log/messages.
And *just* backing samba, samba-common and samba-client from
3.0.2-5 to 3.0.2-1rc1 makes it work again.
I have this sneaking suspicion that this is connected to the selinux
libraries. I run almost full Fedora development distro, but I still
have 2.4.x kernel without selinux support. Might the have been some
changes in samba wrt this samba-3.0.2-1rc1 to 3.0.2-5?
I just saw an interesting message:
Can you look at your smbpasswd file and see if perhaps this is
describing your problem?
This is exactly the problem I had. Still wondering why it didn't log
anything, but I'm happy with the problem solved.
This sort of support the best I could ever have hoped for. I should
give you a virtual gold star :).
Closing per information provided.