Security

LWF talking on UDP 137??

garysmith
New Member

After installing the lightweight forwarder on a DMZ machine, I'm seeing UDP 137 traffic to my splunk server (which is being blocked by my firewall). Is this expected behaviour?

Tags (2)
0 Karma

GArienti
Explorer

Did you ever find out the resolution for this ?
I am seeing the same after installing the Forwarder on my servers, they are all dropping on my ASAs

0 Karma

amrit
Splunk Employee
Splunk Employee

This isn't anything Splunk is doing. If you take a look in /etc/services, you'll see that 137 is a NETBIOS (SAMBA, SMB) port. I'm not sure of what the purpose of this port is, as there are a number of SMB ports (137-139), but I would assume it's just some sort of broadcast to find out whether or not this box is NETBIOS accessible.

Get Updates on the Splunk Community!

Now Available: Cisco Talos Threat Intelligence Integrations for Splunk Security Cloud ...

At .conf24, we shared that we were in the process of integrating Cisco Talos threat intelligence into Splunk ...

Preparing your Splunk Environment for OpenSSL3

The Splunk platform will transition to OpenSSL version 3 in a future release. Actions are required to prepare ...

Easily Improve Agent Saturation with the Splunk Add-on for OpenTelemetry Collector

Agent Saturation What and Whys In application performance monitoring, saturation is defined as the total load ...