Red Hat Bugzilla – Bug 87969
Samba errata package (2.2.7-4.8.0) fails to respond to domain logon or share requests and generates huge numbers of log entries
Last modified: 2014-08-31 19:24:49 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i586; en-US; rv:1.0.1) Gecko/20021003
Description of problem:
After updating samba with the up2date (the GUI version from the System Tools
menu), Samba no longer works (only Samba and Mozilla were updated due to a slow
connection). rpm -q samba returns 2.2.7-4.8.0.
Attempting to use smbclient results in a message that the server failed to
respone after some huge number of seconds after a long wait. Looking at the
logs it seems that this version of Samba is messed up.
I will be attempting to revert to the CD version shortly. If it doesn't work
I'll add that information here otherwise I'll leave the case as-is.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Upgrade Samba to RHN version
2.Attempt to access a share or do a domain login
Actual Results: 1) In Win98SE a message stating that the domain password was
wrong, or the server was not accessible was diaplayed.
2) Connection timed out with smbclient.
Expected Results: 1) Should have found and executed the logon script, and
2) Should have connected to the specified share.
Not all errata have been applied. Not having high speed sucks.
Please attach your /etc/samba/smb.conf file and the log file you mentioned, so I
can attempt to reproduce this.
Sorry about that. I accidentally deleted my logs so I reverted to the old samba
and reinstalled the errata package (and got the same problem). This probably is
for the best anyway since the logs are much smaller since I only tried
connecting once instead of many times with other things being varied on the
theory they were the problem.
Created attachment 90923 [details]
Samba logs and smb.conf (with full path from root)
Can you try the samba-2.2.7-5.8.0 packages I released yesterday? They include a
patch that fixes this problem (as well as the critical security fixes).
*** This bug has been marked as a duplicate of 86307 ***
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.