Closed bengalih closed 2 weeks ago
Hmm, I thought I resolved this issue in server PR #3254. I'll check this again.
OK, I just checked with the latest version (2.16.2) and it is still working for me.
As explained in #3254, It is expected that when you put \\server\share\audiobooks
as the library folder, it would be normalized to \\server/share/audiobooks
However you said it is normalized to \\server/share\audiobooks
(i.e. the first single backslah is normalized to slash but the second single backslash is not normalized). Are you sure this is what you're seeing? that is not expected.
Have you tried using windows explorer to access \\server\share\audiobooks
? Does it work?
You are right, that was a typo on the normalization. Also, I just tried again and I was incorrect, it does seem to work with UNC paths, despite the normalization. This includes even DFS paths. I'm not sure why it didn't work the first time(s) I tried it. Perhaps I was impatient or maybe the scan function was behaving erratic (I seemed to click it a couple of times and it did not appear to start scanning the network location). It does appear to work now. I appreciate you double checking and having me do the same.
If you're eager to see how a scan is progressing, you can go to the Logs
page and set Server Log Level
to Debug
. This will show you debug messages from the scan.
Simply put the interface doesn't allow to specify UNC paths to network locations.
The software supports accessing books across network, because you have the ability to map a drive to a UNC location:
net use x: \\server\share\audiobooks
Then the X drive will work for the library. In fact, even DFS paths are supported, but require you to map the drive first.
If you try to manually add the UNC path above, the interface changes it to:
\\server/share\audiobooks
And it doesn't properly access the location.