ProFTPd ... FTP client fails to connect: timeout after client sends 'LIST'
 

Hi,

Having a little trouble getting a remotely accessable instance of ProFTPd. It starts perfectly and runs fine, however when attempted to be accessed from another machine or indeed locally from an FTP client, the client can progress no further than sending LIST. At this point, it times out.

Using ProFTPd 1.2 on Fedora Core 4.

Some snippets from logs files...

/var/log/messages:

[root@ethereal ~]# tail -n 5 /var/log/messages

Jan 1 23:39:31 localhost proftpd[16141]: localhost.localdomain (127.0.0.1[127.0.0.1]) - FTP session opened.

Jan 1 23:39:31 localhost proftpd(pam_unix)[16141]: session opened for user james by (uid=0)

Jan 1 23:39:52 localhost proftpd[16141]: localhost.localdomain (127.0.0.1[127.0.0.1]) - PAM(setcred): System error

Jan 1 23:39:52 localhost proftpd[16141]: localhost.localdomain (127.0.0.1[127.0.0.1]) - PAM(close_session): System error

Jan 1 23:39:52 localhost proftpd[16141]: localhost.localdomain (127.0.0.1[127.0.0.1]) - FTP session closed.


/var/log/secure:

Jan 1 23:39:31 localhost proftpd[16141]: localhost.localdomain (127.0.0.1[127.0.0.1]) - USER james: Login successful.

I've specified the passive port range in the ProFTPd config file as: 60000 - 65535

Any advice you can offer would be most appreciated.

Kind regards,
James

Try setting the FTP client program to connect as active and open port 21 in the firewall or router.
I use gFTP and i had to set my program to connect as "Active", or else it wouldn't work.

...
 

Hi,

Well, that seems to have done the trick. However, it's more of an avoidance than a fix, and it would be nice to know why passive mode doesn't work.

I can live with it, but anyone who might be able to assist with passive mode please offer your advice ^^.

Thanks,
James