<?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: UNC Path to Network Print Server in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/UNC-Path-to-Network-Print-Server/m-p/701065#M116043</link>
    <description>&lt;P&gt;While ingesting files from network shares is possible (but has performance drawbacks especially in high-volume scenarios) it requires the ingesting component (either a HF or UF) to run with a domain user which has access to the source share. Maybe, just maybe it could work with a completely public share (haven't tested it myself) but it's not a very good idea in a first place.&lt;/P&gt;</description>
    <pubDate>Fri, 04 Oct 2024 21:34:59 GMT</pubDate>
    <dc:creator>PickleRick</dc:creator>
    <dc:date>2024-10-04T21:34:59Z</dc:date>
    <item>
      <title>UNC Path to Network Print Server</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/UNC-Path-to-Network-Print-Server/m-p/701061#M116042</link>
      <description>&lt;P&gt;Trying to monitor a separate print server folder outside where Splunk is hosted with print logs that has a UNC path.&amp;nbsp; Folder only has .log files in it.&amp;nbsp; I have the following index created:&lt;/P&gt;
&lt;LI-CODE lang="markup"&gt;index = printlogs&lt;/LI-CODE&gt;
&lt;P&gt;When I try to add the folder path in Splunk through the add data feature: "add data" - "Monitor" -"Files &amp;amp; Directories" I get to submit and then get an error:&lt;/P&gt;
&lt;P class="lia-indent-padding-left-30px"&gt;"Parameter name:&amp;nbsp; Path must be absolute".&lt;/P&gt;
&lt;P&gt;So I added the following stanza to my inputs.conf file in the systems/local/folder:&lt;/P&gt;
&lt;LI-CODE lang="markup"&gt;[monitor://\\cpn-prt01\c$\Program Files\Printer\server\logs\print-logs\*.log]
index = printlogs
host = cpn-prt01
disabled = 0
renderXml = 1 &lt;/LI-CODE&gt;
&lt;P&gt;I created a second stanza with a index = printlogs2 with respective index to monitor the following path to see if I can pull straight from the path and ignore the file type inside.&lt;/P&gt;
&lt;P class="lia-indent-padding-left-30px"&gt;[monitor://\\cpn-prt01\c$\Program Files\Printer\server\logs\print-logs\]&lt;/P&gt;
&lt;P&gt;I do see the full path to both in the "Files &amp;amp; Director" list under the Data Inputs.&amp;nbsp; However, I am not getting any event counts when I look at the respective indexes seen in the Splunk Indexes page.&amp;nbsp; &amp;nbsp;I did a Splunk refresh and even restarted the Splunk server with now luck.&amp;nbsp; &amp;nbsp;Thought maybe someone has run into similar issue or has a possible solution.&amp;nbsp;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks in advance.&lt;/P&gt;</description>
      <pubDate>Fri, 04 Oct 2024 23:41:18 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/UNC-Path-to-Network-Print-Server/m-p/701061#M116042</guid>
      <dc:creator>ramuzzini</dc:creator>
      <dc:date>2024-10-04T23:41:18Z</dc:date>
    </item>
    <item>
      <title>Re: UNC Path to Network Print Server</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/UNC-Path-to-Network-Print-Server/m-p/701065#M116043</link>
      <description>&lt;P&gt;While ingesting files from network shares is possible (but has performance drawbacks especially in high-volume scenarios) it requires the ingesting component (either a HF or UF) to run with a domain user which has access to the source share. Maybe, just maybe it could work with a completely public share (haven't tested it myself) but it's not a very good idea in a first place.&lt;/P&gt;</description>
      <pubDate>Fri, 04 Oct 2024 21:34:59 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/UNC-Path-to-Network-Print-Server/m-p/701065#M116043</guid>
      <dc:creator>PickleRick</dc:creator>
      <dc:date>2024-10-04T21:34:59Z</dc:date>
    </item>
  </channel>
</rss>

