Deployment Architecture

UF not connecting with Splunk Enterprise (Cooked connection timed out)

HankinAlex
Explorer

Hello, I have tried numerous configurations to get my Splunk Universal Forwarder to connect to my Splunk Enterprise instance with no luck. I am trying to forward data to my indexer located on port 3389 with the only info in the logs reading

WARN AutoLoadBalancedConnectionStrategy [136236 TcpOutEloop] - Cooked connection to ip=XX.XX.XX.XX:3389 timed out

I have checked telnet with that port in both directions and the connection is successful. Any advice would be appreciated

Labels (2)
0 Karma

gcusello
SplunkTrust
SplunkTrust

Hi @HankinAlex,

at firt the port you are usig is unusual, the default port for UF to IDX is 9997.

Anyway:

  • did you configured your IDX to receive logs from UFs on this port [Settings > Forwarding and Receiving > Receiving]?
  • did you configured your UF to send logs to the IDX editing outputs.conf file?

You can find detailed instructions at https://docs.splunk.com/Documentation/Splunk/9.1.2/Data/Usingforwardingagents

Ciao.

Giuseppe

0 Karma
Get Updates on the Splunk Community!

Earn a $35 Gift Card for Answering our Splunk Admins & App Developer Survey

Survey for Splunk Admins and App Developers is open now! | Earn a $35 gift card!      Hello there,  Splunk ...

Continuing Innovation & New Integrations Unlock Full Stack Observability For Your ...

You’ve probably heard the latest about AppDynamics joining the Splunk Observability portfolio, deepening our ...

Monitoring Amazon Elastic Kubernetes Service (EKS)

As we’ve seen, integrating Kubernetes environments with Splunk Observability Cloud is a quick and easy way to ...