Description of problem: My logs are flooded with this junk all the time: Feb 6 07:48:57 arturo smbd[16480]: [2010/02/06 07:48:57, 0] lib/util_sock.c:1491(get_peer_addr_internal) Feb 6 07:48:57 arturo smbd[16480]: getpeername failed. Error was Transport endpoint is not connected Feb 6 07:48:57 arturo smbd[16480]: [2010/02/06 07:48:57, 0] lib/util_sock.c:738(write_data) Feb 6 07:48:57 arturo smbd[16480]: [2010/02/06 07:48:57, 0] lib/util_sock.c:1491(get_peer_addr_internal) Feb 6 07:48:57 arturo smbd[16480]: getpeername failed. Error was Transport endpoint is not connected Feb 6 07:48:57 arturo smbd[16480]: write_data: write failure in writing to client 0.0.0.0. Error Connection reset by peer Feb 6 07:48:57 arturo smbd[16480]: [2010/02/06 07:48:57, 0] smbd/process.c:62(srv_send_smb) Feb 6 07:48:57 arturo smbd[16480]: Error writing 4 bytes to client. -1. (Transport endpoint is not connected) Feb 6 07:49:07 arturo smbd[16483]: [2010/02/06 07:49:07, 0] lib/util_sock.c:1491(get_peer_addr_internal) Feb 6 07:49:07 arturo smbd[16483]: getpeername failed. Error was Transport endpoint is not connected Feb 6 07:49:07 arturo smbd[16483]: [2010/02/06 07:49:07, 0] lib/util_sock.c:738(write_data) Feb 6 07:49:07 arturo smbd[16483]: [2010/02/06 07:49:07, 0] lib/util_sock.c:1491(get_peer_addr_internal) Feb 6 07:49:07 arturo smbd[16483]: getpeername failed. Error was Transport endpoint is not connected Feb 6 07:49:07 arturo smbd[16483]: write_data: write failure in writing to client 0.0.0.0. Error Connection reset by peer Feb 6 07:49:07 arturo smbd[16483]: [2010/02/06 07:49:07, 0] smbd/process.c:62(srv_send_smb) Feb 6 07:49:07 arturo smbd[16483]: Error writing 4 bytes to client. -1. (Transport endpoint is not connected) Version-Release number of selected component (if applicable): samba-3.4.5-55.fc12.x86_64 Additional info: Someone suggested setting "smb ports = 445" but this just cuts off all smb access entirely.
I am running Samba 3.4.7-58 on Fedora 12, x86_64. I was experiencing the problem described, above, earlier today. Here is what fixed the problem for me: I had recently upgraded from Fedora 11 to 12. Samba had been working on Fedora 11. After the upgrade, the file /etc/sysconfig/iptables-config, which is owned by the RPM package 'iptables' (I have version 1.4.5-1.fc12.x86_64 installed), had replaced my previous configuration file. Here is the difference between the F11 and F12 versions of the file: $ cd /etc/sysconfig/ $ sudo diff iptables-config iptables-config.new 6c6 < IPTABLES_MODULES="nf_conntrack_netbios_ns" --- > IPTABLES_MODULES="" I restored the setting for the IPTABLES_MODULES configuration option and then restarted the 'iptables' service. I am now able to connect to Samba shares even after several operating system reboots. If someone knows a reason for not making this change to /etc/sysconfig/iptables-config, please let me know.
Created attachment 411164 [details] Some smbd errors generated after a change to /etc/sysconfig/iptables-config
For what it is worth, 'smbd' is still generating error messages after the change I described. The difference is that Samba shares can now be seen and used despite the error messages. Previously, no Samba shares could be seen or used by an MSwin client.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
Most probably already fixed in current version, please reopen if still an issue.
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '12'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 12's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 12 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping