Angus Robertson - Magenta Systems Ltd wrote: >> Many thanks, today I managed to raise an exception in >> CommandPASV(), "port in use". The port table reported the port as >> free, although >> the server actually was listening on that port. I was clicking >> around in multiple FTP clients when that happened. > > The port release code is called from a lot of places in different > circumstances, not really look at it.
I will look at it. > But at least the change to use sequential ports means such in-use > errors will be much rarer, AFAIR, you did not mention in-use error replies sent by the server. Most likely this just works around a buggy router/firewall that caused the winsock 10061/10060 errors. If so, your fix should work as long as the passive port range is large enough and more than one free port would be available at any time. > it is the normal windows behaviour to use > sequential ports, not the same one repeatedly. However you also mentioned that the server got out of sequence which may not happen, this should be investigated/fixed as well. I tried to reproduce this behaviour yesterday in vain. I quoted PASV then went on with all kind of commands but the server handled them correctly. Arno > > Angus -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
