Error = Connection time out

[motoslide]

This may be a non-samba network problem, but it's primary symptom is lost of connectivity to SMB shares from a Win-XP box.
We have several PC's which access a common SMB share. One of the PC's continually gets disconnected, or shows remarkably slow response. Here is a snippet of the log file on the SMB server (RH-ES3):

[2006/06/30 13:11:16, 0] lib/util_sock.c:read_socket_data(384)
  read_socket_data: recv failure for 4. Error = Connection timed out
[2006/06/30 13:11:16, 1] smbd/service.c:close_cnum(837)
  pcws148 (192.168.1.148) closed connection to service xfer
[2006/06/30 13:11:16, 1] smbd/service.c:close_cnum(837)
  pcws148 (192.168.1.148) closed connection to service xfer
[2006/06/30 13:12:07, 0] lib/util_sock.c:get_peer_addr(1000)
  getpeername failed. Error was Transport endpoint is not connected
[2006/06/30 13:12:07, 0] lib/util_sock.c:write_socket_data(430)
  write_socket_data: write failure. Error = Connection reset by peer
[2006/06/30 13:12:07, 0] lib/util_sock.c:write_socket(455)
  write_socket: Error writing 4 bytes to socket 22: ERRNO = Connection reset by peer
[2006/06/30 13:12:07, 0] lib/util_sock.c:send_smb(647)
  Error writing 4 bytes to client. -1. (Connection reset by peer)
[2006/06/30 13:12:10, 1] smbd/service.c:make_connection_snum(648)
  pcws148 (192.168.1.148) connect to service xfer initially as user pcuser (uid=515, gid=516) (pid 4785)

This basic pattern repeats in log file all day long, whereas the logfile for the other workstations show minor activity.

Any ideas out there?

"Proof that there is intelligent life in Oregon. Well, Life anyway.

 

[ProbablyDown]

Check the duplex on the Network card. See if it matches the other PC's that work...