UNC paths and network-share names

A UNC path identifies a Windows network server, share and remaining pathname without depending on a mapped drive letter.

A Universal Naming Convention path identifies a network resource directly. For a media file, the familiar form is:

\\nas.example.test\Media\Movies\Film.mkv
Component Meaning
nas.example.test The named server
Media The shared resource on that server
Movies\Film.mkv The remaining path within the share

The share name is not necessarily the NAS's physical directory name. A share called Media can expose storage whose server-side location has a completely different path.

Why a mapped drive can work only on the desktop

A desktop user might map M: to \\nas.example.test\Media. The letter is an alias established in that user's logon context.

A background service runs in a separate context and may not have that mapping, even when it uses the same account name in another logon session. Microsoft therefore documents UNC names for service access to remote resources rather than relying on another session's redirected drive letters.

Using the UNC path solves the naming dependency. The service still needs a reachable server and appropriate authentication and access rights. “I changed M: to a UNC name” does not establish that those later checks succeeded.

A path is not a credential or a web URL

The UNC string identifies the destination; it does not grant access. It also does not identify an Emby HTTP playback endpoint. An app receiving media from Emby Server generally uses that server's playback connection, while the server separately opens its media source.

On Linux, the same share may be mounted and presented through a path such as /srv/media/Movies/Film.mkv. That is the path the Linux server process uses. Copying a Windows UNC string into every application's path field is not a universal cross-platform substitute for configuring a supported file-access arrangement.

See Also

References