I solved this problem, I had to uninstall likewise-open which I used to authenticate to the server via active directory/ldap.
Latest posts made by ninjai
-
RE: Unable to connect to TFTP server - FOG 0.32
-
Unable to connect to TFTP server - FOG 0.32
The server was working fine until one of the following blew it up: a series of patches and reboots, or likewise-open for active directory authentication.
I then started doing this [url]http://www.fogproject.org/wiki/index.php/Unable_to_connect_to_TFTP[/url] procedure again and ad no luck. Are these passwords supposed to be encrypted with fogcrypt? I didn’t do this, as I thought that was only for AD authentication.
I am unable to FTP to this server as well. I read in another thread you need to have port 20 open as well as 21, but I seem to only be listening on port 21. Could this be my issue? This is what happens when I try to FTP:
root@Sierra:~# ftp localhost
Connected to localhost.
220 (vsFTPd 2.2.2)
Name (localhost:root): fog
331 Please specify the password.
Password:
530 Login incorrect.
Login failed.
ftp>The password is definitely correct as I’ve set it many times using the passwd command.
I’ve never changed the IP address of the machine, so the IP address listed in the config files is correct as well.
I also noticed that the permissions on my images folder had changed, so I changed them to:
root@Sierra:~# ls -laR /images
/images:
total 16
drwxrwxrwx 4 fog fog 4096 2013-06-10 12:13 .
drwxr-xr-x 24 root root 4096 2013-06-13 09:22 …
drwxrwxrwx 2 fog fog 4096 2013-06-10 12:13 dev
-rwxrwxrwx 1 fog fog 0 2013-06-05 12:27 .mntcheck
drwxrwxrwx 2 fog fog 4096 2013-06-10 12:07 Optiplix390Win7x86/images/dev:
total 8
drwxrwxrwx 2 fog fog 4096 2013-06-10 12:13 .
drwxrwxrwx 4 fog fog 4096 2013-06-10 12:13 …
-rwxrwxrwx 1 fog fog 0 2013-06-05 12:27 .mntcheck/images/Optiplix390Win7x86:
total 8437560
drwxrwxrwx 2 fog fog 4096 2013-06-10 12:07 .
drwxrwxrwx 4 fog fog 4096 2013-06-10 12:13 …
-rwxrwxrwx 1 fog fog 512 2013-06-10 12:07 d1.mbr
-rwxrwxrwx 1 fog fog 8900268 2013-06-10 12:07 d1p1.img
-rwxrwxrwx 1 fog fog 8631143059 2013-06-10 12:13 d1p2.imgI found 2 vsftpd.conf files in /etc, I’m unsure if I made the backup file or not, but this is the cat of them:
root@Sierra:~# cat /etc/vsftp*This one is /etc/vsftpd.conf
anonymous_enable=NO
local_enable=YES
write_enable=YES
local_umask=022
dirmessage_enable=YES
xferlog_enable=YES
connect_from_port_20=YES
xferlog_std_format=YES
listen=YES
pam_service_name=vsftpd
userlist_enable=NO
tcp_wrappers=YESThis one is /etc/vsftpd.conf.fogbackup
Example config file
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
capabilities.
Run standalone? vsftpd can run either from an inetd or as a standalone
daemon started from an initscript.
listen=YES
Run standalone with IPv6?
Like the listen parameter, except vsftpd will listen on an IPv6 socket
instead of an IPv4 one. This parameter and the listen parameter are mutually
exclusive.
#listen_ipv6=YES
Allow anonymous FTP? (Disabled by default)
anonymous_enable=NO
Uncomment this to allow local users to log in.
local_enable=YES
Uncomment this to enable any form of FTP write command.
#write_enable=YES
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)
#local_umask=022
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.
#anon_upload_enable=YES
Uncomment this if you want the anonymous FTP user to be able to create
new directories.
#anon_mkdir_write_enable=YES
Activate directory messages - messages given to remote users when they
go into a certain directory.
dirmessage_enable=YES
If enabled, vsftpd will display directory listings with the time
in your local time zone. The default is to display GMT. The
times returned by the MDTM FTP command are also affected by this
option.
use_localtime=YES
Activate logging of uploads/downloads.
xferlog_enable=YES
Make sure PORT transfer connections originate from port 20 (ftp-data).
connect_from_port_20=YES
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
recommended!
#chown_uploads=YES
#chown_username=whoeverYou may override where the log file goes if you like. The default is shown
below.
#xferlog_file=/var/log/vsftpd.log
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.
#xferlog_std_format=YES
You may change the default value for timing out an idle session.
#idle_session_timeout=600
You may change the default value for timing out a data connection.
#data_connection_timeout=120
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.
#nopriv_user=ftpsecure
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.
#async_abor_enable=YES
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.
#ascii_upload_enable=YES
#ascii_download_enable=YESYou may fully customise the login banner string:
#ftpd_banner=Welcome to blah FTP service.
You may specify a file of disallowed anonymous e-mail addresses. Apparently
useful for combatting certain DoS attacks.
#deny_email_enable=YES
(default follows)
#banned_email_file=/etc/vsftpd.banned_emails
You may restrict local users to their home directories. See the FAQ for
the possible risks in this before using chroot_local_user or
chroot_list_enable below.
#chroot_local_user=YES
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().
#chroot_local_user=YES
#chroot_list_enable=YES(default follows)
#chroot_list_file=/etc/vsftpd.chroot_list
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.
#ls_recurse_enable=YES
Debian customization
Some of vsftpd’s settings don’t fit the Debian filesystem layout by
default. These settings are more Debian-friendly.
This option should be the name of a directory which is empty. Also, the
directory should not be writable by the ftp user. This directory is used
as a secure chroot() jail at times vsftpd does not require filesystem
access.
secure_chroot_dir=/var/run/vsftpd/empty
This string is the name of the PAM service vsftpd will use.
pam_service_name=vsftpd
This option specifies the location of the RSA certificate to use for SSL
encrypted connections.
rsa_cert_file=/etc/ssl/private/vsftpd.pem
What else can I check for?