[Samba] Odd Samba behavior

[mjb at SRINC.biz]

Greetings,

Samba 3.0.28a running on Ubuntu 8.3.

I have 2 shares and have them mounted on Windows Vista, Windows XP, 
Windows 2000 Server, and Slackware Linux.  In my syslog, I recieve the 
following:

Nov 26 11:57:54 NAS winbindd[23761]: [2008/11/26 11:57:54, 0] 
lib/util_sock.c:read_socket_with_timeout(497) 
Nov 26 11:57:54 NAS winbindd[23761]:   read_socket_with_timeout: timeout 
read. read error = Connection reset by peer. 
Nov 26 11:57:54 NAS winbindd[23761]: [2008/11/26 11:57:54, 0] 
libsmb/clientgen.c:cli_receive_smb(111) 
Nov 26 11:57:54 NAS winbindd[23761]:   Receiving SMB: Server stopped 
responding 
Nov 26 11:57:54 NAS winbindd[23761]: [2008/11/26 11:57:54, 0] 
rpc_client/cli_pipe.c:rpc_api_pipe(790) 
Nov 26 11:57:54 NAS winbindd[23761]:   rpc_api_pipe: Remote machine 
SERVER-1 pipe \lsarpc fnum 0x8000returned critical error. Error was Read 
error: Connection reset by peer 
Nov 26 12:05:03 NAS smbd[24743]: [2008/11/26 12:05:03, 0] 
lib/util_sock.c:read_data(534) 
Nov 26 12:05:03 NAS smbd[24743]:   read_data: read failure for 4 bytes to 
client 10.0.0.2. Error = Connection reset by peer 
Nov 26 12:15:39 NAS smbd[24750]: [2008/11/26 12:15:39, 0] 
lib/util_sock.c:read_data(534) 
Nov 26 12:15:39 NAS smbd[24750]:   read_data: read failure for 4 bytes to 
client 10.0.0.2. Error = Connection reset by peer 
Nov 26 11:57:54 NAS winbindd[23761]:   Receiving SMB: Server stopped 
responding 
Nov 26 11:57:54 NAS winbindd[23761]: [2008/11/26 11:57:54, 0] 
rpc_client/cli_pipe.c:rpc_api_pipe(790) 
Nov 26 11:57:54 NAS winbindd[23761]:   rpc_api_pipe: Remote machine 
SERVER-1 pipe \lsarpc fnum 0x8000returned critical error. Error was Read 
error: Connection reset by peer 
Nov 26 12:05:03 NAS smbd[24743]: [2008/11/26 12:05:03, 0] 
lib/util_sock.c:read_data(534) 
Nov 26 12:05:03 NAS smbd[24743]:   read_data: read failure for 4 bytes to 
client 10.0.0.2. Error = Connection reset by peer 
Nov 26 12:15:39 NAS smbd[24750]: [2008/11/26 12:15:39, 0] 
lib/util_sock.c:read_data(534) 
Nov 26 12:15:39 NAS smbd[24750]:   read_data: read failure for 4 bytes to 
client 10.0.0.2. Error = Connection reset by peer 
Nov 26 12:27:33 NAS smbd[24756]: [2008/11/26 12:27:33, 0] 
lib/util_sock.c:read_data(534) 
Nov 26 12:27:33 NAS smbd[24756]:   read_data: read failure for 4 bytes to 
client 10.0.0.2. Error = Connection reset by peer 
Nov 26 12:44:55 NAS smbd[24766]: [2008/11/26 12:44:55, 0] 
lib/util_sock.c:read_data(534) 
Nov 26 12:44:55 NAS smbd[24766]:   read_data: read failure for 4 bytes to 
client 10.0.0.2. Error = Connection reset by peer 
Nov 26 12:55:30 NAS smbd[24808]: [2008/11/26 12:55:30, 0] 
lib/util_sock.c:read_data(534) 
Nov 26 12:55:30 NAS smbd[24808]:   read_data: read failure for 4 bytes to 
client 10.0.0.2. Error = Connection reset by peer 
Nov 26 13:06:06 NAS smbd[24813]: [2008/11/26 13:06:06, 0] 
lib/util_sock.c:read_data(534) 
Nov 26 13:06:06 NAS smbd[24813]:   read_data: read failure for 4 bytes to 
client 10.0.0.2. Error = Connection reset by peer 
Nov 26 13:16:42 NAS smbd[24818]: [2008/11/26 13:16:42, 0] 
lib/util_sock.c:read_data(534) 
Nov 26 13:16:42 NAS smbd[24818]:   read_data: read failure for 4 bytes to 
client 10.0.0.2. Error = Connection reset by peer 

The result of these errors is that a share can be working just fine one 
minute, and then become inaccessible the next.  This affects all the 
Windows boxes, and affects the Linux box if I use the smbclient, but 
doesn't seem to be an issue when i use "mount -t smbfs ....", though I 
haven't tested this as thoroughly as I've tested the other methods yet. 
Windows reports an error regarding the network path being invalid.  I've 
rewritten my smb.conf file about 60 times, read every document that 
mentions anything regarding this error.. and I'm fresh out of ideas. 

I'm also experiencing very, very slow transfers TO the NAS via SMB 
(gigabit lan, transfers to the NAS peak at about 5.5mbytes/sec). 

Any help, ideas, thoughts, whatever would be greatly appreciated.

Thanks!
- Matt