if Pos('P', tempFeat) > 0 then
FSupportedExtensions := FSupportedExtensions +
[ftpFeatProtP];
end;
end;
Regards
Graham
On 11/02/2018 21:16, Graham Powell wrote:
Thank you once again for your help. You are indeed correct. A search
on the Internet suggests
Yes please, an account might be useful to have, thank you.
Graham
On 12/02/2018 12:01, Angus Robertson - Magenta Systems Ltd wrote:
The only reason I mentioned it was, as you may remember, my
mission is to connect to a Linux FTP server using AUTH TLS.
Everything is fine except if I select
The only reason I mentioned it was, as you may remember, my mission is
to connect to a Linux FTP server using AUTH TLS. Everything is fine
except if I select "Passive" mode and PROT=Private, I cannot login. I
get SSL handshake errors. They suggested that I should use BLOCK mode in
this
Hopefully the last question on this FTP client.
I see that the component supports MODE S and MODE Z. Is there any way it
can, or will in the future, support MODE B (Block)?
Regards
Graham
On 11/02/2018 21:16, Graham Powell wrote:
Thank you once again for your help. You are indeed correct
Thank you once again for your help. You are indeed correct. A search on
the Internet suggests the timeout could be between 30 and 120 seconds.
When I have finished all my testing, I show you what I have modified in
the SslFtpClient. Just a simple change to the processing of the FEAT
response
ving itself?
I looks like the Data Port is not being freed up.
Any clues?
Graham
On 23/01/2018 20:53, Graham Powell wrote:
First a reply to Nicholas Machand as a reply to your e-mail bounces:
The "KeepAliveSecs" makes no difference.
I have turned off the Windows Firewall - No d
Am I correct in assuming the following:
In Active mode, the Data Port Range is set by the FTP client (if required)
In Passive Mode, the Data Port Range is set by the FTP server (if required)
Regards
Graham
On 23/01/2018 20:53, Graham Powell wrote:
First a reply to Nicholas Machand as a reply
ham
On 23/01/2018 16:00, Jörg Fischer wrote:
Hi,
Am 23.01.2018 um 15:54 schrieb Graham Powell:
I don't think that's the problem as the ICS FTP demo setup I am
currently using for test only has one connection.
Somehow my network or Windows has a data limit for each session.
Send details please..
I don't think that's the problem as the ICS FTP demo setup I am
currently using for test only has one connection.
Somehow my network or Windows has a data limit for each session.
Graham
On 23/01/2018 14:23, Angus Robertson - Magenta Systems Ltd wrote:
Any clues as to whether or not there is
Hello again,
I have been doing more tests to try and find out which end is causing
the problem.
My latest setup is to use the IcsSslFtpTst1 demo program and connect it
to the IcsSslFtpServ1 demo program.
The client demo has been modified to display the number of times I press
the "Get"
1: The PROT issue is indeed irrelevent, but a simple fix at least lets
you know if PROT is supported.
Something like this maybe, so long as ftpFeatProt is added to the set:
if Pos('PROT', Feat) = 1 then begin
if Feat = 'PROT' then
Hold fire on what I said before. I am still in learning mode as this is
all new to me.
I had made a basic assumption that if I set "C" or "P" in the
ftpClient.ProtLevel then that would be enough to be incorporated into
the FTP connect mechanism. However not so is it. I have to manually
execute
I'll contact the server folks as well to see what they are expecting.
Thanks again.
Graham
On 20/12/2017 12:09, Angus Robertson - Magenta Systems Ltd wrote:
Also if I set the PROT to C, both the listAsync and getAsync
responses are encrypted. If PROT is set to P, only the getAsync
response is
Thank you for that. It does appear that the cert and key files are not
required to log in.
Also if I set the PROT to C, both the listAsync and getAsync responses
are encrypted. If PROT is set to P, only the getAsync response is encrypted.
P and C are the only two PROT commands supported by
Hello,
The FTP server I have connected to for years is being upgraded to FTPS
and now requires AuthTls for the connection. I have changed my FtpClient
to SslFtpClient and amazingly enough it all just works. I use the
01cert.pem etc. as example files, verify peer all works, just waiting
for
Yes, I think this is not a simple solution. In the past when I have
created a timer which times out before the network and then FTP.Abort
this caused me a problem with messages like "Component Not Ready", until
the whole thing had completed. So I have just left it all in its default
state.
OK, thanks for your help.
Graham
On 17/11/2017 17:26, Angus Robertson - Magenta Systems Ltd wrote:
If I try and connect to a FTP server and that computer isn't even
switch on, the FTP client gives up after about 25 seconds. Is
this timeout goverened by the FTP component or by something
deeper
Hello,
If I try and connect to a FTP server and that computer isn't even switch
on, the FTP client gives up after about 25 seconds. Is this timeout
goverened by the FTP component or by something deeper down in Windows
networking. I was just wondering if I could shorten this timeout period.
I have a user who wants to change the FTP Port number to something like
14581. At the client end of the operation, is this just a case of changing:
Ftp1.Port := 21;
To
Ftp1.Port := 14581
Or is there some gotcha I am not aware of.
Regards
Graham
--
To unsubscribe or change your settings
Well that may be a further problem. When the error occurs the FTP is shut
down and a reconnection is made to a backup server. What I am trying to
determine is why the FTP is coming up with an error in the first place. The
complete mechanism is a bit more complicated in that there are actually two
I am starting to get users who want to step up the security of the FTP
connection and are tending towards SFTP (S being Secure and not Simple in
this case) rather than FTPS. Simplicity of getting though firewalls seems to
be a consideration. I see that ICS now has a suite of SSL components, but is
Thanks for your help. You are correct in that in this case it would be
Windows clients connecting to a Linux server.
If I produce anything useful in the future regarding this, I'll let you
know.
Regards
Graham
-Original Message-
From: TWSocket [mailto:twsocket-boun...@lists.elists.org]
computer systems?
I have an implementation using TWSocketServer and TWSocket and may be able
to help.
Robert
-Original Message-
From: TWSocket [mailto:twsocket-boun...@lists.elists.org] On Behalf Of
Graham Powell
Sent: Wednesday, 16 October 2013 2:15 AM
To: 'ICS support mailing'
Subject: Re
The 20 seconds is plenty long enough as a timeout and it is configurable by
the user if necessary.
One minor addition to your scheme if I decide to use your component is that
all the data is Unicode (high byte first) to the end tag is actually:
null null / null m null o null s null
Graham
Ok, so what I am trying to establish is that it must be my software that is
causing the problem. There must be some sneaky situation where I am
triggering a new command before the previous one has finished.
So there is definitely no way it is either the FTP client component itself
or some network
25 matches
Mail list logo
