AW: [Samba] smbd errors from "getpeername"

I,ve read that this is normal behavior.
Win XP uses two Ports at the same time (145 and 137???).
It gets a connection on one of them and then drops the second =
connection.
Samba does not recognise this and tries to communicate to the dropped =
port.
Because of this you get this messages.

________________________________

Von: samba-bounces+benjamin.oeltze=3Dfujitsu-siemens.com@lists.samba.org =
im Auftrag von Kevin Duckett
Gesendet: Mo 19.09.2005 17:26
An: Samba
Betreff: [Samba] smbd errors from "getpeername"



I receive the following errors/warnings in this scenario.

- From my Windows XP client, I open Network Places. I then click View
workgroup computers. When the list of computers is displayed into the
window I receive the following messages in /var/log/messages.

Sep 19 09:48:53 lnx04 smbd[3101]: [2005/09/19 09:48:53, 0]
lib/util_sock.c:get_peer_addr(1222)
Sep 19 09:48:53 lnx04 smbd[3101]: getpeername failed. Error was
Transport endpoint is not connected
Sep 19 09:48:53 lnx04 smbd[4314]: [2005/09/19 09:48:53, 0]
lib/util_sock.c:get_peer_addr(1222)
Sep 19 09:48:53 lnx04 smbd[4314]: getpeername failed. Error was
Transport endpoint is not connected
Sep 19 09:48:53 lnx04 smbd[4314]: [2005/09/19 09:48:53, 0]
lib/util_sock.c:get_peer_addr(1222)
Sep 19 09:48:53 lnx04 smbd[4314]: getpeername failed. Error was
Transport endpoint is not connected
Sep 19 09:48:53 lnx04 smbd[4314]: [2005/09/19 09:48:53, 0]
lib/access.c:check_access(328)
Sep 19 09:48:53 lnx04 smbd[4314]: [2005/09/19 09:48:53, 0]
lib/util_sock.c:get_peer_addr(1222)
Sep 19 09:48:53 lnx04 smbd[4314]: getpeername failed. Error was
Transport endpoint is not connected
Sep 19 09:48:53 lnx04 smbd[4314]: Denied connection from (0.0.0.0)
Sep 19 09:48:53 lnx04 smbd[4314]: [2005/09/19 09:48:53, 0]
lib/util_sock.c:get_peer_addr(1222)
Sep 19 09:48:53 lnx04 smbd[4314]: getpeername failed. Error was
Transport endpoint is not connected
Sep 19 09:48:53 lnx04 smbd[4314]: Connection denied from 0.0.0.0
Sep 19 09:48:53 lnx04 smbd[4314]: [2005/09/19 09:48:53, 0]
lib/util_sock.c:write_data(554)
Sep 19 09:48:53 lnx04 smbd[4314]: write_data: write failure in writing
to client 0.0.0.0. Error Connection reset by peer
Sep 19 09:48:53 lnx04 smbd[4314]: [2005/09/19 09:48:53, 0]
lib/util_sock.c:send_smb(762)
Sep 19 09:48:53 lnx04 smbd[4314]: Error writing 5 bytes to client. -1.
(Connection reset by peer)

Next, I close the Network Places window and execute the same steps to
see if the messages come back the second time around. They do not.
However, if I restart the smbd services and do it all over again, they
do.


--
<man-lnx03@comcast.net>

--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba =
<https://pdbvpn1.fujitsu-siemens.com/.../mailman/list=
info/samba>=20


--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba