asvetov wrote: > As I already said, other Clients work fine. That is not a beating argument. Most other clients use blocking winsock API, AFAIK only Filezilla uses non-blocking calls. Does it never happen with Filezilla client against ICS FTP server? If so, do you confirm that the ICS server isn't the culprid?
-- Arno Garrels And yes, I can reproduce > all with latest V6 > > ----- Server Protocol > > FtpServer (c) 1998-2008 F. Piette V1.10 > Using: > TWSocket (c) 1996-2007 Francois Piette V6.08 > TFtpServer (c) 1998-2008 F. Piette V1.57 > Winsock: > Version 2.2 > WinSock 2.0 > Running > ! Server started > ! 127.0.0.1=(Not Logged On) connected > < 127.0.0.1=(Not Logged On) USER anonymous >> 127.0.0.1=anonymous [0ms] 331 Password required for anonymous. > < 127.0.0.1=anonymous PASS [EMAIL PROTECTED] > ! 127.0.0.1=anonymous is authenticated > ! 127.0.0.1=anonymous Home Directory: c:\temp\ >> 127.0.0.1=anonymous [16ms] 230 User anonymous logged in. > < 127.0.0.1=anonymous PWD >> 127.0.0.1=anonymous [0ms] 257 "/c:/temp" is current directory. > < 127.0.0.1=anonymous PASV >> 127.0.0.1=anonymous [0ms] 227 Entering Passive Mode (127,0,0,1,82,9). > < 127.0.0.1=anonymous LIST > ! 127.0.0.1=anonymous Directory Listing Path: c:\temp\*.* > drw-rw-rw- 1 ftp ftp 0 Mar 08 14:28 . > drw-rw-rw- 1 ftp ftp 0 Mar 08 14:28 .. > drw-rw-rw- 1 ftp ftp 0 Mar 08 14:28 Dir1 > drw-rw-rw- 1 ftp ftp 0 Mar 08 14:29 Dir2 > >> 127.0.0.1=anonymous [0ms] 150 Opening data connection for directory >> list. > ! 127.0.0.1=anonymous Directory 253bytes sent in 15 seconds > (16bytes/sec) >> 127.0.0.1=anonymous [15031ms] 501 Cannot RETR. Error - Socket is not >> connected (#10057) > ! 127.0.0.1=anonymous Data session closed. Error #10057 > ! 127.0.0.1=anonymous disconnected after 17 secs, total recv 66, > total xmit 454 > > ----- Client Protocol > > Winsock version 2.2 > WinSock 2.0 > Running > Executing Requested Command > < 220-Welcome to my Server > < 220- > < 220 ICS FTP Server ready. > Session Connected, error = 0 >> USER anonymous > < 331 Password required for anonymous. >> PASS [EMAIL PROTECTED] > < 230 User anonymous logged in. > Request 5 Done. > StatusCode = 230 > LastResponse was : '230 User anonymous logged in.' > No error > Command Success > Executing Requested Command >> PWD > < 257 "/c:/temp" is current directory. > Request 32 Done. > StatusCode = 257 > LastResponse was : '257 "/c:/temp" is current directory.' > No error > Directory is "/c:/temp" > Command Success > Executing Requested Command >> PASV > < 227 Entering Passive Mode (127,0,0,1,82,9). >> LIST > < 150 Opening data connection for directory list. > Session Closed, error = 0 > Command Failure > Request 7 Done. > StatusCode = 426 > LastResponse was : '150 Opening data connection for directory list.' > Error = 426 (426 Timeout) > > > 08.03.08, 20:52, "Arno Garrels" <[EMAIL PROTECTED]>: > >> Sounds more like somebody is blocking/intercepting the call >> to Connect? >> BTW: I do not use any real time AV scanners or other background >> security tools, it's my experience that they make more trouble >> than they help. Same applies to personal firewalls. They all >> hook the API function calls as they like. If they do not hook >> correctly the hooked application will fail or even crash. And >> especially Kaspersky is known to do ugly things in their drivers >> (as I read in a nice analysis from some driver-guru on the internet >> a couple of months ago). Unfortunately it's always the poor >> application vendor who is blamed :( >> -- >> Arno Garrels -- 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
