[Xitami] FTP Data Socket Issue

[Brian {Hamilton Kelly}]

In message <JCEKKKLCIKDJFAMJJNJMCEEBCBAA.rvanroy@woodhouse.com>
   "Rick VanRoy" writes:

> This is a multi-part message in MIME format.

PLEASE don't do this: whilst other recipients of your e-mails /might/
like them to arrivein both plain ASCII and also in pidgin-HTML, the
latter has no place on any mailing list (or newsgroup).

Find the setting in your mailer which says "only send HTML mail to
addressees known to like it" (or whatever the wording).

> When attempting to connect to my FTP server, I can connect up to the welcome
> screen, but the data socket won't connect.  I have shifted my http port base
> to 2030, and that works fine.  That should make the FTP port shift to 2051,
> and the data socket to 2050.  Since the server is behind a NAT router
> firewall, I should only need ports 2110, 2050, and 2051 open on the firewall
> for all of it to work.  Still, I cannot get the data socket to go, even
> using PASV.  I have even set the server to DMZ so all ports were available,
> and it still won't work.  I'm at a loss.  Any Ideas?  I'm running v2.5b6

You seem to be arithmetically challenged.  The WKP (well-known ports) for
HTTP, FTP control, and FTP data are, respectively, 80, 21, and 20.

So if you add 1950 to shift the web server port up to 2030, then the FTP
ports will be at 1971 & 1970, and not at 2051/2050.

So what's 2110?  Aha!  I had misunderstood; you have added an OFFSET of
2030, not "shifted the http port" to 2030.  OK, so the FTP ports ought to
be at 2051/2050 as you say.  This wasn't exactly crystal clear.

Let's clarify: from the outside, anyone can connect to port 2051 and log
in to the ftpd?  You are behind a firewall, yes?  Is the FTP client
computer also behind a firewall?  There are always potentially problems
with the FTP data port if there are two firewalls involved.  In the non-
PASV case, the client will connect to port 20 to PUT data, but will use a
PORT command to tell the server whereabout to connect its port 20 to GET
a file; the client's firewall then needs to open that port, because in
non-passive mode, the server is the initiator of such data transfers.

If, OTOH, one uses PASV, then the server's firewall needs to allow
connections from the client to port 20 from any arbitrary socket for a
GET operation.

I believe you are saying that the FTP data port is not working on GET
(and LIST) operations, true?  To try to localize things, what happens if
you try a PUT operation?

> ------=_NextPart_001_0003_01C4AC89.37063FF0
> Content-Type: text/html;
> 	charset="iso-8859-1"
> Content-Transfer-Encoding: quoted-printable
> 
> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">

[HTML "duplicate" snipped]

> ------=_NextPart_001_0003_01C4AC89.37063FF0--
> 
> ------=_NextPart_000_0002_01C4AC89.37063FF0
> Content-Type: image/gif;
> 	name="TechTool.gif"
> Content-Transfer-Encoding: base64
> Content-ID: <100370721@07102004-1274>
> 
> R0lGODlhQQByAPcAAAAAADMzM2ZmZpmZmcDAwAAAAAAAAAAAAPB0AQBMAE0AAABNABoAAAAMF1AA

[errm, what are these 40-ish lines of rubbish doing here?]


Note to list administrator: I thought the list blocked ALL binary
attachments?  If not, why not?

-- 
Brian {Hamilton Kelly}                                     bhk@dsl.co.uk
   "I don't use Linux. I prefer to use an OS supported by a large multi-
   national vendor, with a good office suite, excellent network/internet
   software and decent hardware support."