Anoying "delayed write failed" popups

[Red Squirrel]

I have a windows XP VM I use for p2p (utorrent and shareaza) and it writes all it's data to a share that is actually hosted by the same server that is hosting that VM. When there's lot of traffic I just get tons of "delayed write fail" errors. It's actually quite annoying because they are all false alarms. If I go check, the files can be accessed fine.

I also get lot of similar utorrent specific errors, but again, I go to check, and the file is accessible.

Here's an example event ID:

Event Type: Warning
Event Source: MRxSmb
Event Category: None
Event ID: 50
Date: 2/7/2010
Time: 10:16:45 PM
User: N/A
Computer: P2P
Description:
{Delayed Write Failed} Windows was unable to save all the data for the file \Device\LanmanRedirector. The data has been lost. This error may be caused by a failure of your computer hardware or network connection. Please try to save this file elsewhere.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 04 00 04 00 02 00 56 00 ......V.
0008: 00 00 00 00 32 00 04 80 ....2..
0010: 00 00 00 00 0c 02 00 c0 .......
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........
0028: 0c 02 00 c0 ...

I think this may be related:

Event Type: Warning
Event Source: Tcpip
Event Category: None
Event ID: 4226
Date: 2/7/2010
Time: 8:44:11 AM
User: N/A
Computer: P2P
Description:
TCP/IP has reached the security limit imposed on the number of concurrent TCP connect attempts.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 00 00 00 00 01 00 54 00 ......T.
0008: 00 00 00 00 82 10 00 80 ....?..?
0010: 01 00 00 00 00 00 00 00 ........
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........

 

[Red Squirrel]

After further research think I figured it out. Turns out XP has a limit of 10 concurrent connections per app. I found this to fix that:

http://www.speedguide.net/read_articles.php?id=1497

It *seems* to have fixed it, but early to tell.

 

[dfnkt]

I've also found that related to this, turning of write caching solves it as well.

http://support.microsoft.com/kb/259716

 

[Nothinman]

After further research think I figured it out. Turns out XP has a limit of 10 concurrent connections per app. I found this to fix that:

http://www.speedguide.net/read_articles.php?id=1497

It *seems* to have fixed it, but early to tell.

No, XP has a limit of 10 half-open TCP connections per-process. Once the TCP 3-way handshake completes a connection isn't part of that 10 any more.