hmm. D'oh. write_socket_data error
chris at faredge.com.au
Thu Jan 25 06:38:55 GMT 2001
Unfortunately it appears that my efforts to fix things didn't work...
clients are still getting:
[2001/01/23 03:37:46, 0] lib/util_sock.c:write_socket_data(540)
write_socket_data: write failure. Error = Broken pipe
[2001/01/23 03:37:46, 0] lib/util_sock.c:write_socket(566)
write_socket: Error writing 4 bytes to socket 6: ERRNO = Broken pipe
[2001/01/23 03:37:46, 0] lib/util_sock.c:send_smb(754)
Error writing 4 bytes to client. -1. Exiting
which results in the client being bounced.
How can I make samba less paranoid about doing lookups? Currently it's using
the default, which is host lmhost wins bcast . I ended up adding all of the
ip's and computers to /etc/hosts , without luck. If i ping an IP address:
[root at gene samba]# ping 192.168.0.56
Warning: no SO_TIMESTAMP support, falling back to SIOCGSTAMP
PING 192.168.0.56 (192.168.0.56) from 192.168.0.1 : 56(84) bytes of data.
64 bytes from 192.168.0.56: icmp_seq=0 ttl=128 time=1.757 msec
64 bytes from 192.168.0.56: icmp_seq=1 ttl=128 time=481 usec
whereas pinging on my own network, with some real names & addresses gives:
[root at gemini /public]# ping 188.8.131.52
PING 184.108.40.206 (220.127.116.11) from 18.104.22.168 : 56(84) bytes of
64 bytes from celery.faredge.com.au (22.214.171.124): icmp_seq=0 ttl=128
64 bytes from celery.faredge.com.au (126.96.36.199): icmp_seq=1 ttl=128
A couple of other comments - it doesn't appear to happen to NT clients -
only to windows 9x clients.
We usually use dhcp, and set:
option domain-name "corbettresearch.com.au";
option domain-name-servers 192.168.0.1;
option netbios-name-servers 192.168.0.1;
option netbios-node-type 0x2;
in dhcpd.conf. We map MAC addresses in the file below the global area and
deny unknown hosts. All the computers are successfully being allocated IPs,
and having the WINS server set etc.
security = user
no other NT servers
hosts allow = 192.168.0. 127.
socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
interfaces = eth1
remote announce = 192.168.0
local master = yes
os level = 33
domain master = yes
preferred master = yes
domain logons = yes
# the default order is "host lmhosts wins bcast". "host" means use the unix
; name resolve order = host wins lmhosts bcast
wins support = yes
dns proxy = no
all clients have service packs / security patches
A couple of thoughts - if I'm using samba as a wins server, should I put
wins first here? hosts contains an accurate list of machines, as does
I'm pretty close to trying anything here...
More information about the samba