Splunk version 6.6.2
Splunk DB Connect Version 3.1 (Build 19)
I've created an identity to login using the same Windows domain user currently used in Splunk DB Connect 1. I know everything is setup correctly on the remote end because DB Connect 1 is able to access our SQL Servers. However, Splunk DB Connect 3 is unable to connect to these same SQL Servers.
The specific error is a "login failed for user..." and the user is NOT the username in the identity. The domain is correct; however, the user is incorrect. It looks like DB Connect is trying to login using the machine name.
Server Name: WS693
Identity information
================
Identity name: dlovett
Identity username: dlovett
Use Windows Authentication Domain is checked with correct domain name=DOM.
Connection Information
=====================
identity: dlovett
connection type: MS-SQL Server Using MS Generic Driver With Windows Authentication
Error Information
======
When I try to save the connection I get a login error for user "DOM\WS693$"
Again, nothing has changed on the remote SQL Server end and our DB Connect V1 connections are working fine using the same domain username credentials to login to the same servers.
As an interim solution, I can login via Splunk DB Connect v3 using SQL Server IDs. However, using local SQL Server ids to connect to DB servers is not the standard where I work. The DBA's prefer we use domain accounts.
I tried following suggestions/answers that address a similar issue for Splunk DB Connect 2; However, none of those worked.
Any help would be greatly appreciated.
... View more