Article ID: 927991 - Last Review: January 2, 2007 - Revision: 1.1 A large file download fails when an ISA Server 2006 SOCKS client computer uses passive mode FTP
For more information about the Microsoft Internet Security and Acceleration (ISA) Server 2004 version of this article, click the following article number to view the article in the Microsoft Knowledge Base:
923322
(http://support.microsoft.com/kb/923322/
)
A large file download fails when an ISA Server 2004 SOCKS client computer uses passive mode FTP
On This PageSYMPTOMSWhen a Microsoft Internet Security and Acceleration (ISA) Server 2006 FTP client computer downloads a large file by using passive mode FTP, the download fails if it takes longer than 120 seconds. CAUSE
This problem may occur if the following conditions are true:
RESOLUTIONHow to obtain the hotfixThis issue is fixed in the November 22, 2006 Hotfix Package for ISA Server 2006. For more information, click the following article number to view the article in the Microsoft Knowledge Base:928876
(http://support.microsoft.com/kb/928876/
)
Description of the ISA Server 2006 hotfix package: November 22, 2006 After you install this hotfix, run the following Microsoft Visual Basic script to configure the SOCKS filter idle connection time-out value to an appropriate value. Note To determine the appropriate time-out value, use the following equation: File size / download speed * 1.2 = time-out (seconds) (200 * 8) / 1 * 1.2 = 1920 seconds Note The idle connection time-out setting helps free unused resources so that resource-related issues do not occur. Therefore, we recommend that you do not increase the time-out setting unnecessarily. If you use a time-out setting that is less than the default 120 seconds, you can also create unexpected issues. To change the time-out setting, run the following Visual Basic script on the ISA Server 2006 computer. However, you must install the KB928876 hotfix package before you follow these steps:
To change back to the default time-out value, change the value back to 120 seconds in the script, save the change, and then run the script again. WORKAROUND
To work around this problem, configure the FTP program to send "keep-alive" commands on the FTP control channel. For information about whether the FTP program that you use supports this feature, see the documentation for the FTP program. STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. | Article Translations
|
Back to the top
