I am running Samba on a FreeBSD 5.4 system. Up until today, it had been running successfully. Unfortunately, I just updated it to version "3.0.21b,1" and I think that was a mistake. I have two WinXP machines networked with the FreeBSD machine. When the FreeBSD machine comes online now, I am greeted with this message: ges@seibercom ~ $ Feb 24 15:02:04 seibercom nmbd[662]: [2006/02/24 15:02:04, 0] nmbd/nmbd_become_lmb.c:become_local_master_stage2(396) Feb 24 15:02:04 seibercom nmbd[662]: ***** Feb 24 15:02:04 seibercom nmbd[662]: Feb 24 15:02:04 seibercom nmbd[662]: Samba name server SEIBERCOM is now a loca l master browser for workgroup WORKGROUP on subnet 192.168.0.2 Feb 24 15:02:04 seibercom nmbd[662]: Feb 24 15:02:04 seibercom nmbd[662]: ***** That message was never displayed before. Worse, I cannot access any shares on either of the WinXP boxes from the FreeBSD machine. However, I have total access to the FreeBSD machine from the WinXP machines. The is portion part of the log.smbd file: [2006/02/21 19:37:52, 0] smbd/server.c:main(805) smbd version 3.0.21a started. Copyright Andrew Tridgell and the Samba Team 1992-2005 [2006/02/21 19:37:52, 1] smbd/files.c:file_init(197) file_init: Information only: requested 10000 open files, 5401 are available. [2006/02/22 12:04:44, 0] smbd/server.c:main(805) smbd version 3.0.21b started. Copyright Andrew Tridgell and the Samba Team 1992-2006 [2006/02/22 12:04:44, 1] smbd/files.c:file_init(197) file_init: Information only: requested 10000 open files, 5401 are available. [2006/02/22 21:41:31, 0] smbd/server.c:main(805) smbd version 3.0.21b started. Copyright Andrew Tridgell and the Samba Team 1992-2006 [2006/02/22 21:41:31, 1] smbd/files.c:file_init(197) file_init: Information only: requested 10000 open files, 5401 are available. [2006/02/24 09:29:33, 0] lib/util_sock.c:set_socket_options(261) Failed to set socket option TCP_NODELAY (Error Connection reset by peer) [2006/02/24 09:29:34, 0] lib/util_sock.c:get_peer_addr(1225) getpeername failed. Error was Socket is not connected [2006/02/24 10:01:35, 0] smbd/server.c:open_sockets_smbd(395) open_sockets_smbd: accept: Software caused connection abort [2006/02/24 11:37:38, 0] smbd/server.c:open_sockets_smbd(395) open_sockets_smbd: accept: Software caused connection abort [2006/02/24 15:01:42, 0] smbd/server.c:main(805) smbd version 3.0.21b started. Copyright Andrew Tridgell and the Samba Team 1992-2006 [2006/02/24 15:01:43, 1] smbd/files.c:file_init(197) file_init: Information only: requested 10000 open files, 5401 are available. This is from the log.nmbd log: [2006/02/24 14:59:18, 0] nmbd/nmbd.c:terminate(58) Got SIGTERM: going down... [2006/02/24 15:01:41, 0] nmbd/nmbd.c:main(727) Netbios nameserver version 3.0.21b started. Copyright Andrew Tridgell and the Samba Team 1992-2006 [2006/02/24 15:02:04, 0] nmbd/nmbd_become_lmb.c:become_local_master_stage2(396) ***** Samba name server SEIBERCOM is now a local master browser for workgroup WORKGROUP on subnet 192.168.0.2 ***** Finally, this is from the netbios-name.log file: [2006/02/24 05:13:30, 0] lib/util_sock.c:read_data(529) read_data: read failure for 4 bytes to client 192.168.0.4. Error = Connection reset by peer [2006/02/24 05:45:30, 0] lib/util_sock.c:read_data(529) read_data: read failure for 4 bytes to client 192.168.0.4. Error = Connection reset by peer [2006/02/24 06:17:30, 0] lib/util_sock.c:read_data(529) read_data: read failure for 4 bytes to client 192.168.0.4. Error = Connection reset by peer [2006/02/24 06:49:30, 0] lib/util_sock.c:read_data(529) read_data: read failure for 4 bytes to client 192.168.0.4. Error = Connection reset by peer [2006/02/24 07:21:30, 0] lib/util_sock.c:read_data(529) read_data: read failure for 4 bytes to client 192.168.0.4. Error = Connection reset by peer [2006/02/24 07:53:30, 0] lib/util_sock.c:read_data(529) read_data: read failure for 4 bytes to client 192.168.0.4. Error = Connection reset by peer [2006/02/24 08:25:30, 0] lib/util_sock.c:write_data(557) write_data: write failure in writing to client 192.168.0.4. Error Broken pipe [2006/02/24 08:25:30, 0] lib/util_sock.c:send_smb(765) Error writing 4 bytes to client. -1. (Broken pipe) [2006/02/24 08:57:31, 0] lib/util_sock.c:write_data(557) write_data: write failure in writing to client 192.168.0.4. Error Broken pipe [2006/02/24 08:57:31, 0] lib/util_sock.c:send_smb(765) Error writing 4 bytes to client. -1. (Broken pipe) [2006/02/24 09:29:34, 0] lib/util_sock.c:write_data(557) write_data: write failure in writing to client 192.168.0.4. Error Broken pipe [2006/02/24 09:29:34, 0] lib/util_sock.c:send_smb(765) Error writing 4 bytes to client. -1. (Broken pipe) [2006/02/24 10:33:36, 0] lib/util_sock.c:write_data(557) write_data: write failure in writing to client 192.168.0.4. Error Broken pipe [2006/02/24 10:33:36, 0] lib/util_sock.c:send_smb(765) Error writing 4 bytes to client. -1. (Broken pipe) [2006/02/24 11:05:37, 0] lib/util_sock.c:write_data(557) write_data: write failure in writing to client 192.168.0.4. Error Broken pipe [2006/02/24 11:05:37, 0] lib/util_sock.c:send_smb(765) Error writing 4 bytes to client. -1. (Broken pipe) [2006/02/24 12:41:43, 0] lib/util_sock.c:read_data(529) read_data: read failure for 4 bytes to client 192.168.0.4. Error = Connection reset by peer [2006/02/24 13:13:44, 0] lib/util_sock.c:read_data(529) read_data: read failure for 4 bytes to client 192.168.0.4. Error = Connection reset by peer [2006/02/24 13:45:44, 0] lib/util_sock.c:read_data(529) read_data: read failure for 4 bytes to client 192.168.0.4. Error = Connection reset by peer [2006/02/24 14:17:46, 0] lib/util_sock.c:read_data(529) read_data: read failure for 4 bytes to client 192.168.0.4. Error = Connection reset by peer [2006/02/24 14:29:56, 0] lib/util_sock.c:read_data(529) read_data: read failure for 4 bytes to client 192.168.0.4. Error = Connection reset by peer [2006/02/24 15:07:57, 0] lib/util_sock.c:read_data(529) read_data: read failure for 4 bytes to client 192.168.0.4. Error = Connection reset by peer [2006/02/24 15:10:25, 1] smbd/service.c:make_connection_snum(693) I have no idea why this upgrade is causing this problem. However, if I cannot correct it, I will be forced to downgrade to the older version of Samba. Thanks! -- Gerard Seibert gerard@seibercom.net