Select the product you need help with
An FTP session from SUA is terminated in Windows Server 2003 R2 when an FTP client receives the SIGWINCH signalArticle ID: 957501 - View products that this article applies to. On This PageSYMPTOMSOn a Windows Server 2003 R2-based computer, you are running the FTP utility of Subsystem for Unix-based Applications (SUA). When an FTP client receives the SIGWINCH signal while it reads the control session socket from the FTP server, the FTP session is terminated. Additionally, you receive the following error message: 421 Service not available, remote server has closed connection. CAUSEThis problem occurs because the FTP command does not mask the SIGWINCH signal when it reads the FTP control session socket. RESOLUTION A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix. Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: http://support.microsoft.com/contactus/?ws=support Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
(http://support.microsoft.com/contactus/?ws=support)
PrerequisitesTo apply this hotfix, the computer must run Windows Server 2003 R2. Also, SUA must be installed.Restart requirementYou do not have to restart the computer after you apply this hotfix.Hotfix replacement informationThis hotfix does not replace a previously released hotfix.Registry informationTo use this hotfix, you do not have to make any changes to the registry.File informationThe English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.Windows Server 2003 R2, x86-based versionCollapse this table
Windows Server 2003 R2, x64-based versionCollapse this table
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. MORE INFORMATIONMore information about the SIGWINCH signal, visit the following Web site: http://en.wikipedia.org/wiki/SIGWINCH.
http://en.wikipedia.org/wiki/SIGWINCH
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
(http://en.wikipedia.org/wiki/SIGWINCH)
824684
(http://support.microsoft.com/kb/824684/
)
Description of the standard terminology that is used to describe Microsoft software updatesPropertiesArticle ID: 957501 - Last Review: October 8, 2011 - Revision: 2.0 APPLIES TO
|



Back to the top








