You are viewing limited content. For full access, please sign in.

Question

Question

"operation timed out 784" and then "No response received from the server 780"

asked on August 14, 2020

Laserfiche Avante 10.4.1 build 350

when trying to connect to LF server with LF client (10.4) using windows authentication I am receiving these errors:  1st I get "operation timed out 784" after a couple of tries I receive "No response received from the server 780"  

if I put in respository credentials (not windows authentication) I can log in without issue on the client machines.

Also on the LF server I can log in with the client using windows authentication without issue.

The firewall and antivirus software have been turned off on both the server and client machine while testing this and windows will not authenticate from the client machine. This has been tested with multiple client machines. I have to create repository users for them to be able to access LF.

Otherwise everything in LF is working as expected. Just can't authenticate windows users from client machines.

Any suggestions/input would be greatly appreciated.

Thanks

1 0

Replies

replied on August 17, 2020

Hi Wendi,

 

It sounds like if you can login with a repository user but not windows authentication, you will likely have a kerberos issue.

 

Check the windows event logs directly after trying to connect to Laserfiche using windows authentication on both the server and workstation and you will likely see an error relating to kerberos ticket decryption exactly at the time you tried to login.

 

I'm no expert of kerberos, but know this to be the source of your issue.

 

Hope this helps point you in the right direction! smiley

1 0
replied on August 18, 2020

Hi Chris, thank you very much for replying, truly appreciate it. We did look at the event viewer and found nothing, however thanks to your reply i dug a little deeper and found the kerberos error. Not exactly sure how to fix it yet, but you definitely helped point me to the error!  Thank You! Wendi

0 0
replied on August 28, 2020

I am still fighting this is seems to be a VLAN issue, windows authenticates from the VLAN the server is on but no other VLANs. We did open a VLAN with no restrictions (any/any) have TCP, UDP and all protocols open.

I receive this error on the client machine that is on the open VLAN. Also I did disable the windows firewall, and virus protection on this client machine while testing but still receive the errors when using windows authentication.  Repository user works fine from all VLANs

0 0
replied on August 28, 2020

also i did purge the kerberos list on the server and client machine.  Any help would be very much appreciated.

0 0
replied on March 10, 2021

Was this fixed? Getting same error 

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.