Bug 4766 - WinXP client "specified network name is no longer reachable" during long write session
Summary: WinXP client "specified network name is no longer reachable" during long writ...
Status: RESOLVED INVALID
Alias: None
Product: Samba 3.0
Classification: Unclassified
Component: File Services (show other bugs)
Version: 3.0.25b
Hardware: x64 Linux
: P3 normal
Target Milestone: none
Assignee: Samba Bugzilla Account
QA Contact: Samba QA Contact
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-07-05 15:05 UTC by Serge Pashenkov (mail address dead)
Modified: 2007-07-11 13:51 UTC (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Serge Pashenkov (mail address dead) 2007-07-05 15:05:02 UTC 
Same setup as bug #4763. Two WinXP clients write massive amount of data into defferent directories on the same samba share. After many ours of transfer one of them stops with "specified network name is no longer reachable" messages.

This is samba 3.0.25b with the fix from bug #4763 for long notify responces.

Ethereal captures and log.smbd for the failing client are on ftp://208.69.180.86/samba1
	Logon: softeng@powerfile.com
	Pass: SoftDev

.20 is samba server, .13 is the client. Packet #16134 and on.
Comment 1 Jeremy Allison 2007-07-06 17:14:28 UTC 
Looks like the client is going "deaf" after the WriteX reply at packet 16134. You can see the Linux TCP retransmit going off 200ms later, and subsequently. The client must be missing this reply, as you see it setting the "delete on close" bit  and then closing the file to delete what it thinks is the broken write.

It then sits there doing echo requests (probably from the SMB redirector level in the client). Looks like a Windows TCP stack problem to me...

Jeremy.
Comment 2 Serge Pashenkov (mail address dead) 2007-07-11 13:51:52 UTC 
I agree with the analysis, it looks like nothing smbd could be doing differently. I'll make it INVALID.