hmm. D'oh. write_socket_data error

[Grotnes Per Kjetil PBE-SIT]

> [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

I have the same error msgs:

[2001/01/25 10:35:00, 0] lib/util_sock.c:(540)
  write_socket_data: write failure. Error = Broken pipe
[2001/01/25 10:35:44, 0] lib/util_sock.c:(540)
  write_socket_data: write failure. Error = Broken pipe
[2001/01/25 10:36:12, 0] lib/util_sock.c:(540)
  write_socket_data: write failure. Error = Broken pipe

> 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:

Just wondering, why do you think it is the lookups that causes these errors?

> 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:

> I'm pretty close to trying anything here...

I see that you have problems with only 9x clients.  Isnt there an option in explorer for 9x 
clients that takes the network disks 'offline' after a certain amount of time?  Would not this 
cause a "Broken pipe" whenever the disk goes offline after being idle for awhile?

I have been ignoring these error-msgs (even though they are filling up my log.smb) because 
i am running a samba 2.0.7 binary-install and thought it might have todo with some preset 
TCP_KEEPALIVE compile option or something.

If you figure it out I would like to hear what you did.

Regards 
Per Kjetil Grotnes
---
IT-Seksjonen, Plan- og bygningsetaten, Oslo Kommune
Tlf: 22 66 26 61, Fax: 22 66 26 65