[Samba] Transport endpoint not connected
ed at esson.net
Tue Mar 14 05:36:04 GMT 2006
At 06:21 PM Monday, 3/13/2006, Tom Peters wrote -=>
>Well, I WAS puzzled by this persistent error. Then I stumbled onto
>something and I might have fixed it. It looks like with an XP
>client, XP might be trying to renegotiate which port to talk (445 or
>139) over at the start of every transaction. Whichever one answers
>first is used for the rest of the transfer.
>I added this to smb.conf and restarted samba:
>smb ports = 139
>Someone please toss me a clue or three?
>Contents of samba-log.<xpmachineipaddress>
>[2006/03/13 18:00:30, 1] lib/util_sock.c:get_peer_name(1095)
> Gethostbyaddr failed for 172.20.0.186
>[2006/03/13 18:00:30, 2] lib/access.c:check_access(324)
>[2006/03/13 18:00:30, 0] lib/util_sock.c:get_peer_addr(1136)
> getpeername failed. Error was Transport endpoint is not connected
I went around and around with this issue for months replacing cables,
switches and nics on a couple of machines all to no avail. I played
around with something I found in the archives:
Using iptables to drop port 445, I eliminated the errors. I have not seen
the error return nor experienced any other negative impact on performance.
. . . . . . . . . . . . . . . . . .
Randomly Generated Quote (633 of 1042):
It is better to have loved and lost -- much better.
More information about the samba