[Samba] "getpeername failed. Error was Transport endpoint is not connected"

Fabian Arrotin fabian.arrotin at arrfab.net
Mon Apr 18 09:55:40 GMT 2005

I've already seen this in my logs...
A little search on Google shows me that Windows XP client try try to
connect to port 139 and 445 in parallel and drop the connection to port 
139 if the connect to 445 is successful.
In fact, no one was complaining about real network connection loss ...
More informations here : http://www.linuxaa.com/ftopic6568.html
Hope this helps.

On Mon, 2005-04-18 at 03:58 -0300, Guido Lorenzutti wrote:
> I get this error message "getpeername failed. Error was Transport 
> endpoint is not connected" in my logs very often. Any ideas how to fix it?
> Tnxs in advance
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://lists.samba.org/archive/samba/attachments/20050418/305cf457/attachment.bin

More information about the samba mailing list