RE: [Samba] Re: Stopping smb error messages
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Fri, 6 Aug 2004, Paul Farrow wrote: > I had been getting the exact same problem. And looking at an old post, > they recommended that port 445 was shut off to the samba box this makes > samba / smb negotiate its connections through port 339. I think Volker actually tracked this down to the netbios keep alives on port 445. You can try setting 'keepalive = 0' to workaround this in the meantime. cheers, jerry - - Alleviating the pain of Windows(tm) --- http://www.samba.org GnuPG Key- http://www.plainjoe.org/gpg_public.asc "If we're adding to the noise, turn off this song"--Switchfoot (2003) -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) Comment: For info see http://quantumlab.net/pine_privacy_guard/ iD8DBQFBIBYLIR7qMdg1EfYRAvmMAJ9XGdqZ+AyReZY3dJSluMELVHKb6QCgqnZz pUKjQosp8sfDiMMkEJ1op7U= =y2MY -END PGP SIGNATURE- -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
RE: [Samba] Re: Stopping smb error messages
I had been getting the exact same problem. And looking at an old post, they recommended that port 445 was shut off to the samba box this makes samba / smb negotiate its connections through port 339. I had my doubts but it seems to have worked for me. I am using samba 3.0.5 under Fedora Core 2 on a mini-itx V800 talking to windows 2003 server (web edition). The other problem I seemed to have was my smbmounts seemed to die after a while, which I never got to the bottom of, but I just pass a little file over my mounted filesystems and that keeps them running. So not sure if your problem is the one above or both, but it now works for me. Samba used to die every night not (touch wood) its been running for over 3 weeks with out an error. Hope that helps Paul http://www.farrowhosting.com -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Sten Sletbak Sent: 06 August 2004 11:58 To: [EMAIL PROTECTED] Subject: [Samba] Re: Stopping smb error messages In article <[EMAIL PROTECTED]>, 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 -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Re: Stopping smb error messages
In article <[EMAIL PROTECTED]>, 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 -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
