Knowledge Management

DSBind Failed

walsborn
Path Finder

ERROR ExecProcessor - message from ""C:\Program Files\SplunkUniversalForwarder\bin\splunk-winevtlog.exe"" splunk-winevtlog - EvtDC::connectToDC: DsBind failed: (5)

We have 22 out of 3000+ hosts sending thousands of errors for this and I can't seem to figure out why. My best guess at this point is the forwarders need to be updated.  We have a distributed environment with multiple DC's.  Any idea if I'm doing something wrong on my end, or do I need to have these forwarders that are causing errors fixed?

I have things set up as follows:

All Windows hosts Universal Forwarders - inputs.conf -

[default]
evt_resolve_ad_obj = 0

Domain Controller UF inputs -

[admon://DefaultTargetDC]
targetDc = 'DC02'
startingNode = LDAP://OU=Computers,DC=ad
index = msad
monitorSubtree = 1
disabled = 0
baseline = 0
evt_resolve_ad_obj = 1

[admon://SecondTargetDC]
targetDc = 'DC03'
startingNode = LDAP://OU=Computers,DC=ad
index = msad
monitorSubtree = 1
disabled = 1
baseline = 0
evt_resolve_ad_obj = 0

[admon://ThirdTargetDC]
targetDc = 'DC01'
startingNode = LDAP://OU=Computers,DC=ad
disabled = 1
index = msad
baseline = 0
evt_resolve_ad_obj = 0

[admon://FourthTargetDC]
targetDc = 'DC02'
startingNode = LDAP://OU=Computers,DC=ad
disabled = 1
index = msad
baseline = 0
evt_resolve_ad_obj = 0

[admon://FifthTargetDC]
targetDc = 'DC01'
startingNode = LDAP://OU=Computers,DC=adu
disabled = 1
index = msad
baseline = 0
evt_resolve_ad_obj = 0

[admon://FifthTargetDC]
targetDc = 'DC01dev'
startingNode = LDAP://OU=Computers,DC=ad
disabled = 1
index = msad
baseline = 0
evt_resolve_ad_obj = 0

[admon://SixthTargetDC]
targetDc = 'DC04'
startingNode = LDAP://OU=Computers,DC=ad
disabled = 1
index = msad
baseline = 0
evt_resolve_ad_obj = 0

[admon://SeventhTargetDC]
targetDc = 'DC05'
startingNode = LDAP://OU=Computers,DC=ad
disabled = 1
index = msad
baseline = 0
evt_resolve_ad_obj = 0

[admon://EighthTargetDC]
targetDc = 'DC06'
startingNode = LDAP://OU=Computers,DC=ad
disabled = 1
index = msad
baseline = 0
evt_resolve_ad_obj = 0

[admon://NearestDC]
disabled = 1
baseline = 0
evt_resolve_ad_obj = 0

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!

A Four-Part Event Series: State of Observability - Where AI Meets Performance

As AI agents take on more complex tasks, teams need greater visibility into how they behave, what they cost, ...

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 ...

Build resilience for the agentic era: Join us at Splunk Go San Jose

AI is changing how organizations build, operate, and secure digital services. As teams adopt AI agents and ...