This was tried with 2 different servers running ProFTPD 1.3.1:

On two of the servers different error occurs:

this is what I get using ngrep on Linux server #1 with the client.disconnect() from XCeed library 4.0:

 

T 2009/09/22 07:08:07.245982 XXX.XXX.XXX.XXX:54484 -> XXX.XXX.XXX.XXX:21  .QUIT..                                                                                                 

T 2009/09/22 07:08:07.254906 XXX.XXX.XXX.XXX:21 -> XXX.XXX.XXX.XXX:54484   500 .QUIT not understood..   

 

this is what I get using ngrep on Linux server #2 with the client.disconnect() from XCeed library 4.0:

 

T  XXX.XXX.XXX.XXX:14708 ->  XXX.XXX.XXX.XXX:21   .QUIUIT..

T  XXX.XXX.XXX.XXX:21 ->  XXX.XXX.XXX.XXX:14708   500 .QUIUIT not understood..

 

 

And this is what I get when I client.SendCustomCommand(“QUIT”) from XCeed library on both servers:

 

T 2009/09/22 07:16:23.341073  XXX.XXX.XXX.XXX:21 ->  XXX.XXX.XXX.XXX:54564   221 Goodbye...

 

 

Is there a problem with client.disconnect() method?

                                                                          

 

Hi,

actually, the error is not coming from the client.disconnect() method but rather with the server being unable to handle the TelnetInterrupt signal.  Therefore, you should refer to this page : http://doc.xceedsoft.com/products/XceedFileSystem/FTPComponent_FtpClient_properties.html 

You will see a property called SendTelnetInterruptSignal and if this property is set to false before calling disconnect(), you should not have any problem. 

Best regards,

---

Ghislain
Technical Support and software developer
Xceed Software Inc.
Knowledge Base : http://xceed.com/kb/
Update Center : http://xceed.com/updates/
Documentation Center : http://xceed.com/doc/
For everything else, there is Google