Question

Windows authentication using DNS name instead of server name

Updated February 7, 2017

asked on February 2, 2017

I am trying to use windows authentication against a DNS name (Laserfiche-Prod) instead of the actual server name (LFS01) with the Laserfiche client. However when using the DNS name and windows authentication, I get the message "The user account name or password is incorrect".

Does anyone know if this is possible?

0 0

Replies

replied on February 2, 2017 • Show version history

Can you clarify the exact steps you are taking? It sounds to me like you are registering the repository with the DNS alias and then attempting to log in by checking the Windows authentication check box, is that right? That worked for me when I tried it, and I can't think of a reason why it wouldn't work.

If you are entering "Laserfiche-Prod\username" and password, this won't work since "Laserfiche-Prod\username" is not a valid Active Directory account. Even so, authenticating as a local machine account instead of a domain account would be pretty unusual. Is there a reason not to use a domain account?

0 0

replied on February 6, 2017

Hi Brian,

I launch the Laserfiche client, click on the attach button, enter Laserfiche-Prod into the laserfiche server box, select the repository name from the drop down, click attach and leave the Windows authentication radio button selected. When I click OK, I get the message " The user account name or password is incorrect. [9010]". If I select the Password authentication radio button and use a Laserfiche account, it works.

0 0

replied on February 6, 2017

That works for me and I can't think of how the dns name would come into it. You might want to work with your reseller to open a support case.

0 0

replied on February 7, 2017

Thanks Brian, I will contact our reseller.

0 0

You are not allowed to follow up in this post.

Question

Question

Windows authentication using DNS name instead of server name

Replies

Sign in to reply to this post.