samba - Oct 2010 - How can I solve this problem that cause"getpeername failed. Error was Transport endpoint is not connected"

Hello all:

When I was send data between two debian 5.0 system in windows network , I
will get a error message below:

  lib/util_sock.c:read_socket_with_timeout(939)
  lib/util_sock.c:get_peer_addr_internal(1676)
  getpeername failed. Error was Transport endpoint is not connected
  read_socket_with_timeout: client 0.0.0.0 read error = No route to host.

I try insert "smb ports = 139" to solve problem,but it's not
succeed

when boot pc and transport data ,this Error message will happen continue
about one hour 
its only reboot the message is not happen.


OS: Debian 5.0
Samba : 3.2.5

Please help~

Best Regards
-- 
View this message in context:
http://samba.2283325.n4.nabble.com/How-can-I-solve-this-problem-that-cause-getpeername-failed-Error-was-Transport-endpoint-is-not-conne-tp3016636p3016636.html
Sent from the Samba - General mailing list archive at Nabble.com.