Red Hat Bugzilla – Bug 444999
samba/winbind - Receiving SMB: Server stopped responding
Last modified: 2008-12-17 13:39:02 EST
Description of problem: When a samba server is configured as a PDC, with samba
version 3.0.25b, the following message is logged over and over again in smb.log:
"libsmb/clientgen.c:cli_receive_smb(112) Receiving SMB: Server stopped
responding". The log entry is repeated 3 times in quick succession, and the
cycle repeats every 5 minutes. Also, client machines take a long time to
connect to samba shared resources (often 30 seconds or longer). This is a known
samba bug that has been resolved as of samba release 3.0.28a (please see thread
at https://bugzilla.samba.org/show_bug.cgi?id=4973 ). Is the fix for this issue
in the stream for rhel4/5?
Version-Release number of selected component (if applicable):
How reproducible: always/continuous
Steps to Reproduce:
1. Install samba 3.0.25b via rpm and configure as PDC.
2. Have Windows XP/Vista clients connect to samba shares.
3. Examine smb.log
Actual results: Many "server stopped responding" entries in smb.log. Many
instances of very long connection times.
Expected results: Server doesn't stop responding. Clients can connect in a
reasonable amount of time.
Yes should be fixed in the next update release of RHEL4 and RHEL5. Beta packages
are available for testing.
Great! Where can I get the beta for the samba packages?
Through RHN channel.