FTP routing could be wrong

[sgreyling]

Hi,
I can connect to my HPUX 11.11 with ftp command line but cannot with a client example Filezilla.
We changed office locations and got new IP addresses to connect to our servers. The IP on the servers itself did not change, we only got new IP's to connect to our servers which is NAT to external IP's.
Server IP: 196.38.104.54
PC IP: 10.101.132.200
IP connecting from PC to server: 10.207.1.50
Is this maybe a routing problem that I cannot connect with a client?

[Steven E. Protter]

Shalom,

More likely since command line ftp is working, it is a problem with the settings in the filezilla client.

There are a number of options for ftp and authentication, and if any of them are wrong you will not connect.

If you have server access:

tail -f /var/adm/syslog/syslog.log

Try a login see what you see.

netstat -an | grep ":21 "

See if you can find your session.

SEP

[Laurent Menase]

either your server don't know how to join the router or the router to the server

you should take a network trace on server on the router, and on the client

Then identify where messages are lost,

you can also try a ftp from the router to the server.


Depending on your router configuration, it may be also preferable to use passive mode in ftp

[Steven Schweda]

> I can connect to my HPUX 11.11 with ftp
> command line but cannot with a client
> example Filezilla.

"I cannot connect" is not a useful problem
description. It does not say what you did,
nor what happened when you did it.

> Is this maybe a routing problem that I
> cannot connect with a client?

You're joking, right?

[sgreyling]

Hi Shalom,

This is what Im getting, also, just keep in mind our ftp port is setup on hpux to use port 10120 and 10121 for ftp.
We need to connect to our HPUX server with IP 41.0.18.17

Here is my output:
gwsae01:root:/etc # netstat -an |grep 10121
tcp 0 0 196.38.104.54.10121 10.207.1.50.64118 CLOSE_WAIT
tcp 0 0 *.10121 *.* LISTEN

tail -f /var/adm/syslog/syslog.log
Jul 15 14:38:16 gwsae01 ftpd[15244]: FTP LOGIN FROM schalkmac [10.207.1.50], root
Jul 15 14:38:48 gwsae01 ftpd[14018]: FTP session closed

So obviously the connection is getting there. The following is what I get on Filezilla:

Status: Connecting to 41.0.18.17:10121...
Status: Connection established, waiting for welcome message...
Response: 220 gwsae01 FTP server (Version 1.1.214.4(PHNE_38458) Tue Jul 29 07:36:52 GMT 2008) ready.
Command: USER root
Response: 331 Password required for root.
Command: PASS *******
Response: 230 User root logged in.
Status: Connected
Status: Retrieving directory listing...
Command: PWD
Response: 257 "/" is current directory.
Command: TYPE I
Response: 200 Type set to I.
Command: PASV
Response: 227 Entering Passive Mode (196,38,104,54,201,207)
Command: LIST
Error: Connection timed out
Error: Failed to retrieve directory listing

[sgreyling]

Is there anyone that can help me further in this problem?
I will greatly appreciate it.

[Steven Schweda]

> Is there anyone that can help me further in
> this problem?

Perhaps. Perhaps not.

> Jul 15, 2009 12:29:00 GMT 0 pts

> I will greatly appreciate it.

Yeah, that's obvious.

> [...] keep in mind our ftp port is setup on
> hpux to use port 10120 and 10121 for ftp.

It would have been easier to keep it in mind
if you had let it out of yours earlier.

And how, exactly, did you do that?

> I can connect to my HPUX 11.11 with ftp
> command line [...]

> The following is what I get on Filezilla:

And what did you do, and what did you get,
when using the command-line FTP client? (You
may find a "debug" option/command in that FTP
client program, which might provide a
similarly detailed log of the FTP
transactions.)

If one FTP client works but another does not,
then there may be a problem with the one
which does not work.

When I last checked, there was more than one
version of Filezilla available. Should I be
keeping in mind which version you're using,
too? Have you looked for similar bug reports
for Filezilla?


> Command: PWD
> Response: 257 "/" is current directory.
> Command: TYPE I
> Response: 200 Type set to I.

There doesn't seem to be any problem routing
these commands and responses.

[Mel Burslan]

Some routers really dislike pasv ftp mode. Yeah it was a joke but pasv ftp mode had some drawbacks that we have encountered with one of our external business partners which were coming in through a NATed router.

I strongly suggest you engage the network team in charge of the NATing routers and hear what they say. Hopefully you have a CCIE disposable to you as this was not a trivial issue for us but resolved after some extensive research, mostly on the network guys' side. Otherwise, your filezilla client is connecting fine.

Did you try coming in via working command line ftp and at the ftp> prompt switching to pasv mode ? If so, did it start timing out like filezilla or it worked fine over there as well ?

Last but not the least, I know you did not ask this, but try to convince all parties to use scp instead of ftp. Makes life a whole lot easier for you and for scripted file copying.

Hope this helps.

[Patrick Wallek]

Is it possible to turn passive mode OFF in filezilla? If so, try it and then see if it works any better.