1

Hello!

Firstly, I’m so excited to find a helpdesk solution that provides everything I need to better serve my network users all in a beautifully written program.

I’m getting ready to deploy Spiceworks in my organization, however can’t seem to get the Active Directory authentication working, and was wondering if someone could help me.

I’ve been in search of this answer for some time and every thread I find on this subject seems to suggest that if you use user@domain.com it tends to be more successful rather than domain\user – I can’t seem to get either one working correctly and instead I receive “Parameter Error”.

I’ve verified that this account is correct, and when I on purpose use invalid credentials Spiceworks notifies me correctly, so I am to assume that there is either something not configured correctly with the user I’m using (not sure if there is a specific requirement other than read privilages), or i’m doing something wrong.

I assume that spiceworks allows for periods in the domain name other than before the “.com”, however my domain has multiple periods – user@my.do.main.com, three to be exact. Has anyone had a similar experience? The Spiceworks version that I am on is version 3.0.21605.

Thank you!

Matt

— EDIT —

I just updated Spiceworks to Version 3.0.22722 and can confirm that this issue hasn’t been fixed.

Thanks!

Matt

6 Spice ups
2

I also am having the same issue…

I have tried

DOMAINNAME\Username

Domainname.com\Username

even

username@domainname.com

With the same Verifying… ‘Parameter Error’

Thanks,

Jon

3

I am also experiencing the same problems. “Parameter Error” We are using Active Directory on a Windows 2000 Server. Running spiceworks version 3.0 final.

Heath

4

I too am having this problem. Has anyone figured it out yet?

Edit

I just realized that windows server 2000 was not on the supported list, and thats the OS I was running. I migrated over to an XP box that was not being utilized and it seems to be working great. If you’re also running server 2k then this might help.

5

Sorry to report that this is still an issue. I just now downloaded Version 3.0.23470 and get the same error on our freshly setup W2k server. It would be nice if the SpiceWorks folks could get this to work on server 2k. We have a collection of business critical ancient apps that run in server 2k .