🚀 go-pugleaf

"Hugo Dias" <synchron@nospam.synchron-systems.com> wrote in message
news:40f3f2dc@newsgroups.borland.com...

> I need that DATA port be allways the same.
>
> I don't know why, but TIdFTPServer DefaultDataPort
> property doesn't work.

Just saying it doesn't work says nothing at all about the actual problem you
are having.  You need to be more specific.  Are you trying to change the
property to a value different than the default value of 20?  If so, which
version of Indy are you actually using?  If Indy 9, then it appears that the
DefaultDataPort property is not actually hooked up to begin with.


Gambit

Greetings,

Thanks for ansewring. Yes i'm using Indy 9.

I now know that i can solve problem on the client.

I need that the PORT command will be allways : x,x,x,x,207,19 (port 53011)

To do this i've altered the Indy TIdSimpleServer.pas Source code to allways
use this port.

I no this is not a good solution. If you have any idea how i can force the
TIdFTP to use
port 53011 without change Indy source i would apreciate.

Best Reagards,

Hugo Dias

"Hugo Dias" <synchron@nospam.synchron-systems.com> wrote in message
news:40f44d50$1@newsgroups.borland.com...

> I now know that i can solve problem on the client.
>
> I need that the PORT command will be
> allways : x,x,x,x,207,19 (port 53011)
>
> To do this i've altered the Indy TIdSimpleServer.pas
> Source code to allways use this port.

A better solution would be to update TIdFTP to allow assigning custom values
to the TIdSimpleServer's Port property when issuing sPORT commands.
TIdSimpleServer is used in other places of Indy, so you should not mess with
it.  For example (untested):

    TIdFTP = class(TIdTCPClient)
    protected
        //...
        FDefaultDataPort: Integer;
        //...
    published
        //...
        property DefaultDataPort: Integer read FDefaultDataPort write
FDefaultDataPort default 0;
        //...
    end;

    constructor TIdFTP.Create(AOwner: TComponent);
    begin
        //...
        FDefaultDataPort := 0;
    end;

    procedure TIdFTP.InternalGet(const ACommand: string; ADest: TStream;
AResume: Boolean = false);
    begin
        //...
        FDataChannel := TIdSimpleServer.Create(nil); try
            with TIdSimpleServer(FDataChannel) do begin
                //...
                BoundIP := (Self.IOHandler as
TIdIOHandlerSocket).Binding.IP;
                BoundPort := Self.DefaultDataPort;    // <-- here
                BeginListen;
                //...
            end;
        //...
    end;

    procedure TIdFTP.InternalPut(const ACommand: string; ASource: TStream;
AFromBeginning: Boolean = true);
    begin
        //...
        FDataChannel := TIdSimpleServer.Create(nil); try
            with TIdSimpleServer(FDataChannel) do begin
                //...
                BoundIP := (Self.IOHandler as
TIdIOHandlerSocket).Binding.IP;
                BoundPort := Self.DefaultDataPort;    // <-- here
                BeginListen;
                //...
            end;
        //...
    end;

> I no this is not a good solution. If you have any idea
> how i can force the TIdFTP to use port 53011 without
> change Indy source i would apreciate.

Currently, it is not possible without changing Indy's source code.  However,
you simply chose the wrong place to modify, that's all.

Either way, that does not address the original problem that exists in
TIdFTPServer.  That will have to be fixed.


Gambit

"Hugo Dias" <synchron@nospam.synchron-systems.com> wrote in message
news:40f44d50$1@newsgroups.borland.com...

> I no this is not a good solution. If you have any idea
> how i can force the TIdFTP to use port 53011 without
> change Indy source i would apreciate.

I have just now updated Indy 9's snapshot to include a new DefaultDataPort
property in TIdFTP, and hooked up the DefaultDataPort property in
TIdFTPServer.  Please download the latest snapshot of Indy 9 and see if your
problems have been resolved.  If so, then I can see about getting them
incorporated into Indy 10 as well.


Gambit

Thank you very much. Adding DefaultDataPort property to IdFTP solved my
problem.

About the DefaultDataPort on Server, i've dowloaded the latest snapshot, it
seems to me
that it still doesn't work. Or maybe i'm not understading well the
DefaultDataPort concept on
the server.

If the FTP clients allways issues an PORT command when not in PASV mode,
then DataPort
will be allways assigned by the client. Am i missing something ?

Regards,

Hugo Dias

"Hugo Dias" <synchron@nospam.synchron-systems.com> wrote in message
news:40f5b9da@newsgroups.borland.com...

> If the FTP clients allways issues an PORT
> command when not in PASV mode, then
> DataPort will be allways assigned by the client.

That is correct.  However, it will be a port that the client is listening
on, not the server.  The server only listens on ports during PASV
operations.


Gambit