<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Unable to connect to TFTP server - FOG 0.32]]></title><description><![CDATA[<p dir="auto">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.</p>
<p dir="auto">I then started doing this [url]<a href="http://www.fogproject.org/wiki/index.php/Unable_to_connect_to_TFTP%5B/url%5D" target="_blank" rel="noopener noreferrer nofollow ugc">http://www.fogproject.org/wiki/index.php/Unable_to_connect_to_TFTP[/url]</a> 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.</p>
<p dir="auto">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:</p>
<p dir="auto">root@Sierra:~# ftp localhost<br />
Connected to localhost.<br />
220 (vsFTPd 2.2.2)<br />
Name (localhost:root): fog<br />
331 Please specify the password.<br />
Password:<br />
530 Login incorrect.<br />
Login failed.<br />
ftp&gt;</p>
<p dir="auto">The password is definitely correct as I’ve set it many times using the passwd command.</p>
<p dir="auto">I’ve never changed the IP address of the machine, so the IP address listed in the config files is correct as well.</p>
<p dir="auto">I also noticed that the permissions on my images folder had changed, so I changed them to:<br />
root@Sierra:~# ls -laR /images<br />
/images:<br />
total 16<br />
drwxrwxrwx 4 fog fog 4096 2013-06-10 12:13 .<br />
drwxr-xr-x 24 root root 4096 2013-06-13 09:22 …<br />
drwxrwxrwx 2 fog fog 4096 2013-06-10 12:13 dev<br />
-rwxrwxrwx 1 fog fog 0 2013-06-05 12:27 .mntcheck<br />
drwxrwxrwx 2 fog fog 4096 2013-06-10 12:07 Optiplix390Win7x86</p>
<p dir="auto">/images/dev:<br />
total 8<br />
drwxrwxrwx 2 fog fog 4096 2013-06-10 12:13 .<br />
drwxrwxrwx 4 fog fog 4096 2013-06-10 12:13 …<br />
-rwxrwxrwx 1 fog fog 0 2013-06-05 12:27 .mntcheck</p>
<p dir="auto">/images/Optiplix390Win7x86:<br />
total 8437560<br />
drwxrwxrwx 2 fog fog 4096 2013-06-10 12:07 .<br />
drwxrwxrwx 4 fog fog 4096 2013-06-10 12:13 …<br />
-rwxrwxrwx 1 fog fog 512 2013-06-10 12:07 d1.mbr<br />
-rwxrwxrwx 1 fog fog 8900268 2013-06-10 12:07 d1p1.img<br />
-rwxrwxrwx 1 fog fog 8631143059 2013-06-10 12:13 d1p2.img</p>
<p dir="auto">I 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:<br />
root@Sierra:~# cat /etc/vsftp*</p>
<p dir="auto">This one is /etc/vsftpd.conf<br />
anonymous_enable=NO<br />
local_enable=YES<br />
write_enable=YES<br />
local_umask=022<br />
dirmessage_enable=YES<br />
xferlog_enable=YES<br />
connect_from_port_20=YES<br />
xferlog_std_format=YES<br />
listen=YES<br />
pam_service_name=vsftpd<br />
userlist_enable=NO<br />
tcp_wrappers=YES</p>
<p dir="auto">This one is /etc/vsftpd.conf.fogbackup</p>
<h1>Example config file</h1>
<h1></h1>
<h1>The default compiled in settings are fairly paranoid. This sample file</h1>
<h1>loosens things up a bit, to make the ftp daemon more usable.</h1>
<h1>Please see vsftpd.conf.5 for all compiled in defaults.</h1>
<h1></h1>
<h1>READ THIS: This example file is NOT an exhaustive list of vsftpd options.</h1>
<h1>Please read the vsftpd.conf.5 manual page to get a full idea of vsftpd’s</h1>
<h1>capabilities.</h1>
<h1></h1>
<h1></h1>
<h1>Run standalone? vsftpd can run either from an inetd or as a standalone</h1>
<h1>daemon started from an initscript.</h1>
<p dir="auto">listen=YES</p>
<h1></h1>
<h1>Run standalone with IPv6?</h1>
<h1>Like the listen parameter, except vsftpd will listen on an IPv6 socket</h1>
<h1>instead of an IPv4 one. This parameter and the listen parameter are mutually</h1>
<h1>exclusive.</h1>
<p dir="auto">#listen_ipv6=YES</p>
<h1></h1>
<h1>Allow anonymous FTP? (Disabled by default)</h1>
<p dir="auto">anonymous_enable=NO</p>
<h1></h1>
<h1>Uncomment this to allow local users to log in.</h1>
<p dir="auto">local_enable=YES</p>
<h1></h1>
<h1>Uncomment this to enable any form of FTP write command.</h1>
<p dir="auto">#write_enable=YES</p>
<h1></h1>
<h1>Default umask for local users is 077. You may wish to change this to 022,</h1>
<h1>if your users expect that (022 is used by most other ftpd’s)</h1>
<p dir="auto">#local_umask=022</p>
<h1></h1>
<h1>Uncomment this to allow the anonymous FTP user to upload files. This only</h1>
<h1>has an effect if the above global write enable is activated. Also, you will</h1>
<h1>obviously need to create a directory writable by the FTP user.</h1>
<p dir="auto">#anon_upload_enable=YES</p>
<h1></h1>
<h1>Uncomment this if you want the anonymous FTP user to be able to create</h1>
<h1>new directories.</h1>
<p dir="auto">#anon_mkdir_write_enable=YES</p>
<h1></h1>
<h1>Activate directory messages - messages given to remote users when they</h1>
<h1>go into a certain directory.</h1>
<p dir="auto">dirmessage_enable=YES</p>
<h1></h1>
<h1>If enabled, vsftpd will display directory listings with the time</h1>
<h1>in your local time zone. The default is to display GMT. The</h1>
<h1>times returned by the MDTM FTP command are also affected by this</h1>
<h1>option.</h1>
<p dir="auto">use_localtime=YES</p>
<h1></h1>
<h1>Activate logging of uploads/downloads.</h1>
<p dir="auto">xferlog_enable=YES</p>
<h1></h1>
<h1>Make sure PORT transfer connections originate from port 20 (ftp-data).</h1>
<p dir="auto">connect_from_port_20=YES</p>
<h1></h1>
<h1>If you want, you can arrange for uploaded anonymous files to be owned by</h1>
<h1>a different user. Note! Using “root” for uploaded files is not</h1>
<h1>recommended!</h1>
<p dir="auto">#chown_uploads=YES<br />
#chown_username=whoever</p>
<h1></h1>
<h1>You may override where the log file goes if you like. The default is shown</h1>
<h1>below.</h1>
<p dir="auto">#xferlog_file=/var/log/vsftpd.log</p>
<h1></h1>
<h1>If you want, you can have your log file in standard ftpd xferlog format.</h1>
<h1>Note that the default log file location is /var/log/xferlog in this case.</h1>
<p dir="auto">#xferlog_std_format=YES</p>
<h1></h1>
<h1>You may change the default value for timing out an idle session.</h1>
<p dir="auto">#idle_session_timeout=600</p>
<h1></h1>
<h1>You may change the default value for timing out a data connection.</h1>
<p dir="auto">#data_connection_timeout=120</p>
<h1></h1>
<h1>It is recommended that you define on your system a unique user which the</h1>
<h1>ftp server can use as a totally isolated and unprivileged user.</h1>
<p dir="auto">#nopriv_user=ftpsecure</p>
<h1></h1>
<h1>Enable this and the server will recognise asynchronous ABOR requests. Not</h1>
<h1>recommended for security (the code is non-trivial). Not enabling it,</h1>
<h1>however, may confuse older FTP clients.</h1>
<p dir="auto">#async_abor_enable=YES</p>
<h1></h1>
<h1>By default the server will pretend to allow ASCII mode but in fact ignore</h1>
<h1>the request. Turn on the below options to have the server actually do ASCII</h1>
<h1>mangling on files when in ASCII mode.</h1>
<h1>Beware that on some FTP servers, ASCII support allows a denial of service</h1>
<h1>attack (DoS) via the command “SIZE /big/file” in ASCII mode. vsftpd</h1>
<h1>predicted this attack and has always been safe, reporting the size of the</h1>
<h1>raw file.</h1>
<h1>ASCII mangling is a horrible feature of the protocol.</h1>
<p dir="auto">#ascii_upload_enable=YES<br />
#ascii_download_enable=YES</p>
<h1></h1>
<h1>You may fully customise the login banner string:</h1>
<p dir="auto">#ftpd_banner=Welcome to blah FTP service.</p>
<h1></h1>
<h1>You may specify a file of disallowed anonymous e-mail addresses. Apparently</h1>
<h1>useful for combatting certain DoS attacks.</h1>
<p dir="auto">#deny_email_enable=YES</p>
<h1>(default follows)</h1>
<p dir="auto">#banned_email_file=/etc/vsftpd.banned_emails</p>
<h1></h1>
<h1>You may restrict local users to their home directories. See the FAQ for</h1>
<h1>the possible risks in this before using chroot_local_user or</h1>
<h1>chroot_list_enable below.</h1>
<p dir="auto">#chroot_local_user=YES</p>
<h1></h1>
<h1>You may specify an explicit list of local users to chroot() to their home</h1>
<h1>directory. If chroot_local_user is YES, then this list becomes a list of</h1>
<h1>users to NOT chroot().</h1>
<p dir="auto">#chroot_local_user=YES<br />
#chroot_list_enable=YES</p>
<h1>(default follows)</h1>
<p dir="auto">#chroot_list_file=/etc/vsftpd.chroot_list</p>
<h1></h1>
<h1>You may activate the “-R” option to the builtin ls. This is disabled by</h1>
<h1>default to avoid remote users being able to cause excessive I/O on large</h1>
<h1>sites. However, some broken FTP clients such as “ncftp” and “mirror” assume</h1>
<h1>the presence of the “-R” option, so there is a strong case for enabling it.</h1>
<p dir="auto">#ls_recurse_enable=YES</p>
<h1></h1>
<h1>Debian customization</h1>
<h1></h1>
<h1>Some of vsftpd’s settings don’t fit the Debian filesystem layout by</h1>
<h1>default. These settings are more Debian-friendly.</h1>
<h1></h1>
<h1>This option should be the name of a directory which is empty. Also, the</h1>
<h1>directory should not be writable by the ftp user. This directory is used</h1>
<h1>as a secure chroot() jail at times vsftpd does not require filesystem</h1>
<h1>access.</h1>
<p dir="auto">secure_chroot_dir=/var/run/vsftpd/empty</p>
<h1></h1>
<h1>This string is the name of the PAM service vsftpd will use.</h1>
<p dir="auto">pam_service_name=vsftpd</p>
<h1></h1>
<h1>This option specifies the location of the RSA certificate to use for SSL</h1>
<h1>encrypted connections.</h1>
<p dir="auto">rsa_cert_file=/etc/ssl/private/vsftpd.pem</p>
<p dir="auto">What else can I check for?</p>
]]></description><link>http://forums.fogproject.org/topic/1931/unable-to-connect-to-tftp-server-fog-0-32</link><generator>RSS for Node</generator><lastBuildDate>Thu, 16 Apr 2026 01:41:06 GMT</lastBuildDate><atom:link href="http://forums.fogproject.org/topic/1931.rss" rel="self" type="application/rss+xml"/><pubDate>Wed, 19 Jun 2013 15:26:20 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Unable to connect to TFTP server - FOG 0.32 on Wed, 19 Jun 2013 16:26:56 GMT]]></title><description><![CDATA[<p dir="auto">I solved this problem, I had to uninstall likewise-open which I used to authenticate to the server via active directory/ldap.</p>
]]></description><link>http://forums.fogproject.org/post/13183</link><guid isPermaLink="true">http://forums.fogproject.org/post/13183</guid><dc:creator><![CDATA[ninjai]]></dc:creator><pubDate>Wed, 19 Jun 2013 16:26:56 GMT</pubDate></item></channel></rss>