Issues with authenticating to AD.

Hello.

I am attempting to connect to LEM for AD login, but am having issues with authenticating to the DC.

Below is a screen shot of my test to see if it connects to the AD. I can ping the LEM server and the DC and vice versa.

Heres my actual config for the connection to the DC server. I test the connection and all I receive is a small note on the bottom right stating 'sending connector comment...done.'

I guess its running. I start the app and then try to add AD groups and receive the following error message:

I have followed the instructions as per solarwinds, but not got anywhere. Do I need to look on the server or the front facing gui?

Find more posts tagged with

Accepted answers

All comments

vitezslav.papiez

Hello shaun_9999,

there was a change in LDAP communication since the 6.3.1 release and it is not clear from the post on which version you are running on. Therefore we do not know what issues you might be facing. I would try to configure the connection via http://LEM_MANAGER_IP:8080/mvc/login . If it won't be working as well, open a ticket with our Support. They will know how to proceed. Please, do not forget to attach logs.

Thank you

curtisi

Okay, it's a little hard to be sure with the obfuscation (and I understand why you did that), so here's a guide to how those fields should be populated from my lab:

2018-05-30 08_38_45-SolarWinds Log & Event Manager.png

Alias: This doesn't matter, it's just for human readability.

Domain Name: The FQDN of your domain, so you'll need to include the .com or .local or whatever on the domain.

Directory Service Server: This needs to be the hostname or IP of a domain controller.

User Name: The user that has rights to do directory queries. Basically, any user has this right, so this account doesn't need to be special.

Note: The LEM will put the username provided together with the domain name, so you don't want to put the domain in the User Name field.

Password: For the use doing the queries.

Encryption: This depends on your environment.

Custom Port: Unless you know you've changed the AD ports on your DCs, leave this blank. LEM will assume the defaults.

Test Domain Name: The FQDN of your domain controller.

Make sure the connector is saved and running before clicking the "Test Domain Connection" button, or it will not work.

Now that you've done all that, though, this connector is just for pulling AD information (assuming you're running a newer version of LEM) like groups. If you want authentication to work, you'll need to check out these steps:

Set up Active Directory authentication in LEM - SolarWinds Worldwide, LLC. Help and Support

shaun_9999

Alias: Ergo test.

Domain Name: xxxx.com (that's the FQDN)

Directory Service Server: xxx.xxx.xxx.xxx (the IPv4 address)

User Name: I've used my own domain admin account for testing. I know that I can connect to the DC with my account. I've tried to use the service account to, but get the same error.

shaun_9999

We are using 6.2.1

shaun_9999

I just ran an nDepth and I am getting Connection to directory service failed. I then ran the InternalAllInfo request and didn't provide me with any substantial information.

I can't go to Solarwinds, as the company stopped paying for support a couple of years ago on this product.