Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 17 Sep 2001 11:53:50 -0500
From:      "mario" <madd@tecdigital.net>
To:        <questions@freebsd.org>
Subject:   Samba problems
Message-ID:  <000b01c13f99$535637b0$1ea5190a@Compilar>

next in thread | raw e-mail | index | archive | help
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..

Any help is appreciated,


Mario Doria



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?000b01c13f99$535637b0$1ea5190a>