<?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: Splunk Heavy forwarder problem on port 9997 in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Splunk-Heavy-forwarder-How-to-fix-the-problem-on-port-9997/m-p/653300#M110810</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/254391"&gt;@MayurMangoli&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;did you permanently disabled the local firewall on the HF?&lt;/P&gt;&lt;P&gt;Ciao.&lt;/P&gt;&lt;P&gt;Giuseppe&lt;/P&gt;</description>
    <pubDate>Sat, 05 Aug 2023 05:31:10 GMT</pubDate>
    <dc:creator>gcusello</dc:creator>
    <dc:date>2023-08-05T05:31:10Z</dc:date>
    <item>
      <title>Splunk Heavy forwarder: How to fix the problem on port 9997?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Splunk-Heavy-forwarder-How-to-fix-the-problem-on-port-9997/m-p/653297#M110809</link>
      <description>&lt;P&gt;HI,&lt;BR /&gt;&lt;BR /&gt;i'm facing one of the issue on my heavy forwarder is not able to get the logs on 9997, where we have already configured the UF for port 9997 and receiving port 9997 on HF, but from the source to HF we telnet the HF on port 9997, for the first time it gets connected very next time it failed to connect.&lt;BR /&gt;&lt;BR /&gt;due to this we have not receving UF logs on the&lt;/P&gt;</description>
      <pubDate>Mon, 07 Aug 2023 19:14:55 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Splunk-Heavy-forwarder-How-to-fix-the-problem-on-port-9997/m-p/653297#M110809</guid>
      <dc:creator>MayurMangoli</dc:creator>
      <dc:date>2023-08-07T19:14:55Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk Heavy forwarder problem on port 9997</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Splunk-Heavy-forwarder-How-to-fix-the-problem-on-port-9997/m-p/653300#M110810</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/254391"&gt;@MayurMangoli&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;did you permanently disabled the local firewall on the HF?&lt;/P&gt;&lt;P&gt;Ciao.&lt;/P&gt;&lt;P&gt;Giuseppe&lt;/P&gt;</description>
      <pubDate>Sat, 05 Aug 2023 05:31:10 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Splunk-Heavy-forwarder-How-to-fix-the-problem-on-port-9997/m-p/653300#M110810</guid>
      <dc:creator>gcusello</dc:creator>
      <dc:date>2023-08-05T05:31:10Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk Heavy forwarder problem on port 9997</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Splunk-Heavy-forwarder-How-to-fix-the-problem-on-port-9997/m-p/653307#M110811</link>
      <description>&lt;P&gt;You are 100% sure your HF are listening on port 8089.&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;ss -pultan | grep LISTEN&lt;/LI-CODE&gt;&lt;P&gt;should result in some like this:&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;tcp    LISTEN  0       128                  0.0.0.0:8089         0.0.0.0:*       users:(("splunkd",pid=3870899,fd=4))&lt;/LI-CODE&gt;</description>
      <pubDate>Sat, 05 Aug 2023 08:58:20 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Splunk-Heavy-forwarder-How-to-fix-the-problem-on-port-9997/m-p/653307#M110811</guid>
      <dc:creator>jotne</dc:creator>
      <dc:date>2023-08-05T08:58:20Z</dc:date>
    </item>
  </channel>
</rss>

