<?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; settings</title>
	<atom:link href="https://www.dhcpserver.de/cms/category/ini_file_reference/settings/feed/" rel="self" type="application/rss+xml" />
	<link>https://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>IgnoreRequestedAddress</title>
		<link>https://www.dhcpserver.de/cms/ini_file_reference/settings/ignorerequestedaddress/</link>
		<comments>https://www.dhcpserver.de/cms/ini_file_reference/settings/ignorerequestedaddress/#comments</comments>
		<pubDate>Tue, 17 Sep 2024 07:12:33 +0000</pubDate>
		<dc:creator><![CDATA[uwe]]></dc:creator>
				<category><![CDATA[settings]]></category>

		<guid isPermaLink="false">http://www.dhcpserver.de/cms/?p=882</guid>
		<description><![CDATA[Changes how the DHCP Server interprets the requested address submitted from a client. [Settings] IgnoreRequestedAddress=1 ; Default: 0 (don't ignore) If IgnoreRequestedAddress is set to 0 (default): The DHCP server will take the requested address from an unknown client into account when selecting an address to offer, matching the requested address as long as it [&#8230;]]]></description>
				<content:encoded><![CDATA[<p>Changes how the DHCP Server interprets the requested address submitted from a client.</p>
<pre class="textbox">[Settings]
IgnoreRequestedAddress=1        ; Default: 0 (don't ignore)</pre>
<p>If IgnoreRequestedAddress is set to 0 (default): The DHCP server will take the requested address from an unknown client into account when selecting an address to offer, matching the requested address as long as it is free and inside the IP pool.</p>
<div dir="auto">
<p>If IgnoreRequestedAddress is set to 1: The DHCP server will ignore unknown clients suggestion on IP address. Leading to the DHCP server not taking the client request for a specific IP address in account when selection an address to offer the client.</p>
<p>This behavior might not be fully confirmative with the DHCP specification and is not recommended in general usage. But might be useful in special cases.</p>
</div>
<p>This feature was an added in V2.10.0.0.</p>
]]></content:encoded>
			<wfw:commentRss>https://www.dhcpserver.de/cms/ini_file_reference/settings/ignorerequestedaddress/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>BalloonTimeFormat</title>
		<link>https://www.dhcpserver.de/cms/ini_file_reference/settings/balloontimeformat/</link>
		<comments>https://www.dhcpserver.de/cms/ini_file_reference/settings/balloontimeformat/#comments</comments>
		<pubDate>Tue, 01 Mar 2022 06:43:12 +0000</pubDate>
		<dc:creator><![CDATA[uwe]]></dc:creator>
				<category><![CDATA[settings]]></category>

		<guid isPermaLink="false">http://www.dhcpserver.de/cms/?p=750</guid>
		<description><![CDATA[Specifies the time and date format used in balloon messages. The default is %b %d, %H:%M. [Settings] BalloonTimeFormat= ; Default: %b %d, %H:%M This feature was an added in V2.9.2.0. The format supports the following (strftime style) sepcifications: %a Abbreviated weekday name %A Full weekday name %b Abbreviated month name %B Full month name %c [&#8230;]]]></description>
				<content:encoded><![CDATA[<p>Specifies the time and date format used in balloon messages. The default is %b %d, %H:%M.</p>
<pre class="textbox">[Settings]
BalloonTimeFormat=        ; Default: %b %d, %H:%M</pre>
<p>This feature was an added in V2.9.2.0.<br />
The format supports the following (strftime style) sepcifications:</p>
<table>
<tr>
<td>%a</td>
<td>Abbreviated weekday name</td>
</tr>
<tr>
<td>%A</td>
<td>Full weekday name</td>
</tr>
<tr>
<td>%b</td>
<td>Abbreviated month name</td>
</tr>
<tr>
<td>%B</td>
<td>Full month name</td>
</tr>
<tr>
<td>%c</td>
<td>Date and time representation appropriate for locale</td>
</tr>
<tr>
<td>%d</td>
<td>Day of month as decimal number (01 – 31)</td>
</tr>
<tr>
<td>%H</td>
<td>Hour in 24-hour format (00 – 23)</td>
</tr>
<tr>
<td>%I</td>
<td>Hour in 12-hour format (01 – 12)</td>
</tr>
<tr>
<td>%j</td>
<td>Day of year as decimal number (001 – 366)</td>
</tr>
<tr>
<td>%m</td>
<td>Month as decimal number (01 – 12)</td>
</tr>
<tr>
<td>%M</td>
<td>Minute as decimal number (00 – 59)</td>
</tr>
<tr>
<td>%p</td>
<td>Current locale’s A.M./P.M. indicator for 12-hour clock</td>
</tr>
<tr>
<td>%S</td>
<td>Second as decimal number (00 – 59)</td>
</tr>
<tr>
<td>%U</td>
<td>Week of year as decimal number, with Sunday as first day of week (00 – 53)</td>
</tr>
<tr>
<td>%w</td>
<td>Weekday as decimal number (0 – 6; Sunday is 0)</td>
</tr>
<tr>
<td>%W</td>
<td>Week of year as decimal number, with Monday as first day of week (00 – 53)</td>
</tr>
<tr>
<td>%x</td>
<td>Date representation for current locale</td>
</tr>
<tr>
<td>%X</td>
<td>Time representation for current locale</td>
</tr>
<tr>
<td>%y</td>
<td>Year without century, as decimal number (00 – 99)</td>
</tr>
<tr>
<td>%Y</td>
<td>Year with century, as decimal number</td>
</tr>
<tr>
<td>%z, %Z</td>
<td>Time-zone name or abbreviation; no characters if time zone is unknown</td>
</tr>
<tr>
<td>%%</td>
<td>Percent sign</td>
</tr>
</table>
<p>Specify an empty BalloonTimeFormat=, in case no timestamp shall be shown in the balloon message.</p>
]]></content:encoded>
			<wfw:commentRss>https://www.dhcpserver.de/cms/ini_file_reference/settings/balloontimeformat/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>SyncServer</title>
		<link>https://www.dhcpserver.de/cms/ini_file_reference/settings/syncserver/</link>
		<comments>https://www.dhcpserver.de/cms/ini_file_reference/settings/syncserver/#comments</comments>
		<pubDate>Mon, 31 Aug 2020 07:07:49 +0000</pubDate>
		<dc:creator><![CDATA[uwe]]></dc:creator>
				<category><![CDATA[settings]]></category>

		<guid isPermaLink="false">http://www.dhcpserver.de/cms/?p=725</guid>
		<description><![CDATA[Specifies the other DHCP server to load data from. This is a new feature in V2.9 and allows to setup redundant configurations for DNS. The idea is when you setup the split scope redundancy, as described in the FAQ, then you need to handle local DNS requests. See the FAQ for more information. [Settings] SyncServer=other-server:80 ; [&#8230;]]]></description>
				<content:encoded><![CDATA[<p>Specifies the other DHCP server to load data from. This is a new feature in V2.9 and allows to setup redundant configurations for DNS. The idea is when you setup the split scope redundancy, as described in the <a title="How to configure DHCP server for redundancy?" href="http://www.dhcpserver.de/cms/faq/how-to-redundancy/">FAQ</a>, then you need to handle local DNS requests. See the <a title="How to configure DHCP server for redundancy?" href="http://www.dhcpserver.de/cms/faq/how-to-redundancy/">FAQ</a> for more information.</p>
<pre class="textbox">[Settings]
SyncServer=other-server:80  ; load data from other-server</pre>
<p>In order for this to work you need to configure the HTTP function on the other server. IP addresses or names are allowed optionally followed by a colon and the port number of the server.</p>
]]></content:encoded>
			<wfw:commentRss>https://www.dhcpserver.de/cms/ini_file_reference/settings/syncserver/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>ReceiveWindow</title>
		<link>https://www.dhcpserver.de/cms/ini_file_reference/settings/receivewindow/</link>
		<comments>https://www.dhcpserver.de/cms/ini_file_reference/settings/receivewindow/#comments</comments>
		<pubDate>Sat, 16 Nov 2019 07:22:36 +0000</pubDate>
		<dc:creator><![CDATA[uwe]]></dc:creator>
				<category><![CDATA[settings]]></category>

		<guid isPermaLink="false">http://www.dhcpserver.de/cms/?p=688</guid>
		<description><![CDATA[Specifies the size of the windows UDP receive buffer in KBytes. The default is 64, which should be enough to allow 256 clients to request an IP address at the same time. It should only be necessary to change this in very rare cases. [Settings] ReceiveWindow=8 ; Default: 64 [KBytes] This feature was an added in V2.7.]]></description>
				<content:encoded><![CDATA[<p>Specifies the size of the windows UDP receive buffer in KBytes. The default is 64, which should be enough to allow 256 clients to request an IP address at the same time. It should only be necessary to change this in very rare cases.</p>
<pre class="textbox">[Settings]
ReceiveWindow=8        ; Default: 64 [KBytes]</pre>
<p>This feature was an added in V2.7.</p>
]]></content:encoded>
			<wfw:commentRss>https://www.dhcpserver.de/cms/ini_file_reference/settings/receivewindow/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>TraceFileMaxSize</title>
		<link>https://www.dhcpserver.de/cms/ini_file_reference/settings/tracefilemaxsize/</link>
		<comments>https://www.dhcpserver.de/cms/ini_file_reference/settings/tracefilemaxsize/#comments</comments>
		<pubDate>Fri, 27 Oct 2017 05:19:16 +0000</pubDate>
		<dc:creator><![CDATA[uwe]]></dc:creator>
				<category><![CDATA[settings]]></category>

		<guid isPermaLink="false">http://www.dhcpserver.de/cms/?p=664</guid>
		<description><![CDATA[Specifies the maximum size of the trace file (dhcptrc.txt) See also Trace. Once the trace file reached the specified limit in size, it is copied to dhcptrc.bak and a new trace file is created. [Settings] TraceFileMaxSize=256000 ; Default: 128000 This feature was an added in V2.6.0. &#160;]]></description>
				<content:encoded><![CDATA[<p>Specifies the maximum size of the trace file (dhcptrc.txt) See also <a title="Trace" href="http://www.dhcpserver.de/cms/ini_file_reference/settings/trace/">Trace</a>. Once the trace file reached the specified limit in size, it is copied to dhcptrc.bak and a new trace file is created.</p>
<pre class="textbox">[Settings]
TraceFileMaxSize=256000        ; Default: 128000</pre>
<p>This feature was an added in V2.6.0.</p>
<p>&nbsp;</p>
]]></content:encoded>
			<wfw:commentRss>https://www.dhcpserver.de/cms/ini_file_reference/settings/tracefilemaxsize/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>ReadOnly</title>
		<link>https://www.dhcpserver.de/cms/ini_file_reference/settings/readonly/</link>
		<comments>https://www.dhcpserver.de/cms/ini_file_reference/settings/readonly/#comments</comments>
		<pubDate>Fri, 27 Oct 2017 05:16:02 +0000</pubDate>
		<dc:creator><![CDATA[uwe]]></dc:creator>
				<category><![CDATA[settings]]></category>

		<guid isPermaLink="false">http://www.dhcpserver.de/cms/?p=661</guid>
		<description><![CDATA[When ReadOnly is set to 1, then no changes to the INI file will be made by the DHCP server. All newly recognized clients will get an IP address assigned but the respective client entry is not created. Which has the effect that the same IP address will be used next time for another client! [&#8230;]]]></description>
				<content:encoded><![CDATA[<p>When ReadOnly is set to 1, then no changes to the INI file will be made by the DHCP server. All newly recognized clients will get an IP address assigned but the respective client entry is not created. Which has the effect that the same IP address will be used next time for another client! This might be useful for test labs, that test one device after the other and explicitly want to assign the same IP address to each one.</p>
<pre class="textbox">[Settings]
ReadOnly=1        ; Default: 0</pre>
<p>This feature was an added in V2.6.0.</p>
<p>&nbsp;</p>
]]></content:encoded>
			<wfw:commentRss>https://www.dhcpserver.de/cms/ini_file_reference/settings/readonly/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>DeleteClientsFromWrongIndex</title>
		<link>https://www.dhcpserver.de/cms/ini_file_reference/settings/deleteclientsfromwrongindex/</link>
		<comments>https://www.dhcpserver.de/cms/ini_file_reference/settings/deleteclientsfromwrongindex/#comments</comments>
		<pubDate>Fri, 27 Oct 2017 05:10:39 +0000</pubDate>
		<dc:creator><![CDATA[uwe]]></dc:creator>
				<category><![CDATA[settings]]></category>

		<guid isPermaLink="false">http://www.dhcpserver.de/cms/?p=657</guid>
		<description><![CDATA[All newly created clients will get an entry in the client section Index=n where n is the number of the IPBIND_n. If the same client tries to acquire a new IP address but from a different IPBIND_k interface then the software will recognize that n != k meaning the client section is created from a [&#8230;]]]></description>
				<content:encoded><![CDATA[<p>All newly created clients will get an entry in the client section Index=n where n is the number of the IPBIND_n. If the same client tries to acquire a new IP address but from a different IPBIND_k interface then the software will recognize that n != k meaning the client section is created from a different IPBIND. In that situation and when DeleteClientsFromWrongIndex is 1, then DHCP server will delete the client entry and create a new one. Please keep in mind that this will work only, when the client section includes the Index=n entry which is only the case after the client has been acquiring a new lease.</p>
<pre class="textbox">[Settings]
DeleteClientsFromWrongIndex=1        ; Default: 0</pre>
<p>This feature was an added in V2.6.0.</p>
]]></content:encoded>
			<wfw:commentRss>https://www.dhcpserver.de/cms/ini_file_reference/settings/deleteclientsfromwrongindex/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>ReserveByOffer</title>
		<link>https://www.dhcpserver.de/cms/ini_file_reference/settings/reservebyoffer/</link>
		<comments>https://www.dhcpserver.de/cms/ini_file_reference/settings/reservebyoffer/#comments</comments>
		<pubDate>Sun, 13 Sep 2015 08:33:18 +0000</pubDate>
		<dc:creator><![CDATA[uwe]]></dc:creator>
				<category><![CDATA[settings]]></category>

		<guid isPermaLink="false">http://www.dhcpserver.de/cms/?p=607</guid>
		<description><![CDATA[Controls the behavior of the DHCP Server when offering an IP address to the client. In case of ReserveByOffer=1, the client section is written to the INI file with a lease time of 1 second when answering with a DHCPOFFER message. In case of 0, no INI file entry is made at the time of offering [&#8230;]]]></description>
				<content:encoded><![CDATA[<p>Controls the behavior of the DHCP Server when offering an IP address to the client. In case of ReserveByOffer=1, the client section is written to the INI file with a lease time of 1 second when answering with a DHCPOFFER message. In case of 0, no INI file entry is made at the time of offering an IP address. Only the actual assignment (reaction to DHCPREQUEST) of the IP address creates a client section. Of course, the lease time is updated upon assignment to the requested lease time.</p>
<pre class="textbox">[Settings]
ReserveByOffer=0          ; Default: 1</pre>
<p>This was an undocumented feature until V2.5.0.</p>
]]></content:encoded>
			<wfw:commentRss>https://www.dhcpserver.de/cms/ini_file_reference/settings/reservebyoffer/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>VENDORCLASS</title>
		<link>https://www.dhcpserver.de/cms/ini_file_reference/settings/vendorclass/</link>
		<comments>https://www.dhcpserver.de/cms/ini_file_reference/settings/vendorclass/#comments</comments>
		<pubDate>Sat, 06 Sep 2014 16:37:43 +0000</pubDate>
		<dc:creator><![CDATA[uwe]]></dc:creator>
				<category><![CDATA[settings]]></category>

		<guid isPermaLink="false">http://www.dhcpserver.de/cms/?p=184</guid>
		<description><![CDATA[Configure a VENDORCLASS. [Settings] VENDORCLASS=MSFT 5.0 ; Default: - If a VENDORCLASS is specified as an entry in the [Settings] section, then only clients with the same vendor class defined in their DHCP request get an IP address assigned.]]></description>
				<content:encoded><![CDATA[<p>Configure a VENDORCLASS.</p>
<pre class="textbox">[Settings]
VENDORCLASS=MSFT 5.0          ; Default: -</pre>
<p>If a VENDORCLASS is specified as an entry in the [Settings] section, then only clients with the same vendor class defined in their DHCP request get an IP address assigned.</p>
]]></content:encoded>
			<wfw:commentRss>https://www.dhcpserver.de/cms/ini_file_reference/settings/vendorclass/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Trace</title>
		<link>https://www.dhcpserver.de/cms/ini_file_reference/settings/trace/</link>
		<comments>https://www.dhcpserver.de/cms/ini_file_reference/settings/trace/#comments</comments>
		<pubDate>Sat, 06 Sep 2014 16:35:39 +0000</pubDate>
		<dc:creator><![CDATA[uwe]]></dc:creator>
				<category><![CDATA[settings]]></category>

		<guid isPermaLink="false">http://www.dhcpserver.de/cms/?p=182</guid>
		<description><![CDATA[Enabling the Trace. [Settings] Trace=1 ; Default: 0 TraceFile=c:\temp\dhcptrc.txt You can switch the trace on by putting a Trace=1 entry into the [Settings] section. The trace file is called dhcptrc.txt and is written into the same folder as the dhcpsrv.exe and the dhcpsrv.ini files. I recommend to switch the trace on, if you encounter any [&#8230;]]]></description>
				<content:encoded><![CDATA[<p>Enabling the Trace.</p>
<pre class="textbox">[Settings]
Trace=1          ; Default: 0
TraceFile=c:\temp\dhcptrc.txt</pre>
<p>You can switch the trace on by putting a Trace=1 entry into the [Settings] section. The trace file is called dhcptrc.txt and is written into the same folder as the dhcpsrv.exe and the dhcpsrv.ini files. I recommend to switch the trace on, if you encounter any problems and attach the trace file to the e-mail that you are sending to me to report it. If you want the trace to have a different name (and/or directory) then use TraceFile for that. Example:</p>
<pre class="textbox">[Settings]
Trace=1  ; 1= enable,  0=disable
TraceFile=c:\temp\dhcptrc.txt  ; this is where the trace goes</pre>
<p>If the TraceFile setting in not set then the default is dhcptrc.txt in the dhcpsrv.exe directory. TraceFile is a new feature in V1.5.2. Since V2.7 you may also use a relative path to specifiy the trace file name. Relative paths are interpreted relative to the INI file location.</p>
]]></content:encoded>
			<wfw:commentRss>https://www.dhcpserver.de/cms/ini_file_reference/settings/trace/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
