Home › Forums › .NET libraries › Xceed SFTP/FTP for .NET › Client.Disconnect() problem.
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 [AP] .QUIT..
T 2009/09/22 07:08:07.254906 XXX.XXX.XXX.XXX:21 -> XXX.XXX.XXX.XXX:54484 [AP] 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 [AP] .QUIUIT..
T XXX.XXX.XXX.XXX:21 -> XXX.XXX.XXX.XXX:14708 [AP] 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 [AP] 221 Goodbye…
Is there a problem with client.disconnect() method?
Applies to Xceed FTP for .NET. Imported from legacy forums. Posted by too (had 1796 views)
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.
Applies to Xceed FTP for .NET. Imported from legacy forums. Posted by Ghislain (had 1720 views)