<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Windows DHCP Logs in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Windows-DHCP-Logs/m-p/13303#M1165</link>
    <description>&lt;P&gt;I think you have to add more slashes to get this working.&lt;/P&gt;

&lt;P&gt;&lt;CODE&gt;[monitor://C:\Windows\System32\dhcp]&lt;/CODE&gt;&lt;/P&gt;

&lt;P&gt;With the (“\”s added.&lt;/P&gt;</description>
    <pubDate>Sat, 07 Mar 2015 20:06:01 GMT</pubDate>
    <dc:creator>mcronkrite</dc:creator>
    <dc:date>2015-03-07T20:06:01Z</dc:date>
    <item>
      <title>Windows DHCP Logs</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Windows-DHCP-Logs/m-p/13298#M1160</link>
      <description>&lt;P&gt;I am having trouble getting a Splunk forwarder (4.1.2) to send Windows 2008 R2 DHCP logs back to the main Splunk indexer (4.1.2).  When I first setup the forwarder to monitor the DHCP log directory, everything was working fine.  Now it appears that the forwarder does not think there are any new log events to transmit.  Something unique with these logs is that they have names like DhcpSrvLog-Mon.log and DhcpSrvLog-Sat.log.  The logs get overwritten on a weekly basis.  Should Splunk be able to detect that log names are getting reused or do I need to configure an additional setting somewhere? &lt;/P&gt;

&lt;P&gt;Note: All other logs being captured by the forwarder are transmitting correctly.&lt;/P&gt;</description>
      <pubDate>Wed, 12 May 2010 05:18:59 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Windows-DHCP-Logs/m-p/13298#M1160</guid>
      <dc:creator>Justin</dc:creator>
      <dc:date>2010-05-12T05:18:59Z</dc:date>
    </item>
    <item>
      <title>Re: Windows DHCP Logs</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Windows-DHCP-Logs/m-p/13299#M1161</link>
      <description>&lt;P&gt;Do these files happen to have a large identical header at the beginning? Or, are the files possibly written in Unicode/UTF-16 (and Splunk is failing to detect that)?&lt;/P&gt;</description>
      <pubDate>Wed, 12 May 2010 10:38:31 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Windows-DHCP-Logs/m-p/13299#M1161</guid>
      <dc:creator>gkanapathy</dc:creator>
      <dc:date>2010-05-12T10:38:31Z</dc:date>
    </item>
    <item>
      <title>Re: Windows DHCP Logs</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Windows-DHCP-Logs/m-p/13300#M1162</link>
      <description>&lt;P&gt;The log files do have large headers. The header is 31 lines, and the 32nd line is when new log events appear. Is there a conf file setting I need to accommodate this? If so, does this need to be done on the forwarder or indexer?&lt;/P&gt;

&lt;P&gt;I am not sure how to determine if the file has Unicode. Is there an easy way to check this?&lt;/P&gt;</description>
      <pubDate>Thu, 13 May 2010 00:00:33 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Windows-DHCP-Logs/m-p/13300#M1162</guid>
      <dc:creator>Justin</dc:creator>
      <dc:date>2010-05-13T00:00:33Z</dc:date>
    </item>
    <item>
      <title>Re: Windows DHCP Logs</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Windows-DHCP-Logs/m-p/13301#M1163</link>
      <description>&lt;P&gt;I contacted Splunk Enterprise support and they pointed me to a solution.  On the Splunk forwarder system (the one with the DHCP logs), I had to add an entry to inputs.conf in /etc/system/local/.&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[monitor://C:\Windows\System32\dhcp]
sourcetype = dhcp
crcSalt = &amp;lt;SOURCE&amp;gt;
alwaysOpenFile = 1
disabled = false
whitelist = Dhcp.+\.log
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;The key was the "crcSalt" entry.  I hope this helps others.&lt;/P&gt;</description>
      <pubDate>Sat, 05 Jun 2010 01:41:25 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Windows-DHCP-Logs/m-p/13301#M1163</guid>
      <dc:creator>Justin</dc:creator>
      <dc:date>2010-06-05T01:41:25Z</dc:date>
    </item>
    <item>
      <title>Re: Windows DHCP Logs</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Windows-DHCP-Logs/m-p/13302#M1164</link>
      <description>&lt;P&gt;Solved my problem !&lt;/P&gt;</description>
      <pubDate>Thu, 10 Nov 2011 19:38:55 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Windows-DHCP-Logs/m-p/13302#M1164</guid>
      <dc:creator>mgaleti</dc:creator>
      <dc:date>2011-11-10T19:38:55Z</dc:date>
    </item>
    <item>
      <title>Re: Windows DHCP Logs</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Windows-DHCP-Logs/m-p/13303#M1165</link>
      <description>&lt;P&gt;I think you have to add more slashes to get this working.&lt;/P&gt;

&lt;P&gt;&lt;CODE&gt;[monitor://C:\Windows\System32\dhcp]&lt;/CODE&gt;&lt;/P&gt;

&lt;P&gt;With the (“\”s added.&lt;/P&gt;</description>
      <pubDate>Sat, 07 Mar 2015 20:06:01 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Windows-DHCP-Logs/m-p/13303#M1165</guid>
      <dc:creator>mcronkrite</dc:creator>
      <dc:date>2015-03-07T20:06:01Z</dc:date>
    </item>
    <item>
      <title>Re: Windows DHCP Logs</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Windows-DHCP-Logs/m-p/13304#M1166</link>
      <description>&lt;P&gt;crcSalt = &lt;BR /&gt;
Did it mean  is to be replaced with DHCP Servers IP?&lt;/P&gt;</description>
      <pubDate>Mon, 27 Nov 2017 10:49:53 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Windows-DHCP-Logs/m-p/13304#M1166</guid>
      <dc:creator>koolvasco</dc:creator>
      <dc:date>2017-11-27T10:49:53Z</dc:date>
    </item>
    <item>
      <title>Re: Windows DHCP Logs</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Windows-DHCP-Logs/m-p/13305#M1167</link>
      <description>&lt;P&gt;Look at this documentation Link: &lt;/P&gt;

&lt;P&gt;&lt;A href="https://docs.splunk.com/Documentation/Splunk/7.1.0/Admin/Inputsconf"&gt;https://docs.splunk.com/Documentation/Splunk/7.1.0/Admin/Inputsconf&lt;/A&gt;&lt;/P&gt;

&lt;UL&gt;
&lt;LI&gt;If set to the literal string  (including the angle brackets), the
full directory path to the source file is added to the CRC. This ensures
that each file being monitored has a unique CRC.   When crcSalt is invoked,
it is usually set to .&lt;/LI&gt;
&lt;/UL&gt;</description>
      <pubDate>Tue, 22 May 2018 23:39:47 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Windows-DHCP-Logs/m-p/13305#M1167</guid>
      <dc:creator>vgollapudi</dc:creator>
      <dc:date>2018-05-22T23:39:47Z</dc:date>
    </item>
  </channel>
</rss>

