You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For a shared drive on a regular Windows machine, not a corporate collaborative drive, the user was able to successfully login, but they couldn't see any files (the share had been the C drive). After some experimentation, replacing the '/' (which isn't a Windows location) with Users, the browser displayed the files in that directory. Going up from that location, the '/' reappeared in the field with the path, but the correct files were now visible in the file browser. I suspect that the initial landing spot of 'root' is the source of the problem, since for Windows that should be the C drive. Only once the file browser had been pointed to a valid location, could it actually find and return a file list.
The text was updated successfully, but these errors were encountered:
For a shared drive on a regular Windows machine, not a corporate collaborative drive, the user was able to successfully login, but they couldn't see any files (the share had been the C drive). After some experimentation, replacing the '/' (which isn't a Windows location) with Users, the browser displayed the files in that directory. Going up from that location, the '/' reappeared in the field with the path, but the correct files were now visible in the file browser. I suspect that the initial landing spot of 'root' is the source of the problem, since for Windows that should be the C drive. Only once the file browser had been pointed to a valid location, could it actually find and return a file list.
The text was updated successfully, but these errors were encountered: