Header Shadow Image


Error writing bytes to client Transport endpoint is not connected

 

While transferring a large file, I've disconnected then disabled the WIRELESS port only to receive these messages in /var/log/messages on the HTPC server.  No connection was possible from the Windows 7 desktops to the server at this point even waiting a bit didn't help.  Looked like something crashed during the disabling of the wireless card while files were being sent up to my Windows 7 PC.  On the HTPC server, these are the messages that were received:
 
Mar 25 20:25:46 mbpc smbd[555]: [2013/03/25 20:25:46.416588,  0] lib/util_sock.c:474(read_fd_with_timeout)
Mar 25 20:25:46 mbpc smbd[555]: [2013/03/25 20:25:46.416794,  0] lib/util_sock.c:1441(get_peer_addr_internal)
Mar 25 20:25:46 mbpc smbd[555]:   getpeername failed. Error was Transport endpoint is not connected
Mar 25 20:25:46 mbpc smbd[555]:   read_fd_with_timeout: client 0.0.0.0 read error = Connection reset by peer.
Mar 25 20:25:46 mbpc smbd[555]: [2013/03/25 20:25:46.419352,  0] lib/util_sock.c:680(write_data)
Mar 25 20:25:46 mbpc smbd[555]: [2013/03/25 20:25:46.419461,  0] lib/util_sock.c:1441(get_peer_addr_internal)
Mar 25 20:25:46 mbpc smbd[555]:   getpeername failed. Error was Transport endpoint is not connected
Mar 25 20:25:46 mbpc smbd[555]:   write_data: write failure in writing to client 0.0.0.0. Error Broken pipe
Mar 25 20:25:46 mbpc smbd[555]: [2013/03/25 20:25:46.419563,  0] smbd/process.c:79(srv_send_smb)
Mar 25 20:25:46 mbpc smbd[555]:   Error writing 75 bytes to client. -1. (Transport endpoint is not connected)
Mar 25 20:25:46 mbpc smbd[555]: [2013/03/25 20:25:46.419692,  0] lib/util_sock.c:680(write_data)
Mar 25 20:25:46 mbpc smbd[555]: [2013/03/25 20:25:46.419740,  0] lib/util_sock.c:1441(get_peer_addr_internal)
Mar 25 20:25:46 mbpc smbd[555]:   getpeername failed. Error was Transport endpoint is not connected
Mar 25 20:25:46 mbpc smbd[555]:   write_data: write failure in writing to client 0.0.0.0. Error Broken pipe
Mar 25 20:25:46 mbpc smbd[555]: [2013/03/25 20:25:46.419835,  0] smbd/process.c:79(srv_send_smb)
Mar 25 20:25:46 mbpc smbd[555]:   Error writing 75 bytes to client. -1. (Transport endpoint is not connected)
Mar 25 20:25:46 mbpc smbd[555]: [2013/03/25 20:25:46.419999,  0] lib/util_sock.c:680(write_data)
Mar 25 20:25:46 mbpc smbd[555]: [2013/03/25 20:25:46.420062,  0] lib/util_sock.c:1441(get_peer_addr_internal)
Mar 25 20:25:46 mbpc smbd[555]:   getpeername failed. Error was Transport endpoint is not connected
Mar 25 20:25:46 mbpc smbd[555]:   write_data: write failure in writing to client 0.0.0.0. Error Broken pipe
Mar 25 20:25:46 mbpc smbd[555]: [2013/03/25 20:25:46.420157,  0] smbd/process.c:79(srv_send_smb)
Mar 25 20:25:46 mbpc smbd[555]:   Error writing 75 bytes to client. -1. (Transport endpoint is not connected)
 
Restarting the service using service smb restart yielded these messages:
 
Mar 25 20:29:52 mbpc smbd[18330]: [2013/03/25 20:29:52.659126,  0] smbd/server.c:281(remove_child_pid)
Mar 25 20:29:52 mbpc smbd[18330]:   Could not find child 620 — ignoring
Mar 25 20:30:30 mbpc smbd[639]: [2013/03/25 20:30:30.786449,  0] smbd/server.c:500(smbd_open_one_socket)
Mar 25 20:30:30 mbpc smbd[639]:   smbd_open_once_socket: open_socket_in: Address already in use
 
 
On the Windows 7 side of things I get the message:
 
The mapped network drive could nto be created because the following error has occurred:
The specified network name is no longer available.
 
Which doesn't help all that much.  (We already know we can't connect to it.)  Using another computer, I could verify and map the network drives there successfully meaning the issue must have been isolated to my Windows 7 and just this particular workstation.  This eliminated the HTPC server completely.
 
Unfortunately, I took a less then scientific approach and restarted my laptop to recover my connection suggesting a service was crashed by the cancelled installed operation that was restarted on a complete system restart.  However nothing in event viewer hinted at what that service might be.  Next time this happens, we'll have to dig a little deeper.
 
Cheers,
Tom

One Response to “Error writing bytes to client Transport endpoint is not connected”

  1. I had similar problem. I had probably bad the relation among user and group.

    I deleted user and group maded new one and it was OK

     

        Jan

Leave a Reply

 

     
  Copyright © 2003 - 2013 Tom Kacperski (microdevsys.com). All rights reserved.

Creative Commons License
This work is licensed under a Creative Commons Attribution 3.0 Unported License