[Samba] [Samba Version 3.0.20b-3.4-SUSE]: WinXP-Error writing to share

[Robert Schetterer]

Hi, if it is a bug it is relate to winxp 64 versions,
i had never such problems with suse/samba during all upgrades from first 
samba 3 release up to now
on different servers 32/64 intel  /amd  with mutliple nics
perhaps somthing is allready in bugzilla about win xp 64?
Regards
Beschorner Daniel schrieb:
> We have a similar or same problem with one of our servers after upgrade from
> 3.0.14 to 3.0.21x (incidentally??).
>
> The log shows things like:
>
> write_data: write failure in writing to client 192.168.17.249. Error Broken
> pipe
>
> [2006/03/06 20:46:47, 0] lib/util_sock.c:get_peer_addr(1225)
>   getpeername failed. Error was Transport endpoint is not connected
> [2006/03/06 20:46:47, 0] lib/access.c:check_access(328)
> [2006/03/06 20:46:47, 0] lib/util_sock.c:get_peer_addr(1225)
>   getpeername failed. Error was Transport endpoint is not connected
>   Denied connection from  (0.0.0.0)
> [2006/03/06 20:46:47, 1] smbd/process.c:process_smb(1187)
> [2006/03/06 20:46:47, 0] lib/util_sock.c:get_peer_addr(1225)
>   getpeername failed. Error was Transport endpoint is not connected
>   Connection denied from 0.0.0.0
> [2006/03/06 20:46:47, 0] lib/util_sock.c:write_data(557)
>   write_data: write failure in writing to client 192.168.17.250. Error
> Connection reset by peer
> [2006/03/06 20:46:47, 0] lib/util_sock.c:send_smb(765)
>   Error writing 5 bytes to client. -1. (Connection reset by peer)
>
> Clients are XP x64.
>
> When saving fails the Windows log reports "mrxsmb - delayed write failed".
>
> I still suspect the network hardware (switch? NICs?) to do something wrong,
> but can't Samba take out yet.
>