Second Call to FtpOpenFile() Without Write Permission Hangs

When a program makes a second FtpOpenFile function call to a file on a File Transfer Protocol (FTP) server, the program may stop responding (hang) if you do not have write permissions to the site.

In this case, a stop command is sent to the server because the file was not completely read. A reply is sent to the client from the server that the stop was successful. However, Wininet.dll does not read the response before the socket is closed. Therefore, when the socket is reopened for writing, the "stop successful" response is still in the buffer. This situation causes the send commands and responses to get out of synchronization. Being out of synchronization causes the client to hang.

A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem. This fix may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next Internet Explorer service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:NOTE: In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The typical support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

The English version of this fix should have the following file attributes or later:

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.