On Wed, Mar 05, 2008 at 04:17:35PM -0500, Phil wrote: > Hello all, > > I'm far from being a samba expert and truth be told I could use some > education on networking in general but here it is... > > I have a stand alone samba server that I use a stunnel to connect to. Reads > take place fine from the server but writes *always* fail exactly one time > per open session, but if you immediately try to copy the file again it will > work (without closing the window), in fact all file transfers will work > perfectly beyond this point. By open session I mean from the time you open > up the network drive to the time you close the window. On the client side I > receive the message "Cannot copy FILENAME: The specified network name is no > longer available.", in the server logs I see the following; > > Mar 5 15:59:52 HOSTNAME smbd[13086]: [2008/03/05 15:59:52, 0] > lib/util_sock.c:read_data(534) > Mar 5 15:59:52 HOSTNAME smbd[13086]: read_data: read failure for 4 bytes > to client 127.0.0.1. Error = Connection reset by peer
All that means is that the client terminated the connection. You need to find out why. Jeremy. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba