Router blocks FTP access

I have set up a DSL-G664T router for my home network, consisting
of three computers with fixed IP numbers, running under SuSE 9.2.

Whereas http, smtp, and pop3 work perfectly, I do not manage to
get access to any ftp server, even though I can ping those servers.
Here an example:

| /home/wolfgang 243>ftp -i www.ariannuccia.de
| Connected to www.ariannuccia.de.
| 220 212.72.185.10 FTP server ready
| Name (www.ariannuccia.de:wolfgang): wolfgang
|
| 421 Service not available, remote server timed out. Connection closed
| ftp: Login failed.
| ftp>

Any help would be highly appreciated!

Thanks in advance,
Wolfgang

On 2005-02-07, Wolfgang Mueller <(E-Mail Removed)> wrote:
>| /home/wolfgang 243>ftp -i www.ariannuccia.de
>| Connected to www.ariannuccia.de.
>| 220 212.72.185.10 FTP server ready

It looks like the ftp server is responding. Check if you
have both port 20 and 21 opened.

Davide

--
In 1968 it took the computing power of 2 C-64's to fly a rocket to the moon.
Now, in 1998 it takes the Power of a Pentium 200 to run Microsoft Windows 95.
Something must have gone wrong.

On Mon, 7 Feb 2005 17:20:08 GMT, Davide Bianchi wrote:
>
> On 2005-02-07, Wolfgang Mueller wrote:
> >
> >| /home/wolfgang 243>ftp -i www.ariannuccia.de
> >| Connected to www.ariannuccia.de.
> >| 220 212.72.185.10 FTP server ready
>
> It looks like the ftp server is responding.

Obviously. It even responds to ping without any losses.
Nevertheless, it does not permit me to enter. Che strano...

> Check if you have both port 20 and 21 opened.

As a newby to networking, I need an explanation how to
check the status of ports.

Tante grazie in anticipo,
Wolfgang

Wolfgang Mueller wrote:
> On Mon, 7 Feb 2005 17:20:08 GMT, Davide Bianchi wrote:
>>
>> Check if you have both port 20 and 21 opened.

>
> As a newby to networking, I need an explanation how to
> check the status of ports.

Check your firewall, is it activated? SuSE must have a firewall enabled
by default, check it. Is it blocking ports 20, 21? I don't use SuSE, so
I'm not sure where you check?


--
When you say: "I wrote a program that crashed Windows",
people just stare at you blankly and say: "Hey, I got those
with the system -- for free."
- Linus Torvalds
(remove _eh to email)

On Mon, 07 Feb 2005 20:59:40 GMT, Johnny Bobby Bee wrote:
>
> Mon, 07 Feb 2005 20:02:48 +0100, Wolfgang Mueller wrote:
> >
> > On Mon, 7 Feb 2005 17:20:08 GMT, Davide Bianchi wrote:
> > >
> > > Check if you have both port 20 and 21 opened.
> >
> > As a newby to networking, I need an explanation how to
> > check the status of ports.
>
> Check your firewall, is it activated? SuSE must have a
> firewall enabled by default, [...]

That's correct, but I have disabled it for excluding any possible
trouble that may be caused by it.

But I forgot to mention that all internet services, including ftp,
worked perfectly as long as the computers were connected to the
standard ADSL modem, without router, supplied by Deutsche Telekom.
The trouble with ftp only began with the new combined modem-router
DSL-G664T I have recently installed.

Bye, Wolfgang

On Mon, 07 Feb 2005 17:33:14 +0100, I wrote:
>
> I have set up a DSL-G664T router for my home network, consisting
> of three computers with fixed IP numbers, running under SuSE 9.2.
>
> Whereas http, smtp, and pop3 work perfectly, I do not manage to
> get access to any ftp server, even though I can ping those servers.

First of all thanks to Davide and Johnny for their collaboration.

Meanwhile, I found out the true reason of my problem. It turned
out to be due to the FTP client in use. Having installed and
checked out various FTP clients, I came to the following results:

- Unix standard ftp does not work.
- Nor does lukemftp.
- ncftp works correctly; moreover it is much more comfortable
than the two previously mentioned programs.
- Konqueror does, too; but I don't like it, always preferring
a command line tool.

Thanks again and bye,
Wolfgang

On Wed, 09 Feb 2005 12:41:23 +0100,
Wolfgang Mueller <(E-Mail Removed)> wrote:


>
> Meanwhile, I found out the true reason of my problem. It turned
> out to be due to the FTP client in use. Having installed and
> checked out various FTP clients, I came to the following results:
>
> - Unix standard ftp does not work.
> - Nor does lukemftp.
> - ncftp works correctly; moreover it is much more comfortable
> than the two previously mentioned programs.
> - Konqueror does, too; but I don't like it, always preferring
> a command line tool.
>

Wouldn't that be just the difference between active and passive mode?
Some of the clients default to active mode in which case any firewall
needs to open incomming calls to port 20 from the server. Issuing the
command passive to the standard unix ftp client puts that in passive
mode.

Villy

On Wed, 9 Feb 2005 15:37:01 GMT, Villy Kruse wrote:
>
> On Wed, 9 Feb 2005 12:41:23 +0100, Wolfgang Mueller wrote:
> >
> > Meanwhile, I found out the true reason of my problem. It turned
> > out to be due to the FTP client in use. Having installed and
> > checked out various FTP clients, I came to the following results:
> >
> > - Unix standard ftp does not work.
> > - Nor does lukemftp.
> > - ncftp works correctly; moreover it is much more comfortable
> > than the two previously mentioned programs.
> > - Konqueror does, too; but I don't like it, always preferring
> > a command line tool.
>
> Wouldn't that be just the difference between active and passive mode?

I guessed so, too, initially. But use of the parameter "-p"
for passive mode did not change anything. So, this hypothesis
could not be valid.

Wolfgang

Wolfgang Mueller wrote:

> On Wed, 9 Feb 2005 15:37:01 GMT, Villy Kruse wrote:
> >
> > On Wed, 9 Feb 2005 12:41:23 +0100, Wolfgang Mueller wrote:
> > >
> > > Meanwhile, I found out the true reason of my problem. It turned
> > > out to be due to the FTP client in use. Having installed and
> > > checked out various FTP clients, I came to the following results:
> > >
> > > - Unix standard ftp does not work.
> > > - Nor does lukemftp.
> > > - ncftp works correctly; moreover it is much more comfortable
> > > than the two previously mentioned programs.
> > > - Konqueror does, too; but I don't like it, always preferring
> > > a command line tool.
> >
> > Wouldn't that be just the difference between active and passive mode?
>
> I guessed so, too, initially. But use of the parameter "-p"
> for passive mode did not change anything. So, this hypothesis
> could not be valid.

I notice ncftp doesn't set tos bits but ftp does - maybe this is the reason.

If you have iptables on the box you are testing from you could try with the
others after doing -

iptables -A POSTROUTING -t mangle -j DSCP --set-dscp 0x0

Andy.

On Wed, 9 Feb 2005 22:32:53 +0000, Andy Furniss wrote:
>
> I notice ncftp doesn't set tos bits but ftp does - maybe
> this is the reason.
>
> If you have iptables on the box you are testing from you
> could try with the others after doing -
>
> iptables -A POSTROUTING -t mangle -j DSCP --set-dscp 0x0

Your guess hit exactly, Andy. In fact your iptables statement
immediately made standard ftp work.

Thanks a lot,
Wolfgang