Here are me exact steps on.
NOTE: I have set anonymous to write.
PS: Filezilla server works fine.
User (Kester-PC.ICNS.local:(none)): ftp
331 Anonymous login OK, send e-mail as password.
Password:
230 Anonymous user logged in, proceed.
ftp> send c:\myfile.log
522 Network protocol mismatch, use (1)
425 Can't open data connection.
ftp>
---
This email is free from viruses and malware because avast! Antivirus protection is active.
http://www.avast.com
Vote for best question.
Score: 0
# Vote: 0
Date Posted: 19-Nov-2014, at 3:29 AM EST
From: Colin Maharaj
Re: Win FTP cmdline to Indy10 Server on localhost fails to s
Colin wrote:
> Did you do the upload?
I did the checkin, yes. Fulgan runs an automated script every night that
pulls the latest SVN code and zips it up.
> I am looking for your notes in the source for
> the download I just did from fulgan
> I assume it is Indy10_5207.zip.
The latest SVN revision is 5209. Looks like Fulgan pulled the SVN code before
I was finished making changes to it. So either pull the latest SVN code
manually, or wait until tomorrow for Fulgan to catch up.
--
Remy Lebeau (TeamB)
Vote for best answer.
Score: 0
# Vote: 0
Date Posted: 22-Nov-2014, at 1:06 PM EST
From: Remy Lebeau (TeamB)
Re: Win FTP cmdline to Indy10 Server on localhost fails to s
> {quote:title=Remy Lebeau (TeamB) wrote:}{quote}
> > {quote:title=Remy Lebeau (TeamB) wrote:}{quote}
> > But I am have an issue with EPSV and PASV.
>
> Problem solved. It was an issue with my firewall after all. EPSV and PASV transfers work fine. I have checked in updates to Indy.
>
> --
> Remy Lebeau (TeamB)
Thanks much Remy. I suspect this has helped a lot more people than just Colin and myself. Really appreciate your efforts.
Vote for best answer.
Score: 0
# Vote: 0
Date Posted: 22-Nov-2014, at 5:24 AM EST
From: Brian Browne
Re: Win FTP cmdline to Indy10 Server on localhost fails to s
Why I am asking is I see differences in the svn vs the downloaded versions
of the.....
procedure TIdFTPServer.CommandEPSV(ASender: TIdCommand);
routine.
And you may not have labeled the bug change in the source.
(believe me I hate bothering folks on a Saturday :( )
On 22/11/2014 03:14 AM, Remy Lebeau (TeamB) wrote:
>> {quote:title=Remy Lebeau (TeamB) wrote:}{quote}
>> But I am have an issue with EPSV and PASV.
>
> Problem solved. It was an issue with my firewall after all. EPSV and PASV transfers work fine. I have checked in updates to Indy.
>
> --
> Remy Lebeau (TeamB)
>
---
This email is free from viruses and malware because avast! Antivirus protection is active.
http://www.avast.com
Vote for best answer.
Score: 0
# Vote: 0
Date Posted: 22-Nov-2014, at 3:41 AM EST
From: Colin Maharaj
Re: Win FTP cmdline to Indy10 Server on localhost fails to s
Hi,
Did you do the upload?
I am looking for your notes in the source for
the download I just did from fulgan
I assume it is Indy10_5207.zip.
On 22/11/2014 03:14 AM, Remy Lebeau (TeamB) wrote:
>> {quote:title=Remy Lebeau (TeamB) wrote:}{quote}
>> But I am have an issue with EPSV and PASV.
>
> Problem solved. It was an issue with my firewall after all. EPSV and PASV transfers work fine. I have checked in updates to Indy.
>
> --
> Remy Lebeau (TeamB)
>
---
This email is free from viruses and malware because avast! Antivirus protection is active.
http://www.avast.com
Vote for best answer.
Score: 0
# Vote: 0
Date Posted: 22-Nov-2014, at 3:29 AM EST
From: Colin Maharaj
Re: Win FTP cmdline to Indy10 Server on localhost fails to s
wow,
I am really glad you were able to discover and fix this.
Thanks so much.
On 22/11/2014 03:14 AM, Remy Lebeau (TeamB) wrote:
>> {quote:title=Remy Lebeau (TeamB) wrote:}{quote}
>> But I am have an issue with EPSV and PASV.
>
> Problem solved. It was an issue with my firewall after all. EPSV and PASV transfers work fine. I have checked in updates to Indy.
>
> --
> Remy Lebeau (TeamB)
>
---
This email is free from viruses and malware because avast! Antivirus protection is active.
http://www.avast.com
Vote for best answer.
Score: 0
# Vote: 0
Date Posted: 22-Nov-2014, at 2:32 AM EST
From: Colin Maharaj
Re: Win FTP cmdline to Indy10 Server on localhost fails to s
> {quote:title=Remy Lebeau (TeamB) wrote:}{quote}
> But I am have an issue with EPSV and PASV.
Problem solved. It was an issue with my firewall after all. EPSV and PASV transfers work fine. I have checked in updates to Indy.
--
Remy Lebeau (TeamB)
Vote for best answer.
Score: 0
# Vote: 0
Date Posted: 21-Nov-2014, at 11:14 PM EST
From: Remy Lebeau (TeamB)
Re: Win FTP cmdline to Indy10 Server on localhost fails to s
> {quote:title=Remy Lebeau (TeamB) wrote:}{quote}
> The problem is the *client* requesting an IPv6 transfer while connected using
> IPv4. I have no clue if/how to disable that in the client. However, that
> being said, I looked at TIdFTPServer's code, and there is no reason why it
> should be limiting which IP version a transfer can use, it should be able
> to support an IPv6 transfer if the OS supports IPv6 even if the client is
> connected using IPv4. So I will update TIdFTPServer to support that.
Here is some more information.
Microsoft's command-line FTP client (and Filezilla, and probably others, too) attempts to connect to a server using IPv6 if available, otherwise it connects using IPv4 instead. If it connects via IPv6, it uses EPRT/EPSV for transfers, otherwise it uses PORT/PASV instead. I found a bug in TIdFTPServer where if a client connects via IPv6, its EPRT/EPSV handlers think the client is using IPv4 instead. That accounts for the mismatch error, and I have fixed that in my local copy of Indy, and have been able
to get EPRT transfers working.
But I am have an issue with EPSV and PASV. As soon as Indy sends a successful reply to either of those commands, something on my machine (not Indy) is immediately killing the client's command socket. I thought it might be my firewall, but I turned it off and am still having the problem. I will have to check my antivirus next.
As soon as I get EPSV/PASV transfers working, I will check in my changes to Indy's SVN for you.
--
Remy Lebeau (TeamB)
Vote for best answer.
Score: 0
# Vote: 0
Date Posted: 21-Nov-2014, at 9:43 PM EST
From: Remy Lebeau (TeamB)
Re: Win FTP cmdline to Indy10 Server on localhost fails to s
Colin wrote:
> But is it possible to disable the IPv6 'listener'
> or not have IPv6 involved?
The problem is the *client* requesting an IPv6 transfer while connected using
IPv4. I have no clue if/how to disable that in the client. However, that
being said, I looked at TIdFTPServer's code, and there is no reason why it
should be limiting which IP version a transfer can use, it should be able
to support an IPv6 transfer if the OS supports IPv6 even if the client is
connected using IPv4. So I will update TIdFTPServer to support that. Check
back with me in a few days if you don't hear from me before then.
--
Remy Lebeau (TeamB)
Vote for best answer.
Score: 0
# Vote: 0
Date Posted: 19-Nov-2014, at 5:14 PM EST
From: Remy Lebeau (TeamB)
Re: Win FTP cmdline to Indy10 Server on localhost fails to s
Ok, thanks!
But is it possible to disable the IPv6 'listener'
or not have IPv6 involved?
On 19/11/2014 02:50 PM, Remy Lebeau (TeamB) wrote:
> Colin wrote:
>
>> 522 Network protocol mismatch, use (1)
>
> That error means that the client is using an IPv4 socket to connect to the
> server, but is sending an EPRT or EPSV command specifying an IPv6 address
> for the transfer socket. TIdFTPServer currently requires the two sockets
> to use the same IP version.
>
> --
> Remy Lebeau (TeamB)
>
---
This email is free from viruses and malware because avast! Antivirus protection is active.
http://www.avast.com
Mega Search
Sign Up 
