From owner-freebsd-questions Mon Sep 17 15:53:49 2001 Delivered-To: freebsd-questions@freebsd.org Received: from mail.the-i-pa.com (mail.the-i-pa.com [151.201.71.132]) by hub.freebsd.org (Postfix) with SMTP id DC38237B40C for ; Mon, 17 Sep 2001 15:53:45 -0700 (PDT) Received: (qmail 42553 invoked from network); 17 Sep 2001 23:04:06 -0000 Received: from unknown (HELO proxy.the-i-pa.com) (151.201.71.210) by mail.the-i-pa.com with SMTP; 17 Sep 2001 23:04:06 -0000 Content-Type: text/plain; charset="iso-8859-1" From: Bill Moran Organization: Potential Technology To: "mario" , Subject: Re: Problems with samba Date: Mon, 17 Sep 2001 18:56:45 -0400 X-Mailer: KMail [version 1.2] References: <00a201c13fc7$b17f8250$1ea5190a@Compilar> In-Reply-To: <00a201c13fc7$b17f8250$1ea5190a@Compilar> MIME-Version: 1.0 Message-Id: <01091718564500.00330@proxy.the-i-pa.com> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG [moved to -questions, since I think it more belongs there] On Monday 17 September 2001 18:25, mario wrote: > Hello, > > I'm having some strange problems with samba. My Windows clients (ME and > 2000) report a "Semaphore timeout problem" while on the logs, samba > reports: [2001/09/17 11:32:25, 0] lib/util_sock.c:write_socket(568) > write_socket: Error writing 4 bytes to socket 12: ERRNO = Broken pipe > [2001/09/17 11:32:25, 0] lib/util_sock.c:send_smb(732) > Error writing 4 bytes to client. -1. (Broken pipe) > [2001/09/17 11:32:37, 0] lib/util_sock.c:get_socket_addr(1034) > getpeername failed. Error was Socket is not connected > [2001/09/17 11:32:37, 0] lib/util_sock.c:write_socket_data(544) > write_socket_data: write failure. Error = Broken pipe > [2001/09/17 11:32:37, 0] lib/util_sock.c:write_socket(568) > write_socket: Error writing 4 bytes to socket 12: ERRNO = Broken pipe > [2001/09/17 11:32:37, 0] lib/util_sock.c:send_smb(732) > Error writing 4 bytes to client. -1. (Broken pipe) > > This is an esporadic problem, sometimes the machines just connect to the > samba server with no problems. I recompilled samba under FreeBSD 4.4 and > stopped experiencing these problems on Friday. Today (Monday), the problems > are back. I recompilled again Samba but to no avail, the clients cannot > connect to the samba server.. Sounds a lot like hardware trouble. Are you getting any other errors in /var/log/messages? Does FTP and SSH and/or other protocols work while samba is having trouble. Verify the cabling, etc. I could be wrong, it's just that with the limited information, it sounds like the first thing to check would be verity that the hardware is sound. -- Bill Moran Potential Technology technical services (412) 793-4257 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message