I have a toshiba copy machine that is also used as a scanner. The scanner can be set to store files to a SMB UNC. So I create a username/password for the scanner to login with, then configured a unc path for to store to. All was working well for a while. Then the scanner stopped storing to the samba share. Initial analysis seemed to indicate that the username/password was failing. So I reset it and again, the machine started working. (NOTE, these are changes to the toshiba MFD, not samba or samba-ad) Again, the scanner stopped storing files to the samba server. So I look in the samba logs and see this: [2016/09/12 12:47:13.387013, 3] ../source3/smbd/process.c:1538(switch_message) switch message SMBtdis (pid 9099) conn 0x7f88d8a835e0 [2016/09/12 12:47:13.387069, 3] ../source3/smbd/server_exit.c:246(exit_server_common) [2016/09/12 12:47:13.387080, 2] ../source3/smbd/service.c:1140(close_cnum) Server exit (failed to receive smb request) toshiba523print (ipv4:192.168.1.19:1321) closed connection to service scans [2016/09/12 12:47:13.387382, 1] ../source3/smbd/process.c:554(receive_smb_talloc) receive_smb_raw_talloc failed for client ipv4:192.168.1.19:1321 read error = NT_STATUS_CONNECTION_RESET. [2016/09/12 12:47:13.387679, 3] ../source3/smbd/server_exit.c:246(exit_server_common) Server exit (failed to receive smb request) This looks to me like the toshiba MFD/scanner is not doing things correctly. .. but then why is a TALLOC failing? This is for samba 4.4.3 server. A samba AD DC is running in a separate VM. Samba file server running in a host. Can anyone suggest what could be happening? The toshiba MFD works for a couple of days, then stops? (works means successfully creates files on the samba server) -- David Bear mobile: (602) 903-6476
On Mon, Sep 12, 2016 at 05:03:57PM -0700, David Bear via samba wrote:> I have a toshiba copy machine that is also used as a scanner. > The scanner can be set to store files to a SMB UNC. So I create a > username/password for the scanner to login with, then configured a unc path > for to store to. All was working well for a while. > > Then the scanner stopped storing to the samba share. Initial analysis > seemed to indicate that the username/password was failing. > > So I reset it and again, the machine started working. (NOTE, these are > changes to the toshiba MFD, not samba or samba-ad) > > Again, the scanner stopped storing files to the samba server. So I look in > the samba logs and see this: > > [2016/09/12 12:47:13.387013, 3] > ../source3/smbd/process.c:1538(switch_message) > switch message SMBtdis (pid 9099) conn 0x7f88d8a835e0 > [2016/09/12 12:47:13.387069, 3] > ../source3/smbd/server_exit.c:246(exit_server_common) > [2016/09/12 12:47:13.387080, 2] ../source3/smbd/service.c:1140(close_cnum) > Server exit (failed to receive smb request) > toshiba523print (ipv4:192.168.1.19:1321) closed connection to service > scans > [2016/09/12 12:47:13.387382, 1] > ../source3/smbd/process.c:554(receive_smb_talloc) > receive_smb_raw_talloc failed for client ipv4:192.168.1.19:1321 read > error = NT_STATUS_CONNECTION_RESET.This means a TCP RST packet usually. What does a wireshark trace show ?
Thanks for the response. I did not do a wireshark. I try to get one made. I'll see if I can get this to reproduce and follow the directions at https://wiki.samba.org/index.php/Capture_Packets If you don't see back from me on this thread its because I couldn't get it to reproduce the error. On Tue, Sep 13, 2016 at 3:23 PM, Jeremy Allison <jra at samba.org> wrote:> On Mon, Sep 12, 2016 at 05:03:57PM -0700, David Bear via samba wrote: > > I have a toshiba copy machine that is also used as a scanner. > > The scanner can be set to store files to a SMB UNC. So I create a > > username/password for the scanner to login with, then configured a unc > path > > for to store to. All was working well for a while. > > > > Then the scanner stopped storing to the samba share. Initial analysis > > seemed to indicate that the username/password was failing. > > > > So I reset it and again, the machine started working. (NOTE, these are > > changes to the toshiba MFD, not samba or samba-ad) > > > > Again, the scanner stopped storing files to the samba server. So I look > in > > the samba logs and see this: > > > > [2016/09/12 12:47:13.387013, 3] > > ../source3/smbd/process.c:1538(switch_message) > > switch message SMBtdis (pid 9099) conn 0x7f88d8a835e0 > > [2016/09/12 12:47:13.387069, 3] > > ../source3/smbd/server_exit.c:246(exit_server_common) > > [2016/09/12 12:47:13.387080, 2] ../source3/smbd/service.c: > 1140(close_cnum) > > Server exit (failed to receive smb request) > > toshiba523print (ipv4:192.168.1.19:1321) closed connection to service > > scans > > [2016/09/12 12:47:13.387382, 1] > > ../source3/smbd/process.c:554(receive_smb_talloc) > > receive_smb_raw_talloc failed for client ipv4:192.168.1.19:1321 read > > error = NT_STATUS_CONNECTION_RESET. > > This means a TCP RST packet usually. What does a wireshark trace > show ? >-- David Bear mobile: (602) 903-6476