Unable to connect to vsftpd

This isn’t my first vsftpd install, but this is the 1st time I have ever ran into this problem and I have already exhausted the things I know to try and test for. Hoping someone can point out what i forgot/missed.


when trying to connect to the ftp server the error I get is:
Error: Connection timed out
Error: Could not connect to server

so i checked the server:
netstat -a | grep ftp
tcp 0 0 *:ftp : LISTEN

My network insticts said to check the firewall, but it is a hosted server and when I asked they said no firewall is before the device right now. aka it is directly connected to the switch which then goes to border device then to ISP.

The server is running Fedora and I installed vsftpd via: yum install vsftpd (no switches).

the files look like they went to the right place and I am able to run /sbin/service vsftpd restart

/sbin/service vsftpd restart Shutting down vsftpd: OK ] Starting vsftpd for vsftpd: OK ]

Here is the conf file:

[code]# Example config file /etc/vsftpd/vsftpd.conf

The default compiled in settings are fairly paranoid. This sample file

loosens things up a bit, to make the ftp daemon more usable.

Please see vsftpd.conf.5 for all compiled in defaults.

READ THIS: This example file is NOT an exhaustive list of vsftpd options.

Please read the vsftpd.conf.5 manual page to get a full idea of vsftpd’s


Allow anonymous FTP? (Beware - allowed by default if you comment this out).


Uncomment this to allow local users to log in.


Uncomment this to enable any form of FTP write command.


Default umask for local users is 077. You may wish to change this to 022,

if your users expect that (022 is used by most other ftpd’s)


Uncomment this to allow the anonymous FTP user to upload files. This only

has an effect if the above global write enable is activated. Also, you will

obviously need to create a directory writable by the FTP user.


Uncomment this if you want the anonymous FTP user to be able to create

new directories.


Activate directory messages - messages given to remote users when they

go into a certain directory.


Activate logging of uploads/downloads.


Make sure PORT transfer connections originate from port 20 (ftp-data).


If you want, you can arrange for uploaded anonymous files to be owned by

a different user. Note! Using “root” for uploaded files is not



You may override where the log file goes if you like. The default is shown



If you want, you can have your log file in standard ftpd xferlog format.

Note that the default log file location is /var/log/xferlog in this case.


You may change the default value for timing out an idle session.


You may change the default value for timing out a data connection.


It is recommended that you define on your system a unique user which the

ftp server can use as a totally isolated and unprivileged user.


Enable this and the server will recognise asynchronous ABOR requests. Not

recommended for security (the code is non-trivial). Not enabling it,

however, may confuse older FTP clients.


By default the server will pretend to allow ASCII mode but in fact ignore

the request. Turn on the below options to have the server actually do ASCII

mangling on files when in ASCII mode.

Beware that on some FTP servers, ASCII support allows a denial of service

attack (DoS) via the command “SIZE /big/file” in ASCII mode. vsftpd

predicted this attack and has always been safe, reporting the size of the

raw file.

ASCII mangling is a horrible feature of the protocol.


You may fully customise the login banner string:

ftpd_banner=Welcome to HOHA FTP Server.

You may specify a file of disallowed anonymous e-mail addresses. Apparently

useful for combatting certain DoS attacks.


(default follows)


You may specify an explicit list of local users to chroot() to their home

directory. If chroot_local_user is YES, then this list becomes a list of

users to NOT chroot().


(default follows)


You may activate the “-R” option to the builtin ls. This is disabled by

default to avoid remote users being able to cause excessive I/O on large

sites. However, some broken FTP clients such as “ncftp” and “mirror” assume

the presence of the “-R” option, so there is a strong case for enabling it.


When “listen” directive is enabled, vsftpd runs in standalone mode and

listens on IPv4 sockets. This directive cannot be used in conjunction

with the listen_ipv6 directive.


This directive enables listening on IPv6 sockets. To listen on IPv4 and IPv6

sockets, you must run two copies of vsftpd whith two configuration files.

Make sure, that one of the listen options is commented !!




Thanks in advance for the help.

I found the issue is with my iptables. When i did a stop on the service I was able to connect just fine.

I must admit my linux security knowledge is more than a little weak. I thought I had already allowed in/out 20/21.