ftp server and dyndns

Hi

LAMP, VSFTPD on Ubuntu 7.10

The server hosts several unqualified sites.
The DNS is on DynDNS for 5 of them.
I access the web trough a speedstream router.
Ports 20-21 and 50000-50100 are rerouted to the server.

I want to access the ftp on the server by one of the sites address.

In vsftpd.conf I have:
=====
pasv_promiscuous=yes
pasv_enable=yes
pasv_mis_port=50000
pasv_max_port=50100
pasv_address=asite.selfip.com (was 192.168.2.3)
anonymous_enable=no
local_enable=yes
write_enable=yes
======

Tried with g6ftpserver.com with asite.selfip.com on port 21 leads to :
=======
* About to connect() to asite.selfip.com port 21
* Trying 70.55.139.51... connected
* Connected to nregimbald.selfip.com (70.55.139.51) port 21
* FTP response reading failed
* Closing connection #0
========


if I try with the external IP of the router it works.

What am I missing ?




Thanks

Bill <(E-Mail Removed)> wrote:

> What am I missing ?

Some routers will not allow you to access your internal resources via
your domain name. However, you can access your resources externally
using your domain name.

A fix is to modify the /etc/hosts file on your internal client machine,
and put your fully qualified hostname against the IP address of your
server.

If you want to test externally, you can either go to a friends or
neighbours house and borrow their internet for five minutes, or you can
find an externally hosted shell account to do your tests.

I noticed recently that internet web search engines follow links to the
anonymous ftp server. I don't know what they do there, presumably they
crawl the files for indexable content.

Mark.

--
Mark Hobley
Linux User: #370818 http://markhobley.yi.org/

Hello,

Bill a écrit :
>
> I access the web trough a speedstream router.
> Ports 20-21 and 50000-50100 are rerouted to the server.

Port 20 is used as a source port for outbound (active mode) data
connections, so it should not need to be rerouted.

> pasv_address=asite.selfip.com (was 192.168.2.3)

It the router handles FTP correctly, this option should not be necessary
and could even disrupt the router's operation.

> Tried with g6ftpserver.com with asite.selfip.com on port 21 leads to :
> =======
> * About to connect() to asite.selfip.com port 21
> * Trying 70.55.139.51... connected
> * Connected to nregimbald.selfip.com (70.55.139.51) port 21
> * FTP response reading failed
> * Closing connection #0
> ========
>
> if I try with the external IP of the router it works.

Could it be that asite.selfip.com resolves to the wrong IP address ?

Pascal Hambourg a écrit :
> Hello,
>
> Bill a écrit :
>>
>> I access the web trough a speedstream router.
>> Ports 20-21 and 50000-50100 are rerouted to the server.
>
> Port 20 is used as a source port for outbound (active mode) data
> connections, so it should not need to be rerouted.

Sorry only port 20 is specified in the router's conf

>> pasv_address=asite.selfip.com (was 192.168.2.3)
>
> It the router handles FTP correctly, this option should not be necessary
> and could even disrupt the router's operation.

It's ok on the LAN but on the web I must provide the IP.

>> Tried with g6ftpserver.com with asite.selfip.com on port 21 leads to :
>> =======
>> * About to connect() to asite.selfip.com port 21
>> * Trying 70.55.139.51... connected
>> * Connected to nregimbald.selfip.com (70.55.139.51) port 21
>> * FTP response reading failed
>> * Closing connection #0
>> ========
>>
>> if I try with the external IP of the router it works.
>
> Could it be that asite.selfip.com resolves to the wrong IP address ?

Well the actual external IP is not the same. Why ?
But it says "connected", why is it denying the read operation? The login
I gave is a real one and works locally.

The sites on the server are virtual sites and none is registered, they
only serve as private sites that we can reach when we're out.

See the difference.

logged with the actual IP
> * About to connect() to 70.52.72.145 port 21
> * Trying 70.52.72.145... connected
> * Connected to 70.52.72.145 (70.52.72.145) port 21
> < 220 " Serveur FTP prive, Bienvenue et respectez la propriété d'autrui. !!"
>
>> USER anonymous
> < 331 Please specify the password.
>
>> PASS *****
> < 530 Login incorrect.
> * Access denied: 530
> * Closing connection #0

now with the dyndns domain name
> * About to connect() to nregimbald.selfip.com port 21
> * Trying 70.55.139.51... connected
> * Connected to nregimbald.selfip.com (70.55.139.51) port 21
> * FTP response reading failed
> * Closing connection #0

See the different addresses ? (70.52.72.145 and 70.55.139.51)
Dyndns would give 2 different IPs to access depending on the protocol used ?