[Samba] Why am i getting "Transport endpoint is not connected"
eds3141 at gmail.com
Fri May 10 07:40:55 MDT 2013
I got no replies to my last post "win 7 client can't map drive: getpeername
Anyway I've dug a little deeper on the server side by setting log level 10
"Transport endpoint is not connected"
Basically I compared the logs (several thousand lines!) from two windows 7
one of which always works (the good client) and one which always fails (the
On each client I ran
net view \\saturn
The logs are virtually identical up to the bad client error
The only differences are:
the bad client requests two additional protocols: [SMB 2.002] and [SMB
But then both client log files say "Selected protocol NT LM 0.12" anyway
Both clients call
set_remote_arch: Client arch is 'Win2K'
at the same point in the logs
But later on the good client calls
set_remote_arch: Client arch is 'Vista'
This does happen on the bad client but much later in the logs
Thats it, everything else is idetical up until the error!
On the good client we continue with
but on the bad client we see a
[2013/05/10 12:35:54.185760, 3] smbd/reply.c:846(reply_tcon_and_X)
[2013/05/10 12:35:54.186151, 0] lib/util_sock.c:474(read_fd_with_timeout)
[2013/05/10 12:35:54.186216, 0]
getpeername failed. Error was Transport endpoint is not connected
read_fd_with_timeout: client 0.0.0.0 read error = Connection reset by
[2013/05/10 12:35:54.186259, 10] smbd/process.c:291(receive_smb_raw_talloc)
[2013/05/10 12:35:43.755239, 3] smbd/reply.c:846(reply_tcon_and_X)
[2013/05/10 12:35:43.755642, 10]
got smb length of 100
Does anyone have any ideas how I can resolve this or thoughts on how to
Does the NT_STATUS_CONNECTION_RESET
mean the bad client is disconnecting ? But why ?
Please guys you are my last hope of getting to the bottom of this :(
More information about the samba