Issues with server indexing permissions on DFS share

[onedrop]

Currently testing the install/config of everything server and keep running into issues with the server indexing some DFS share locations. All shares have the following minimum permissions assigned

There seems to be some permissions issue with the shares that i cant seem to isolate. Below is a synopsis

If \\DFSdomainRoot\Namespace1\Share1 is set as the index folder directory in Tools-Option-Index-Folder Everything is unable to index any files
permissions on the above parent folder for service user acct is - Read&Execute - list folder contents

if \\DFSRoot\Namespace1\Share1\subfolder1 is added as a folder, the server IS able to index this path fine
permissions on the above folder for service user acct is - Read&Execute - list folder contents
this share a referral on a separate device.

if \\DFSRoot\Namespace1\Share1\subfolder2 is added as a folder, the server IS NOT able to index this path
permissions on the above folder for service user acct is - Read&Execute - list folder contents
this share is in the main dfs namespace.

Question is why is it able to index some of the subfolders and not other even though the permissions are similar

[void]

Please try the following to debug the issue:

• Stop the client service:
• Everything.exe -stop-client-service
• Launch Everything with the same service user account. (If this isn't an easy option, please let me know)
• Show the debug console from Tools -> Debug -> Console.
• Rescan your "\\DFSRoot\Namespace1\Share1\subfolder2" folder from Tools -> Options -> Folders -> Rescan Now
• Watch the debug console for errors in Red text, they should look like:
  FindFirstFileEx <error-code> \\DFSRoot\Namespace1\Share1\subfolder2
• What error code is shown?
• Exit Everything (File -> Exit)
• Restart the client service:
• Everything.exe -start-client-service

Error 5 might indicate a permission issue.
Everything will only need list access. (FILE_LIST_DIRECTORY)

[onedrop]

see attached for debug log

[void]

Thanks for the log.

Error 59 is ERROR_UNEXP_NET_ERR: An unexpected network error occurred.

Maybe a timeout? how large is this folder?
Antivirus or firewall blocking the access?
Is there a folder junction redirection in the path on the server?
-Check the event viewer for on both client and server for SMB or redirector errors.

Weird the first FindFirstFile call fails with error 59, then immediately after with 5.
To me that sounds like Antivirus or firewall temporarily blocking access after an error.



What OS are you using for the server?

[onedrop]

There is folder junction redirection taking place. All windows firewall disabled on client workstation and server as part of testing. No real errors in the SMB logs in event viewer that point to an issue. Server os is Win2k22

[void]

Does the issue occur for shares where there's no redirection?

FindFirstFileEx 5 \\\\DFSRoot\Share\Subfolder1\*

This folder shouldn't be starting with \\\\DFSRoot (it should be \\DFSRoot)
On the Server, could you please upload your Everything-1.5a.ini in a bug report.

[onedrop]

Does the issue occur for shares where there's no redirection?

FindFirstFileEx 5 \\\\DFSRoot\Share\Subfolder1\*

This folder shouldn't be starting with \\\\DFSRoot (it should be \\DFSRoot)
On the Server, could you please upload your Everything-1.5a.ini in a bug report.

That was a typo, I have attached server ini to bugreport with title of tihis topic.
It seems the other way around the redirected shares are the one that seem to work vs the ones directly in the DFSRoot not working. i will test further and validate