I think your problem is between your app and IIS FTP.
the timeout is in between the process. Well, the timeout value in the ftp
setting is for connection idle status, say 900 seconds if there's no
activities between client and server. IIS ftp will closed the connection.
I would suggest you try ftp.exe and simulate the upload. do you see any
problem?
most of the time - if a decent ftp client is talking to the ftp server, you
don't see such issue.
set aside of coz the IIS FTP itself is also not up to the standard.
--
Regards,
Bernard Cheah
http://www.iis.net/
http://www.iis-resources.com/
http://msmvps.com/blogs/bernard/
Post by smokehouseDear Bernard
§Ú·Q»¡©ú€£°÷²M·¡
Client·|§Q¥ÎIIS¥DŸ÷°õŠæºô¶¥\¯à
±NÀɮקQ¥ÎIIS¥DŸ÷¶ÇšìFTP¥DŸ÷€W
·|¥X²{ Connection Time out : Connect
³oÓ³]©wȬOŠpŠópºâ©O?
šÒŠp : ¹O®É¬°600¬í
ÁÙ¬O¶¢žm«áTimeOut
ŠpªGTimeOut±Œ«á
ÁÂÁ±z
Cloud
"Bernard Cheah [MVP]" šÓšç¡G
Post by Bernard Cheah [MVP]What's the error msgs ?
I think aspbufferinglimit is for asp response to write to the buffer before
it flush.
this mainly for download or page response.
aspmaxrequestentityallowed is for uploading to asp content size, it also
related to maxrequestentityallowed metabase key.
--
Regards,
Bernard Cheah
http://www.iis.net/
http://www.iis-resources.com/
http://msmvps.com/blogs/bernard/
±zŠn
Š]Š¹°Ñ·Ó·L³nªº€å¥ó¥hקï
%systemroot%\inetsrv\metabase.xml€€šâÓ°ÑŒÆ
AspBufferingLimit="4194304"
AspMaxRequestEntityAllowed="204800"
³£±N€Wzªº°ÑŒÆȧ15MB
Šý¬OŠb¶ÇÀÉ®É
€£œT©w¬O§_¶ÇÀɌƀӊh
ŠpªG±qClientªœ±µ³sFTP«o¬O¥¿±`ªº
·QªŸ¹DIIS³ošâÓ°ÑŒÆȬOŠpŠó¥h§P©w¶Ç°e¶q¹L€j?
ÁÂÁ±z