Broken Pipe Errors Samba 3.0.30

rschiavi — Thu, 25 Feb 2010 15:21:54 GMT

We are expierancing some strange things at this site. Clients are windows XP and access files from the Samaba Share. Since they have been upgraded to to new servers and new version of samba, they expierance slowness issues when accessing these files. It is not specific to 1 workstation but all. The errors are below in the log.samba file. We are running HP UNIX 11.23

[2010/02/25 09:14:46, 0] lib/util_sock.c:read_data(533)
read_data: read failure for 4 bytes to client 172.23.80.60. Error = Connection reset by peer
[2010/02/25 09:15:01, 0] lib/util_sock.c:set_socket_options(261)
Failed to set socket option SO_KEEPALIVE (Error Invalid argument)
[2010/02/25 09:15:01, 0] lib/util_sock.c:get_peer_addr(1224)
getpeername failed. Error was Invalid argument
[2010/02/25 09:15:01, 0] lib/util_sock.c:write_data(561)
write_data: write failure in writing to client 172.23.11.72. Error Broken pipe
[2010/02/25 09:15:01, 0] lib/util_sock.c:send_smb(760)
Error writing 4 bytes to client. -1. (Broken pipe)

The smb.conf file is below

global]

netbios name = SERVENAME

workgroup = NAME

hosts allow =

# General settings. Rarly changed.
server string = ImageServer/s
log file = /var/opt/samba/log.samba
log level = 0
max log size = 1000
#socket options = TCP_NODELAY
socket options =
printing = sysv
name resolve order = host

security = SHARE
local master = No
oplocks = No
public = Yes

Any help would be apreciated in resolveing these errors.

Thanks

Re: Broken Pipe Errors Samba 3.0.30

D. Jackson_1 — Thu, 25 Feb 2010 23:07:43 GMT

Make sure all sides network throughput is set to MAX. 1000 or 100FD.

HTH

topic Re: Broken Pipe Errors Samba 3.0.30 in Operating System - HP-UX

Broken Pipe Errors Samba 3.0.30

Re: Broken Pipe Errors Samba 3.0.30