Cl?ment
How about telling us what the invalid parameter was?
Mark Moss
USA
***
Message: 8
Date: Thu, 12 Jul 2018 14:17:27 -0300
From: Cl?ment Doss
To: twsocket@lists.elists.org
Subject: Re: [twsocket] Idle Socket is closed even with KeepAlive
Do you have any software which came from the vendor which works with
this device?
If yes you can use WireShark to sniff the traffic and see what is being
sent to avoid the connection is being closed.
Merijn
On 7/12/2018 13:57, Angus Robertson - Magenta Systems Ltd wrote:
(reply from
(reply from original poster)
Thanks for taking your time to help me!
>> I working on a device communication protocol using TCP with
>> TWSocketServer and TWSocket. (Delphi XE Project)
>> Small description: This device
> Sorry don't understand what you are doing.
>
> Is this two ICS applications
Hello,
I thought I would do some testing with TSslFtpClient (version V8.09).
I downloaded and installed ProVide server
(https://www.provideserver.com/free-trial/) on another computer, setup it up
for normal FTP and it worked for getting a file
Altered the settings to support FTPS Implicit
> I set up the properties and called SslFtpClient1.Receive;
Which does not allow to control anything or make choices about what
server commands to use, or indeed do more than a single file.
You should use ConnectFeat, check the FEAT response for capabilities,
then download your files.
>
> Altered the settings to support FTPS Explicit SSL/TLS, set the
> TSslFtpClient.SslType to sslTypeAuthTls, and getting the file
> worked.
>
> Altered the setting TSslFtpClient.SslType to sslTypeAuthSsl, and
> getting the file failed.
sslTypeAuthTls and sslTypeAuthSsl do the same thing but
Hello,
Thanks for the response Angus.
>You should have done a FEAT command to find out what the server needs.
I set up the properties and called SslFtpClient1.Receive;
>ProtLevel C or P means Clear or Private,
OK, so if P then the control AND data are encrypted.
I assume servers support C
Hello!
I finally found the issue! Of course it was on my side. An invalid
parameter was resetting the idle connection "by design". I just bypassed
that parameter and the communication is working flawlessly!
Thanks for your help!
Clément
On 12/07/2018 10:07, Merijn Bosma wrote:
Do you have
