> The data-socket must effectively be stopped from "accepting" a > connection once the primary transfer command has failed.
I found your change made no difference to the issue of the extra response being generated, since it was triggered when the data socket was closed, and it was already open and listening when the RETR command was rejected. I've fixed TFtpServer by adding checks for the Client.PassiveMode flag still being set when the connection is closed, normally it's reset when the data connection is opened. If it's still set, I skip the second response event and closed trigger event, for both STOR and RETR. Angus -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
