On Tue, Oct 22, 2002 at 06:29:30PM +0200, [EMAIL PROTECTED] wrote: > for months, we keep fighting issues with smbd > (now at released 2.2.6), config is with spoolss, > domain logon, and the client in question is an > NT4 machine. server is a i386/linux 2.2.19 > > For a very long time, we thought it was related > to oplocks, but now after having them disabled, > it still is there. > > Level 3 Log is as follows: > > [2002/10/22 17:08:18, 3] smbd/ipc.c:reply_trans(480) > trans <\PIPE\> data=1224 params=0 setup=2 > [2002/10/22 17:08:18, 3] smbd/ipc.c:named_pipe(334) > named pipe command on <> name > [2002/10/22 17:08:18, 3] smbd/ipc.c:api_fd_reply(296) > Got API command 0x26 on pipe "spoolss" (pnum 7222)free_pipe_context: > destroying talloc pool of size 0 > [2002/10/22 17:08:18, 3] rpc_server/srv_pipe.c:api_pipe_request(1148) > Doing \PIPE\spoolss > [2002/10/22 17:08:18, 3] rpc_server/srv_pipe.c:api_rpcTNP(1180) > api_rpcTNP: pipe 29218 rpc command: SPOOLSS_GETPRINTER > [2002/10/22 17:08:18, 3] > rpc_server/srv_pipe_hnd.c:free_pipe_context(448) > free_pipe_context: destroying talloc pool of size 1740 > [2002/10/22 17:08:18, 0] lib/util_sock.c:write_socket_data(499) > write_socket_data: write failure. Error = Broken pipe > [2002/10/22 17:08:18, 0] lib/util_sock.c:write_socket(524) > write_socket: Error writing 1264 bytes to socket 6: ERRNO = Broken > pipe > [2002/10/22 17:08:18, 0] lib/util_sock.c:send_smb(704) > Error writing 1264 bytes to client. -1. (Broken pipe) > > And in the end, it will exit: > > [2002/10/22 17:08:18, 3] smbd/server.c:exit_server(495) > Server exit (send_trans_reply: send_smb failed.
This means the client disconnected from the server. A debug level 10 probably wouldn't help, capture the ethernet packets with ethereal and find out whether it's the server or client sending a TCP FIN or RST packet - that's who to pin the blame on. In this log my guess would be it's the client that is doing the FIN or RST - there's nothing that smbd can do about it. If I'm correct, as to why the client is doing this, I don't have a clue unfortunately. You will have to wade into the oily pool of Windows :-) :-). Jeremy -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
