Have a new install of FILR 23.2.1. Trying large deployment. When logging into the web interface, My Files can take like 10-30 seconds to come up. Just to make sure I was not guessing on the time. I just logged into FILR with my account and it took 1 minute and 20 seconds for the icons for Home, MyFiles and NetFolders to appear on the left side. That was unusually long. Only a few of us are testing it, I may have been the first to login today.
When I test connection in the Net Folder Server area. Very rarely does it immediately come back with a "Test Succeeded". If I test right after getting a valid result it will succeed immediately. I just did a quick test on 1 Net Folder Server and it took 11 seconds to come back with a "Test Succeeded". But sometimes it gives an error too. But if you try later it works. I feel I have some kind of authentication time out going on, that is delaying the accessing of FILR. They want all the connection to be DFS but for testing, we have tried the direct path and still seen issues.
Is there something to look for in the logs or settings I may want to review that could help? The famtd.log file is full of errors but I am unsure which ones are important. They might be errors because the FILR user just does not have rights to a folder it is trying to scan?
I do not know the Windows versions we are connecting too. They are really good about keeping them up to date. If there is a version I should be worried about let me know. Could there be windows setting I could ask the AD admins to verify that might cause an issue?
Thanks
Shane