Deployment Architecture

Help configuring forwarder on Windows 2008R2 for DHCP & RADIUS logs

Sparky70
New Member

I am attempting to add the DHCP and RADIUS logs on a server installed with the Splunk Forwarder.

I have the following configured within C:\Program Files\SplunkUniversalForwarder\etc\apps\Splunk_TA_windows\local\input.conf and restarted the forwarder service.

###### DHCP ######
[monitor://C:\Windows\System32\DHCP]
disabled = false
whitelist = Dhcp*.log
crcSalt = <SOURCE>
sourcetype = Dhcp
alwaysOpenFile = 1

###### RADIUS ######
[monitor://C:\Windows\System32\LogFiles]
disabled = false
whitelist = IN*.log
crcSalt = <SOURCE>
sourcetype = RADIUS
alwaysOpenFile = 1

I cannot see any of that data within Splunk. What am I missing?

0 Karma

phuongnst
New Member

Just this command in input.conf

DHCP

[monitor://C:\Windows\System32\DHCP\Dhcp*.log]
disabled = 0

0 Karma

jstrandman
New Member

You might still have an other inputs.cong file taking precedence over the one you listed above. Check /system/local and any other apps.

0 Karma

satishsdange
Builder

make disabled = 0 & see the results.

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!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...