<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>DHCP Server for Windows &#187; tftp</title>
	<atom:link href="http://www.dhcpserver.de/cms/category/ini_file_reference/tftp/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.dhcpserver.de/cms</link>
	<description></description>
	<lastBuildDate>Fri, 30 Jan 2026 05:36:21 +0000</lastBuildDate>
	<language>en-US</language>
		<sy:updatePeriod>hourly</sy:updatePeriod>
		<sy:updateFrequency>1</sy:updateFrequency>
	<generator>https://wordpress.org/?v=4.0.38</generator>
	<item>
		<title>TransferWindow</title>
		<link>http://www.dhcpserver.de/cms/ini_file_reference/tftp/transferwindow/</link>
		<comments>http://www.dhcpserver.de/cms/ini_file_reference/tftp/transferwindow/#comments</comments>
		<pubDate>Sat, 06 Sep 2014 17:20:25 +0000</pubDate>
		<dc:creator><![CDATA[uwe]]></dc:creator>
				<category><![CDATA[tftp]]></category>

		<guid isPermaLink="false">http://www.dhcpserver.de/cms/?p=209</guid>
		<description><![CDATA[Setting the TFTP Transfer window. [TFTP-Settings] TransferWindow=1 ; Default: 4 The tftp-setting TransferWindow sets the maximum number of tftp data packets that are sent before an acknowledge is received. TFTP protocol standard behavior is achieved by setting TransferWindow=1. The default of 4 should increase TFTP performance by about 50%. In case of problems try to [&#8230;]]]></description>
				<content:encoded><![CDATA[<p>Setting the TFTP Transfer window.</p>
<pre class="textbox">[TFTP-Settings]
TransferWindow=1          ; Default: 4</pre>
<p>The tftp-setting TransferWindow sets the maximum number of tftp data packets that are sent before an acknowledge is received. TFTP protocol standard behavior is achieved by setting TransferWindow=1. The default of 4 should increase TFTP performance by about 50%. In case of problems try to set to 1.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.dhcpserver.de/cms/ini_file_reference/tftp/transferwindow/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Root</title>
		<link>http://www.dhcpserver.de/cms/ini_file_reference/tftp/tftp-root/</link>
		<comments>http://www.dhcpserver.de/cms/ini_file_reference/tftp/tftp-root/#comments</comments>
		<pubDate>Sat, 06 Sep 2014 17:18:29 +0000</pubDate>
		<dc:creator><![CDATA[uwe]]></dc:creator>
				<category><![CDATA[tftp]]></category>

		<guid isPermaLink="false">http://www.dhcpserver.de/cms/?p=207</guid>
		<description><![CDATA[Specifying the root for the TFTP server. [TFTP-Settings] Root=c:\tftproot\ ; Default: - Only files located in or under the given Root path are served by the tftp server. A tftp client request asking for a file x automatically translates to a file access to c:\tftproot\x.]]></description>
				<content:encoded><![CDATA[<p>Specifying the root for the TFTP server.</p>
<pre class="textbox">[TFTP-Settings]
Root=c:\tftproot\          ; Default: -</pre>
<p>Only files located in or under the given Root path are served by the tftp server. A tftp client request asking for a file x automatically translates to a file access to c:\tftproot\x.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.dhcpserver.de/cms/ini_file_reference/tftp/tftp-root/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>WritePermission</title>
		<link>http://www.dhcpserver.de/cms/ini_file_reference/tftp/writepermission/</link>
		<comments>http://www.dhcpserver.de/cms/ini_file_reference/tftp/writepermission/#comments</comments>
		<pubDate>Sat, 06 Sep 2014 17:16:51 +0000</pubDate>
		<dc:creator><![CDATA[uwe]]></dc:creator>
				<category><![CDATA[tftp]]></category>

		<guid isPermaLink="false">http://www.dhcpserver.de/cms/?p=205</guid>
		<description><![CDATA[Allowing the TFTP server to write files. [TFTP-Settings] WritePermission=1 ; Default: 0 If not set or set to 0 WritePermission is not granted. Tftp clients can not write files in this case.]]></description>
				<content:encoded><![CDATA[<p>Allowing the TFTP server to write files.</p>
<pre class="textbox">[TFTP-Settings]
WritePermission=1          ; Default: 0</pre>
<p>If not set or set to 0 WritePermission is not granted. Tftp clients can not write files in this case.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.dhcpserver.de/cms/ini_file_reference/tftp/writepermission/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>PortRange</title>
		<link>http://www.dhcpserver.de/cms/ini_file_reference/tftp/portrange/</link>
		<comments>http://www.dhcpserver.de/cms/ini_file_reference/tftp/portrange/#comments</comments>
		<pubDate>Sat, 06 Sep 2014 17:15:38 +0000</pubDate>
		<dc:creator><![CDATA[uwe]]></dc:creator>
				<category><![CDATA[tftp]]></category>

		<guid isPermaLink="false">http://www.dhcpserver.de/cms/?p=203</guid>
		<description><![CDATA[The PortRange setting defines the ports the TFTP server will use for sending and receiving data. [TFTP-Settings] PortRange=51000-51100 ; Default: AUTO The default is AUTO and specifies that the port numbers are allocated automatically on demand as they are made available by windows sockets (winsock). This can be a problem with firewalls, because the port [&#8230;]]]></description>
				<content:encoded><![CDATA[<p>The PortRange setting defines the ports the TFTP server will use for sending and receiving data.</p>
<pre class="textbox">[TFTP-Settings]
PortRange=51000-51100          ; Default: AUTO</pre>
<p>The default is AUTO and specifies that the port numbers are allocated automatically on demand as they are made available by windows sockets (winsock). This can be a problem with firewalls, because the port numbers can not be explicitly opened in the firewall if they are unknown at configuration time. Therefore it is possible to specify a range of ports like PortRange=51000-51100. This tells the TFTP function to select port numbers out of the given range for sending and receiving data. Please make sure that the specified port numbers are not confilicting with other network services running on the server.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.dhcpserver.de/cms/ini_file_reference/tftp/portrange/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>MaxBlockSize</title>
		<link>http://www.dhcpserver.de/cms/ini_file_reference/tftp/maxblocksize/</link>
		<comments>http://www.dhcpserver.de/cms/ini_file_reference/tftp/maxblocksize/#comments</comments>
		<pubDate>Sat, 06 Sep 2014 17:13:07 +0000</pubDate>
		<dc:creator><![CDATA[uwe]]></dc:creator>
				<category><![CDATA[tftp]]></category>

		<guid isPermaLink="false">http://www.dhcpserver.de/cms/?p=200</guid>
		<description><![CDATA[Controlling the TFTP blksize. [TFTP-Settings] MaxBlockSize=1024 ; Default: - (whatever the client asks for) The tftp protocol allows to negotiate the blksize. This is the number of bytes transfered between client and server in each packet. It has been shown that if the client asks for a blksize that is bigger than the MTU, that [&#8230;]]]></description>
				<content:encoded><![CDATA[<p>Controlling the TFTP blksize.</p>
<pre class="textbox">[TFTP-Settings]
MaxBlockSize=1024          ; Default: - (whatever the client asks for)</pre>
<p>The tftp protocol allows to negotiate the blksize. This is the number of bytes transfered between client and server in each packet. It has been shown that if the client asks for a blksize that is bigger than the MTU, that the tftp communication does not work. Therefore it is since V2.2.3 possible to limit the blksize on the server side. MaxBlockSize should be set to a value between 512 and the MTU.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.dhcpserver.de/cms/ini_file_reference/tftp/maxblocksize/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>EnableTFTP</title>
		<link>http://www.dhcpserver.de/cms/ini_file_reference/tftp/enabletftp/</link>
		<comments>http://www.dhcpserver.de/cms/ini_file_reference/tftp/enabletftp/#comments</comments>
		<pubDate>Sat, 06 Sep 2014 17:11:14 +0000</pubDate>
		<dc:creator><![CDATA[uwe]]></dc:creator>
				<category><![CDATA[tftp]]></category>

		<guid isPermaLink="false">http://www.dhcpserver.de/cms/?p=198</guid>
		<description><![CDATA[Enabling the TFTP function. [TFTP-Settings] EnableTFTP=1 ; Default: 0 EnableTFTP enables the integrated Trivial File Transfer Protocol (TFTP) server functionality of the DHCP Server.]]></description>
				<content:encoded><![CDATA[<p>Enabling the TFTP function.</p>
<pre class="textbox">[TFTP-Settings]
EnableTFTP=1          ; Default: 0</pre>
<p>EnableTFTP enables the integrated Trivial File Transfer Protocol (TFTP) server functionality of the DHCP Server.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.dhcpserver.de/cms/ini_file_reference/tftp/enabletftp/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
