samba - Apr 2005 - "getpeername failed. Error was Transport endpoint is not connected"

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

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

man, 18.04.2005 kl. 08.58 skrev Guido Lorenzutti:
> 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?
Correct your network problems; make sure that all computers in your
network are reachable and booted.

--Tonni

-- 
Nothing sucksseeds like a pigeon without a beak ...

mail: tonye@billy.demon.nl
http://www.billy.demon.nl
 
They love us, don't they, They feed us, won't they ...