Splunk Enterprise

Usin Splunk forwarder

abe
New Member

Hi

I have installed a Splunk Forwarder on a remote computer and I chose wmi as data input in the main server. But when I want to find a log I get the message that remote computer is not reachable. This is while I have defined firewall rules for Splunk dynamic ports. Would you please help me?

Labels (1)
0 Karma

datadevops
Path Finder

Hi there,

The remote Splunk Forwarder might not be reachable due to:

  1. Connectivity: Ping the remote machine and check WMI service status.
  2. WMI configuration: Verify inputs.conf settings (server, namespace, credentials, source path).
  3. Firewall: Ensure firewall allows connections on Splunk dynamic ports (9997, 8089) and WMI port (135).
  4. Authentication: Double-check Splunk credentials have WMI access on the remote machine.
  5. Logs: Review Splunk logs on both machines for errors or warnings.

If these don't help, consider:

  • Testing WMI connection manually using wbemtest.exe.
  • Enabling debug logging in inputs.conf for more detailed logs.
  • Using file inputs instead of WMI if necessary.

Please provide more details (Splunk version, error messages) if you need further assistance.

~ If the reply helps, a Karma upvote would be appreciated

0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Announcing Modern Navigation: A New Era of Splunk User Experience

We are excited to introduce the Modern Navigation feature in the Splunk Platform, available to both cloud and ...

Modernize your Splunk Apps – Introducing Python 3.13 in Splunk

We are excited to announce that the upcoming releases of Splunk Enterprise 10.2.x and Splunk Cloud Platform ...

Step into “Hunt the Insider: An Splunk ES Premier Mystery” to catch a cybercriminal ...

After a whole week of being on call, you fell asleep on your keyboard, and you hit a sequence of buttons that ...