This is very strange, please open a support case so we can get the logs needed to diagnose the problem.

You noted "The only unusual thing is I do port mapping on my firewall so external port 444 maps to 443 internally. On the client I attach the repository using servername.com:444 and check use ssl. the Repositories list in the drop down just fine but if I use Windows auth it doesn't work."

Is the client in the same domain as the Server? Why would you need to do port mapping?

If you manually type in the login information (e.g. domain\username) in the username field of the client and then put in the password for the account, does windows authentication work?

Raymond,

We do port mapping because we are using our external WAP IP port 443 for other applications. I am connecting a client to the external FQDN of our router and logging in from remote locations with the client.

The clients are at remote locations and we wish to securely use the full client.

No, if I select Laserfiche authentication and enter domain\username and password it rejects the name and password the same as selecting Windows Auth.

Is the LF client that you are using inside the same domain that the Laserfiche server is in or outside of it?

In the same domain.

Please open a support case so we can get the logs needed to diagnose the problem.

I know this was a while back, but was there ever a solution found to this issue?

I am having the exact same issue with the LF Desktop Client version 10.3 failing to authenticate Windows accounts over SSL. Web Client, Forms, Import Agent, etc. authenticate Windows accounts over SSL fine, and the LF Desktop Client will authenticate Windows accounts when NOT using SSL; LF repository users work over SSL, but not Windows accounts.

Any update is appreciated!