Sekigawa Ai
2019-Jun-17 13:17 UTC
[Samba] What does "NT_STATUS_PIPE_BROKEN" in log files mean ?
Hi All, One day we upgraded client pc's OS from Windows7 to Windows10, Windows10 clients could not access a samba server. When we re-enabled the SMBv1 protocol on Windows10, Windows10 clients still could not access a samba server. After adding the following [global] settings, Windows10 clients could access a samba server at last. ------------------------------------------------------------ min protocol = SMB2 max protocol = SMB2 ------------------------------------------------------------ But Windows10 clients could not access a samba server via VPN. Samba's log files show "smbd_smb2_request_incoming: client read error NT_STATUS_PIPE_BROKEN" in many times. What does "NT_STATUS_PIPE_BROKEN" in log files mean ? See below for detail. ------------------------------------------------------------ [root at machine samba]# cat log.XXX.XXX.XXX.XXX [2019/06/14 13:15:48.874851, 3] lib/access.c:338(allow_access) Allowed connection from XXX.XXX.XXX.XXX (XXX.XXX.XXX.XXX) [2019/06/14 13:15:48.874963, 3] smbd/oplock.c:922(init_oplocks) init_oplocks: initializing messages. [2019/06/14 13:15:48.875051, 3] smbd/oplock_linux.c:246(linux_init_kernel_oplocks) Linux kernel oplocks enabled [2019/06/14 13:15:48.875133, 3] smbd/process.c:1609(process_smb) Transaction 0 of length 72 (0 toread) [2019/06/14 13:15:48.885221, 2] smbd/reply.c:553(reply_special) netbios connect: name1=*SMBSERV0x0 name2=XXX-XXX 0x0 [2019/06/14 13:15:48.886409, 2] smbd/reply.c:573(reply_special) netbios connect: local=_smbserv remote=XXX-XXX, name type = 0 [2019/06/14 13:15:48.911383, 3] smbd/process.c:1609(process_smb) Transaction 0 of length 73 (0 toread) [2019/06/14 13:15:48.911464, 3] smbd/process.c:1414(switch_message) switch message SMBnegprot (pid 4278) conn 0x0 [2019/06/14 13:15:48.926995, 3] smbd/negprot.c:598(reply_negprot) Requested protocol [NT LM 0.12] [2019/06/14 13:15:48.927056, 3] smbd/negprot.c:598(reply_negprot) Requested protocol [SMB 2.002] [2019/06/14 13:15:48.927077, 3] smbd/negprot.c:598(reply_negprot) Requested protocol [SMB 2.???] [2019/06/14 13:15:48.927225, 3] smbd/negprot.c:704(reply_negprot) Selected protocol SMB 2.002 [2019/06/14 13:15:48.962421, 2] smbd/smb2_server.c:2631(smbd_smb2_request_incoming) smbd_smb2_request_incoming: client read error NT_STATUS_PIPE_BROKEN [2019/06/14 13:15:48.962611, 3] smbd/server_exit.c:181(exit_server_common) Server exit (NT_STATUS_PIPE_BROKEN) ------------------------------------------------------------ If you have time, Please let me know. Regards, Ai Sekigawa --- ??E???????? ????????????????????????? https://www.avast.com/antivirus
Rowland penny
2019-Jun-17 13:50 UTC
[Samba] What does "NT_STATUS_PIPE_BROKEN" in log files mean ?
On 17/06/2019 14:17, Sekigawa Ai via samba wrote:> Hi All, > > One day we upgraded client pc's OS from Windows7 to Windows10, > Windows10 clients could not access a samba server. > > When we re-enabled the SMBv1 protocol on Windows10, Windows10 clients > still could not access a samba server. > > After adding the following [global] settings, Windows10 clients could access > a samba server at last. > ------------------------------------------------------------ > min protocol = SMB2 > max protocol = SMB2 > ------------------------------------------------------------ > > But Windows10 clients could not access a samba server via VPN. > Samba's log files show "smbd_smb2_request_incoming: client read error > NT_STATUS_PIPE_BROKEN" in many times. > > What does "NT_STATUS_PIPE_BROKEN" in log files mean ?The pipe operation has failed because the other end of the pipe has been closed. I suggest you check the windows logs to see why this is happening. Rowland
Sekigawa Ai
2019-Jun-19 00:10 UTC
[Samba] What does "NT_STATUS_PIPE_BROKEN" in log files mean ?
Hi Rowland,> I suggest you check the windows logs to see why this is happening.Thanks a lot ! Regards, Ai Sekigawa> On 17/06/2019 14:17, Sekigawa Ai via samba wrote: > > Hi All, > > > > One day we upgraded client pc's OS from Windows7 to Windows10, > > Windows10 clients could not access a samba server. > > > > When we re-enabled the SMBv1 protocol on Windows10, Windows10 clients > > still could not access a samba server. > > > > After adding the following [global] settings, Windows10 clients could access > > a samba server at last. > > ------------------------------------------------------------ > > min protocol = SMB2 > > max protocol = SMB2 > > ------------------------------------------------------------ > > > > But Windows10 clients could not access a samba server via VPN. > > Samba's log files show "smbd_smb2_request_incoming: client read error > > NT_STATUS_PIPE_BROKEN" in many times. > > > > What does "NT_STATUS_PIPE_BROKEN" in log files mean ? > > The pipe operation has failed because the other end of the pipe has been closed. > > I suggest you check the windows logs to see why this is happening. > > Rowland > > > -- To unsubscribe from this list go to the following URL and read the > instructions: https://lists.samba.org/mailman/options/samba--- ??E???????? ????????????????????????? https://www.avast.com/antivirus