In article <59950.129.80.22.143.1091558102.squirrel@129.80.22.143>, Gerry
Doris wrote:> I have been getting flooded with the following error messages:
>
> smbd[8874]: getpeername failed. Error was Transport endpoint is not
> connected
> smbd[8874]: read_socket_data: recv failure for 4. Error = Connection
> reset by peer
>
> I can't figure out how to stop these smb errors short of shutting down
> samba. I have both an XP Pro and often a Win2000 box on my network and
> assume they're causing the errors. These boxes have been configured by
> the IT guys where I work and have a number of security items enabled.
I'm
> not able to make configuration changes to these boxes.
>
> However, everything that is supposed to work does. I just don't want
to
> see these messages cluttering up my log files anymore.
>
> My smb.conf file is standard. This system is neither a domain or
> preferred master nor is wins support turned on. I only use samba on this
> system so the Win boxes can use the attached printers. I'm running
Fedora
> core 2.
>
> I'd appreciate any suggestions on how to turn these errors off .
>
Try this in smb.conf.
[global]
syslog = 0
I'm not sure this will work, but it's worth a try.
I don't think this will work on the samba logs though, even with
log level = 0.
And yes, I agree, these error messages are annoying.
Sten