If it is FTP then it is a known (and unfixed) problem with IIS 5 FTPSVC -
occurs pretty frequently, in my experience, when you upload a huge number of
files.  File size is unimportant, file quantity is.  I can't tell you just
how many is the threshold to the server's "sleepiness", but < 100 per block
seems to get through almost every time.

It's also a 50% probability whether the connection will "wake up" and resume
transfer.  The interesting fact is if your FTP client supports
multi-threaded transfers - different ephemeral ports on your end - you can
invoke a new transfer of files that carries on fine while the original
session is still "sleeping".  Of course your new connection is just as
susceptible.

Perhaps you'll be glad to know that my testing with IIS 6's FTPSVC so far
doesn't exhibit this problem, unlike my previous win2000 Server/IIS 5.


Aaron

----- Original Message -----
From: "Richard Kline" <[EMAIL PROTECTED]>
To: "IIS50 Discussions" <[EMAIL PROTECTED]>
Sent: Thursday, December 12, 2002 19:35
Subject: Re: IIS 5 and frontpage


Not a solution, but perhaps a place to search.  Does Frontpage use FTP to
upload?

I have unexplained sever timeouts from within Dreamweaver (uploading files
via FTP) and standard client/server WS_FTP Pro uploads.   Nothing in the
event logs and Microsoft's support page indicates that the problem was
resolved with... Service Pack 2 (??).  I'm at SP 3 so that appears not to be
entirely accurate.  I've had the problem for several months now (test
machine) but haven't had the incentive (read "time") to further research.

Only difference is that I see the problem with small files as well as big.

Good Luck!

Richard


---
You are currently subscribed to iis50 as: [email protected]
To unsubscribe send a blank email to [EMAIL PROTECTED]

---------
Administrated by 15 Seconds : http://www.15Seconds.com
List Archives/Search : http://local.15Seconds.com/search
Subscription Information : http://www.15seconds.com/listserv.htm
Advertising Information: http://www.internet.com/mediakit/


Reply via email to