I have a Samba share on a Solaris 8 server that is being accessed from a NT server. It works most all of the time except every night it will fail for about 25mins before it works. The log.smbd file is filled with several messages that repeat over and over. The connection seems to work all other times. Jeff [2002/09/17 21:41:41, 0] lib/util_sock.c:write_socket_data(542) write_socket_data: write failure. Error = Broken pipe [2002/09/17 21:41:41, 0] lib/util_sock.c:write_socket(565) write_socket: Error writing 190 bytes to socket 22: ERRNO = Broken pipe [2002/09/17 21:41:41, 0] libsmb/clientgen.c:cli_send_smb(88) Error writing 190 bytes to client. -1 [2002/09/17 21:42:01, 0] lib/util_sock.c:read_socket_with_timeout(300) read_socket_with_timeout: timeout read. read error = Connection reset by peer. [2002/09/17 21:42:01, 0] lib/util_sock.c:write_socket_data(542) write_socket_data: write failure. Error = Broken pipe [2002/09/17 21:42:01, 0] lib/util_sock.c:write_socket(565) write_socket: Error writing 168 bytes to socket 24: ERRNO = Broken pipe [2002/09/17 21:42:01, 0] libsmb/clientgen.c:cli_send_smb(88) Error writing 168 bytes to client. -1 [2002/09/17 21:42:01, 0] passdb/pdb_smbpasswd.c:startsmbfilepwent(171) startsmbfilepwent_internal: unable to open file /usr/local/samba/private/smbpasswd. Error was No such file or directory [2002/09/17 21:42:01, 0] passdb/pdb_smbpasswd.c:pdb_getsampwnam(1368) unable to open passdb database. [2002/09/17 21:48:59, 0] lib/util_sock.c:write_socket_data(542) write_socket_data: write failure. Error = Broken pipe The content of this email message and any attachments are confidential and may be legally privileged, intended solely for the addressee. If you are not the intended recipient, be advised that any use, dissemination, distribution, or copying of this e-mail is strictly prohibited. If you receive this message in error, please notify the sender immediately by reply email and destroy the message and its attachments.