Hi Robert,

The user has attempted logging in with both Windows Authentication and entering credentials manually to no avail.

Thanks!

Their machine needs to be a member of the windows domain to use windows authentication. 

Hi Robert,

The user's machine looks to be a member of the windows domain as they are able to log in with Windows Authentication when they are locally connected to their network and not over VPN. Is there something in the VPN configuration that may change the machine so that it no longer thinks it is a part of the Windows Domain?

Thanks

I don't see how it would make a difference. You can verify that they are logged in to windows as the correct use by running whoami from the windows command prompt. Also, try clearing the kerberos tickets by running 'klist purge' before signing in to Laserfiche.

HI Robert,

I will go ahead and look into that. Quick question, am I running the klist purge on the users machine in Command Prompt?

Thanks!

Yes, on the problem machine when it is connected to the vpn.

Hi Robert,

I have had the user run whoami while connected to VPN and it is the same result they get when connected directly to their network. I also had them run klist purge and it said "succesful" but still no luck in getting them logged into the LF client while on VPN.

Thanks!

Are there specific ports that need to be open between the client and server or vice versa that maybe aren't open and is causing the issue?

Thanks!

If they get an 'invalid username' error, that means the client is able to communicate with the LF server. At this point I would suggest opening a support case. I can't think of why it would fail like this, but if we get some trace logs it might reveal the cause.