Hi Paul, This is another report I came across that indicates this may be a naming service problem, as you mentioned in your bug description:
http://www.geocrawler.com/archives/3/151/2002/11/150/10253550/ Perhaps we can compare configs. I'm running bind for DNS and have "wins support = yes" on the samba3 pdc to run a WINS server. I was not pushing down through dhcp a WINS server IP or node type (nor was one hard coded in each client), but I just set that and I'll let you know if that makes a difference. Are you setting a WINS server on each client machine or through dhcp ? On Thu, 2003-07-17 at 14:42, Paul Eggleton wrote: > Hi Kristis, > > Kristis Makris wrote on Friday, 18 July 2003 9:19 a.m.: > > [2003/07/17 12:16:06, 0] lib/util_sock.c:get_socket_addr(900) > > getpeername failed. Error was Transport endpoint is not connected > > [2003/07/17 12:16:06, 0] lib/util_sock.c:write_socket_data(388) > > write_socket_data: write failure. Error = Connection reset by peer > > [2003/07/17 12:16:06, 0] lib/util_sock.c:write_socket(412) > > write_socket: Error writing 4 bytes to socket 16: ERRNO = Connection > > reset by peer [2003/07/17 12:16:06, 0] lib/util_sock.c:send_smb(573) > > Error writing 4 bytes to client. -1. (Connection reset by peer) > https://bugzilla.samba.org/show_bug.cgi?id=232 -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba