Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
- About abaumbusch
abaumbusch
Explorer
Member since:
07-18-2018
05-19-2022
Community Statistics
| Posts | 9 |
| Solutions | 0 |
| Karma Given | 3 |
| Karma Received | 1 |
| Member Since | 07-18-2018 |
Activity Feed
- Karma Re: Windows Universal Forwarders no longer performing AD GUID/SID-to-value lookups after upgrade to 8.1 for jeff. 02-08-2021 06:31 AM
- Karma Re: Windows Universal Forwarders no longer performing AD GUID/SID-to-value lookups after upgrade to 8.1 for jeff. 02-08-2021 06:31 AM
- Karma Re: Windows Universal Forwarders no longer performing AD GUID/SID-to-value lookups after upgrade to 8.1 for greggernigant. 01-13-2021 09:08 AM
- Posted Re: Windows Universal Forwarders no longer performing AD GUID/SID-to-value lookups after upgrade to 8.1 on Getting Data In. 01-13-2021 09:07 AM
- Posted Windows Universal Forwarders no longer performing AD GUID/SID-to-value lookups after upgrade to 8.1 on Getting Data In. 12-23-2020 02:02 PM
- Posted Re: Disabling KVStore parts of the Palo Alto app on All Apps and Add-ons. 09-11-2020 08:21 AM
- Got Karma for DB Connect 3.1.3 Issue: "Login failed. The login is from an untrusted domain and cannot be used with Windows authentication.". 06-05-2020 12:50 AM
- Posted Re: DB Connect 3.1.3 Issue: "Login failed. The login is from an untrusted domain and cannot be used with Windows authentication." on All Apps and Add-ons. 11-27-2018 10:52 AM
- Posted Re: DB Connect 3.1.3 Issue: "Login failed. The login is from an untrusted domain and cannot be used with Windows authentication." on All Apps and Add-ons. 11-02-2018 12:27 PM
- Posted Re: DB Connect 3.1.3 Issue: "Login failed. The login is from an untrusted domain and cannot be used with Windows authentication." on All Apps and Add-ons. 11-02-2018 10:41 AM
- Posted Re: DB Connect 3.1.3 Issue: "Login failed. The login is from an untrusted domain and cannot be used with Windows authentication." on All Apps and Add-ons. 11-02-2018 08:35 AM
- Posted Re: Splunk DB Connect 3: Why am I unable to login using Windows authentication? on All Apps and Add-ons. 11-02-2018 07:43 AM
- Posted DB Connect 3.1.3 Issue: "Login failed. The login is from an untrusted domain and cannot be used with Windows authentication." on All Apps and Add-ons. 11-02-2018 07:11 AM
- Tagged DB Connect 3.1.3 Issue: "Login failed. The login is from an untrusted domain and cannot be used with Windows authentication." on All Apps and Add-ons. 11-02-2018 07:11 AM
- Tagged DB Connect 3.1.3 Issue: "Login failed. The login is from an untrusted domain and cannot be used with Windows authentication." on All Apps and Add-ons. 11-02-2018 07:11 AM
Topics I've Started
01-13-2021
09:07 AM
I opened a support case with Splunk, but research on their end is still ongoing. They thought the issue might be with Windows machines on older versions of the OS (e.g. 2012), but we are seeing this on 2016 servers as well. If I do get a solutions from them, I will make sure to post it. Thanks for your response!
... View more
12-23-2020
02:02 PM
Greetings! We recently upgraded our UFs throughout the environment to 8.1.0, and since the upgrade, none of the Windows based forwarders appear to be doing AD GUID/SID-to-value lookups. We have verified that evt_resolve_ad_obj = 1 is set in inputs.conf for the [WinEventLog://Security] stanza (verified with btool as well), and prior to the upgrade, the functionality was working fine. We tried installing the 8.1.1 version of the forwarder on one box as a test, but the problem persisted. Has anyone seen this or have any suggestions on what to check? This is a multi-site clustered environment running Splunk Enterprise 8.0.7. Thanks for your help!
... View more
Labels
- Labels:
-
inputs.conf
-
universal forwarder
-
Windows
09-11-2020
08:21 AM
Hey, cboillot! I can currently seeing the same issue with the huge KVStore. Did you ever manage to work out a good solution?
... View more
11-27-2018
10:52 AM
I was not. I ended up having to a use a SQL Login which the client was not happy about because they are "less secure." I may try Kerberos, but happy to just be able to connect for now. I did a good amount of research and it appears that It is not possible to use native Windows Authentication for JDBC connections to MSSQL from a JVM running on Linux.
https://stackoverflow.com/questions/37835929/connect-to-sql-server-with-windows-authentication-from-a-linux-machine-through-j/37839177?noredirect=1#comment76499441_37839177
... View more
11-02-2018
12:27 PM
Yeah, no luck with the change you suggested. User did came across as sql login after that change.
... View more
11-02-2018
10:41 AM
I tried that change and received an Invalid User message. I believe this indicates that my user tried to authenticate as a SQL User instead of an AD account because the user name was not presented with the domain in the error message, and I had this happen before when experimenting with the JTDS driver. I have emailed the DBA to confirm which type of login came across. If I mistyped the password I will be very pleased. 😉
When trying to use that driver with integratedSecurity=true, I get a "This driver is not configured for integrated authentication." I assume this is normal behavior for this driver when DB Connect is on a Linux box based on the documentation for DB Connect. I'm so annoyed by this! The documentation makes it appear as if this should just work as long as you have followed the sparse instructions. I'm wondering if going with Kerberos is the proper thing to do (or just getting a sql server user) as I can't spend too much more time trying to get this to work.
... View more
11-02-2018
08:35 AM
Thanks, Rob. I have tried this without success.
... View more
11-02-2018
07:43 AM
Anyone ever have any luck with this?
... View more
11-02-2018
07:11 AM
1 Karma
I decided to post a new question as I have checked the previous questions and answers related to this error message on various versions of DB Connect, but alas, I am still stuck.
I am using DB Connect v.3.1.3 with Splunk 7.0.4 on Red Hat 7.5 to try and connect to a SQL Server 2014 sp2 CU13 database. The *nix box is a member of the same domain as the SQL Server box and I am using the "MS-SQL Server Using jTDS Driver With Windows Authentication" connection type and have the jtds-1.3.1.jar driver sitting in the right place with correct permissions for the splunk user. I keep getting the following error: Login failed. The login is from an untrusted domain and cannot be used with Windows authentication. I have searched the googles and tried out various permutations of the JDBC URL, modifications to the db_connections.conf file, permutations of the Identitiy (Win Auth toggle on/off, uname@domain vs domain/username, just uname with domain hard coded in JDBC URL, etc), but can't seem to make any headway.
Any help or ideas would be greatly appreciated!
... View more
Contact Me
| Online Status |
Offline
|
| Date Last Visited |
05-19-2022
05:49 PM
|
