Mirrors/Sonarr
1
0
Fork 0
mirror of https://github.com/Sonarr/Sonarr.git synced 2024-11-22 02:32:51 +01:00
Code Issues Releases Wiki Activity

Add a mapped network drive common problems section.

Donald Webster 2019-12-14 21:20:55 -08:00
parent 761db96df1
commit e18fa8e090
1 changed files with 4 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
Downloads-and-Importing.md

@ -20,3 +20,6 @@ Incorrect path issues are possible too, though less common in normal setups. The
## Can't see share on Windows
The default user for a Windows service is **SYSTEM** which typically doesn't have access to your shares. Edit the service and set it up to run as your own user, see the FAQ entry [why can't Sonarr see my files on a remote server](https://github.com/Sonarr/Sonarr/wiki/FAQ#why-cant-sonarr-see-my-files-on-a-remote-server) for details.
## Mapped network drives are not reliable
While mapped network drives like `X:\` are convenient, they aren't as reliable as UNC paths like `\\server\share`. Setup Sonarr and your download client(s) so that they user UNC paths as needed. If your library is on a share, you'd make sure your root folders are using UNC paths. If your download client sends to a share, that is where you'll need to configure UNC paths since Sonarr gets the download path from the download client. It is fine to keep your mapped network drives to use yourself, just don't use them for automation.