Knowledge Base |

# TCP/IP-32 FTP.EXE PUT Command Fails on Some FTP Servers

Article ID: 123208

Article Last Modified on 10/10/2003

APPLIES TO

- Microsoft TCP/IP for Windows for Workgroups 3.11
- Microsoft TCP/IP for Windows for Workgroups 3.11a
- Microsoft Windows for Workgroups 3.11

This article was previously published under Q123208

## SYMPTOMS

Microsoft TCP/IP-32 for Windows for Workgroups includes an FTP client, FTP.EXE. When you use the FTP.EXE PUT command to transfer files to an FTP server the transfer fails. One of the following error messages (or one similar) appears:
426 Connection Closed, transfer aborted.

-or-

Error 146: Connection reset by peer.
After the failed transfer, the resulting file on the FTP server may be smaller than the original file on the client workstation.

## CAUSE

At the end of the file transfer to the FTP server, the TCP/IP-32 client sends a TCP packet with the RST bit set in the CODE field of the TCP header. A packet with the RST bit set requests a Connection Reset, and is normally used to break a TCP connection when an abnormal situation occurs. The effect of this Connection Reset depends on the version of software installed on the FTP server. Some FTP servers will react by aborting the file transfer before completely saving the file. Other FTP servers may save the whole file.

## RESOLUTION

To avoid this problem in the future, obtain TCP/IP-32 for Windows for Workgroups version 3.11b.

## STATUS

Microsoft has confirmed this to be a problem in TCP/IP-32 for Windows for Workgroups version 3.11. This problem was corrected in TCP/IP-32 for Windows for Workgroups version 3.11a.

Additional query words: prodtcp32 3.11 wfw wfwg

Keywords: KB123208