I have tried every possible combination of Active Directory server settings and user fields I can think of to no avail. I’m either getting ‘Could not authenticate’ or ‘server down’ messages. Is there someone out in the SW community that could offer some guidance here. We’re hoping to go live with Spiceworks Help Desk this coming week and would love to have this AD authentication in place.

4 Spice ups

Hi Drew. Are you referring to scan errors? Or e-mail errors?

Kevin,

Actually, I’m just referring to the Help Desk settings page where you enter AD credentials to enable authentication via Active Directory to the help desk.

Drew

In the email settings, Spiceworks requires the address on fqdn of your Active Directory main server. This is for the LDAP connection. The other item it needs is a domain account that has at least READ access to the LDAP and its password. You should be able to test the connection immediately when you configure it. After that, Spiceworks will respond to AD account names for the email address of your users.

Try using the server’s IP address if the server name isn’t working. Also ensure (as Duwayne said) that you have read access with the credentials you are providing.

I believe the standard LDAP port is 389, but this is configurable on the Windows side.

Are you using LDAP (not LDAPS) on port 389?

I think you guys are misunderstanding the part of the configuration I’m having trouble with. It’s actually the Help Desk User Authentication section that I’m trying to configure, not the LDAP. (See attached)

That is exactly where the LDAP is used. SW links into LDAP to match up the user ID with the email address if they are stored in Active Directory properly. If you have an Exchange Server that uses Active Directory, this is the easiest way to connect Spiceworks to your users.

1 Spice up

The Active Directory server should be the same one that your Exchange server is pointed at. The user ID you list can be formatted as Domain\UserID or UserID@domain.local with the appropriate password. The userID must have at least read privileges in Active Directory to pull the information.

Drew,

DEngelhardt is right - try out a few different username formats, and try using the server’s IP address as well.

Let us know what you have tried, and what errors you get!

I am having a similar issue, but the only error message I get is “server down.” I’ve tried both IP address of the server and the server name, but I always get a very long “testing” message before it says “server down.”

I’ve tried it with both the spiceworks AD account I created and one that I know should work.

Any other suggestions, guys? Much appreciated!

serverdown.JPG

I am still having this problem can anybody advise

I had this problem for so long time.

Now I solved this one.

Clear to the default settings Advenced and try again - I tested this and this fixed my case.