[Samba] Samba ver 2.2.2 - socket read - WinXP

[Greg Banschbach - Sandata - 292]

						Jan. 21, 2004

Dear All, 

	I have enjoyed some success with Samba version 2.2.2.  I am using 
it to serve Micro$ Access to end users.  It works very well on a prior 
version of Unix, with older Win2k clients.  Now, with my current version, 
and Win XP Pro, I have problems.  Periodically, they get abruptly kicked out.
I get syslog errors which look like:

kforce-adm-# tail syslog
Jan  7 16:29:09 hforce smbd[29915]: [2004/01/07 16:29:09, 0] lib/util_sock.c:read_socket_data(478)
Jan  7 16:29:09 hforce smbd[29915]:   read_socket_data: recv failure for 4. Error = Connection reset by peer
Jan  7 16:29:50 hforce smbd[14128]: [2004/01/07 16:29:50, 0] lib/util_sock.c:read_socket_data(478)
Jan  7 16:29:50 hforce smbd[14128]:   read_socket_data: recv failure for 4. Error = Connection reset by peer
Jan  7 16:30:44 hforce smbd[3310]: [2004/01/07 16:30:44, 0] lib/util_sock.c:read_socket_data(478)
Jan  7 16:30:44 hforce smbd[3310]:   read_socket_data: recv failure for 4. Error = Connection reset by peer
Jan  7 16:38:43 hforce smbd[2706]: [2004/01/07 16:38:43, 0] lib/util_sock.c:read_socket_data(478)
Jan  7 16:38:43 hforce smbd[2706]:   read_socket_data: recv failure for 4. Error = Connection timed out


And I get log.client entries that look like:
 
kforce-var-# tail log.hfuser6
[2003/12/16 17:26:28, 0] lib/util_sock.c:read_socket_data(478)
  read_socket_data: recv failure for 4. Error = Connection reset by peer
[2003/12/19 15:57:55, 0] smbd/nttrans.c:call_nt_transact_ioctl(1762)
  call_nt_transact_ioctl: Currently not implemented.
[2003/12/19 16:36:14, 0] lib/util_sock.c:read_socket_data(478)
  read_socket_data: recv failure for 4. Error = Connection reset by peer
[2004/01/02 08:31:15, 0] lib/util_sock.c:read_socket_data(478)
  read_socket_data: recv failure for 4. Error = Connection reset by peer
[2004/01/07 16:26:42, 0] lib/util_sock.c:read_socket_data(478)
  read_socket_data: recv failure for 4. Error = Connection reset by peer

kforce-var-# tail log.hfuser3
[2003/12/19 16:36:59, 0] lib/util_sock.c:read_socket_data(478)
  read_socket_data: recv failure for 4. Error = Connection reset by peer
[2004/01/02 08:28:18, 0] lib/util_sock.c:read_socket_data(478)
  read_socket_data: recv failure for 4. Error = Connection reset by peer
[2004/01/07 16:27:45, 0] lib/util_sock.c:read_socket_data(478)
  read_socket_data: recv failure for 4. Error = Connection reset by peer
kforce-var-# tail log.hfuser10
[2004/01/07 16:29:50, 0] lib/util_sock.c:read_socket_data(478)
  read_socket_data: recv failure for 4. Error = Connection reset by peer
kforce-var-#

Is it the WinXP/Access? or is the newer Unix having socket library issues.
My netstat -m output shows no failures. Connecton reset by peer makes me
think Access is the culprit.  The samba config is setup to have very public
folders and no samba passwords - a very fat security hole behind the firewall.
Pobody's nerfect. 8-).   Anyway,  I also saw some code changes related to 
read() versus recv().   I suspect this is not really a bad code issue, when 
I am seeing "connection reset by peer."   Rather, the code might not work so
well with this version of the system libraries?

TIA,

Greg